Skip to content
    Gaincontrol

    AI is probabilistic. Execution must not be.

    Drona is the execution layer we're building to close the gap between probabilistic AI and the deterministic trust enterprises need.

    The design has two parts: structured pipelines that limit what agents can decide before they run, and runtime checks that validate every action before it executes.

    Drona is in private development.

    Apply for early access to be notified when it ships.

    Request early access

    contract: cve-remediation · v3 (Design preview · in private development). Intent: patch the critical CVE on the payments hosts

    1. ingest scanner findings: in contract
    2. rank by EPSS: in contract
    3. open ITSM change: in contract
    4. ssh db-prod-01 "DROP TABLE …": blocked: not in contract, logged
    5. apply patch on payments hosts (JEA, 30 min): in contract

    4 steps allowed · 1 blocked before execution

    From chat to coordinated action

    A simulated run of the intended design: a plain-language request becomes a step-by-step plan across specialist agents, with every step recorded.

    Simulated run: illustrative steps, not live output.

    User intent
    Ingest latest vulnerability scan for payments-service, prioritize by EPSS > 0.7, open Jira tickets, and auto-remediate safe issues.
    Selected agents
    Vulnerability AnalyzerThreat IntelligenceITSM AgentLinux JEA Agent
    Execution timeline

    Planning & agent selection

    Drona Planner

    Ingest latest scan report

    Vulnerability Analyzer Agent

    Prioritize by EPSS & asset criticality

    Threat Intelligence Agent

    Create remediation tickets

    ITSM Agent

    Apply safe remediations

    Linux JEA Agent

    Execution output
    → Planning & agent selection [Drona Planner]
    ✓ Done: Planning & agent selection
    → Ingest latest scan report [Vulnerability Analyzer Agent]
    ✓ Done: Ingest latest scan report
    → Prioritize by EPSS & asset criticality [Threat Intelligence Agent]
    ✓ Done: Prioritize by EPSS & asset criticality
    → Create remediation tickets [ITSM Agent]
    ✓ Done: Create remediation tickets
    → Apply safe remediations [Linux JEA Agent]
    ✓ Done: Apply safe remediations
    Simulated run complete.
    Simulation complete

    Simulated: scan ingested (3,421 findings), 27 high-risk items prioritized (EPSS > 0.7), 12 Jira tickets drafted, 5 safe misconfigurations remediated, each step signed and logged.

    AI agents are probabilistic systems. The same prompt can produce different actions on different runs. Enterprises cannot accept that variability when agents touch production infrastructure. Existing orchestration tools route agent calls. They don't enforce what agents can do. The model decides and then acts. There is no validation layer between intent and execution. Constrain the decision space before the model runs. Validate every action before it executes. The model can be uncertain. The downstream consequences of that uncertainty are not.

    Two layers, by design. Both mandatory.

    IntentDesign timeRuntimeOutput

    Structured pipelines constrain the decision space.

    Before a single agent runs, Drona's workflow design layer is meant to define what can happen: which agents are in scope, which tools they can invoke, what data they can reach and which sequences are permitted. The model works inside a bounded space, not an open field.

    Every action checked before it executes.

    At execution time, Drona is designed to intercept each agent action (a file write, an API call, an infrastructure change, a credential use) and check it against the workflow contract before letting it proceed. The model may have decided; Drona decides whether that decision is permitted. Actions outside the contract are to be blocked, logged and surfaced for review.

    One fabric. Six planned domains.

    Each domain agent is planned as an instance of the same Drona execution layer for a specific enterprise context. The design-time constraints and runtime checks stay the same; only the permitted actions and tool integrations differ.

    Planned for every domain · design-time constraints, runtime enforcement, audit trail

    Security
    Threat response, CVE triage, and incident containment, executed with bounded and revocable permissions.
    Cloud Ops
    Provisioning, drift remediation, and cost optimization, within defined infrastructure boundaries.
    ITSM
    Ticket routing, SLA management, and escalation, with deterministic workflow sequencing.
    Database
    Query execution, schema operations, and backup verification, constrained to scoped credentials.
    JEA
    Just-enough-access grants, auto-revoked on task completion with zero standing privilege.
    Command
    Cross-domain workflows across multiple agents within a single coherent execution contract.

    Frequently asked questions

    Deterministic AI execution means that even though an AI model produces probabilistic outputs, the actions it takes in the real world are checked against explicit rules before they happen. Drona is being designed to enforce those rules at runtime, so no agent action outside its defined boundaries executes.

    LangChain and CrewAI are agent frameworks that help you build multi-agent workflows. Drona is being designed to sit above the framework layer and enforce safety constraints at runtime. The intent is to work with LangChain, CrewAI, AutoGen and custom agents, adding a deterministic execution contract on top of whichever framework you choose.

    That's the design. Drona is meant to check agent actions rather than model outputs, so it's being built to work with whichever model you use: Claude, GPT, Gemini, Llama or another.
    All posts
    • · 3 min read

      A checklist for evaluating agentic AI security vendors

      "Agentic AI security" bundles three different disciplines under one umbrella term: visibility, identity, and execution. Most vendors selling under it only answer one of the three.

    • · 3 min read

      What is agentic AI security?

      "AI security" and "agentic AI security" sound like the same category. They're not. One centers the model; the other centers what the model is authorized to do once it can act.

    • · 3 min read

      Authenticating the agent isn't authenticating the action

      "Which agent is this" and "is this action allowed right now" are different questions. Most systems built for agent authentication only ever answer the first one, and treat that as settling the second.

    Drona, in private development, is being built to enforce execution. Available today: Quin finds agent threats before they reach your pipelines, and Zino governs who's allowed to act.

    Get early access when Drona is ready.

    Drona is being built for engineering and platform teams who know that deterministic AI execution can't wait for a production incident to prove its value.

    Status · in private development · early-access requests open


    Request early access