01 / NATIVE AGENT RUNTIME

AGENT AUTOMATIONUNDER HUMAN COMMAND.

Built for platform and AI engineering teams that answer to security reviews, auditors, and their own infrastructure.

  • SINGLE BINARY
  • MIT
  • POSTGRES HITL
  • SBOM + SIGNED

02 / WHERE PILOTS STALL

THE HARD PART STARTS AFTER THE DEMO.

Agent pilots do not fail because the demo was too small. They fail when control, deployment, and evidence arrive too late.

02

Dependency swamp

Ship one Rust binary. No Python or Node runtime is required in production.

Inspect the release
03

Procurement wall

Bring checksums, an SBOM, signatures, source, and an on-prem deployment path.

Review the posture

03 / THE OPERATING MODEL

CONTROL IS PART OF THE RUNTIME.

Every operating claim points to source, documentation, or a release artifact.

01

Human chain of command

Agents ask for missing context. Consequential tools wait for a separate, fail-closed approval.

HITL contract
02

Deploys where you are allowed

A native binary runs with your provider, your network controls, and PostgreSQL when scale needs it.

Deployment guide
03

Survives procurement

MIT source, CycloneDX SBOM, keyless signatures, checksums, and a signed OCI path.

Release evidence
04

Operates like infrastructure

Replicas coordinate durable ownership, replay, encrypted human answers, and graceful drain.

Multi-replica contract
05

No platform bet

Switch between native and OpenAI-compatible providers through configuration, including local Ollama.

Provider matrix

04 / WHAT YOUR TEAM SHIPS

A CREW YOU CAN READ. A RUNTIME YOU CAN OPERATE.

Define the team in readable Lua. The native runtime owns scheduling, policy, providers, and durable execution.

crew.lua / release-risk
local crew = Crew.new({
    goal = "Assess release risk",
    provider = "openai",
    model = "gpt-5.6-luna",
    require_approval = { "file_write" },
})

crew:add_agent(Agent.new({
    name = "researcher",
    goal = "Collect release evidence",
    tools = { "ask_human" },
}))

crew:add_agent(Agent.new({
    name = "reviewer",
    goal = "Challenge evidence and decide",
    tools = { "file_write" },
}))

crew:add_task({ name = "collect", description = "List the riskiest changes in this release." })

crew:add_task({
    name = "decide",
    agent = "reviewer",
    depends_on = { "collect" },
    description = "Write a go/no-go plan for: ${results.collect.output}",
})

crew:run()
Read the executable shape
01

PARALLEL DAG

Run independent specialists together, then synthesize.

02

COORDINATOR

Let one agent delegate bounded work to specialists.

03

ROUNDTABLE

Rotate through expert views with an explicit moderator.

04

HUMAN CHECKPOINTS

Pause for context or authorization before consequences.

05 / HUMAN AUTHORITY

HUMANS DON'T WATCH.THEY STEER.

Any agent can pause a live run for missing context. A human can answer from the CLI or over HTTP, and the same owner resumes from the suspended point.

INPUT

Ask the human

Several named agents can raise separately attributed questions inside one run.

Inspect human input
AUTHORITY

Approve the consequence

Tool approval is separate and fail closed. An answer never grants permission.

Inspect approval gates

06 / WORK WITH THE MAINTAINERS

OPEN CORE. DIRECT ACCOUNTABILITY.

The software stays open. Commercial work buys response commitments, direct expertise, and priority.

01

Support contracts

SLA-backed support from maintainers who work on the runtime.

02

Integration & consulting

Crew design, HITL patterns, deployment, providers, and PostgreSQL.

03

Sponsored development

Priority work that lands in the open-source core.

Explore enterprise services

V3.0.0 / RELEASE EVIDENCE

Inspect release assets

MAKE THE OPERATING MODEL EXPLICIT

BUILD THE CREW. KEEP THE CONTROLS.