Skip to content
For agencies

Build and run governed agents for your clients

OrchStack is the operating system for the AI-native company. At its core is OrchKernel. Give each client their own deployment, with their own rules, approvals and audit log.

Become a design partnerSee how it works
What clients ask

Clients want proof before agents touch their money

Agents you build for a client will email their customers, change their records and touch their money. Expect these questions.

01

Who approved that?

Risky actions should wait for a named person at the client, who sees exactly what will happen.
02

Who holds our keys?

Agents should not carry the client's CRM, billing and email credentials around.
03

What did it do?

The client needs a record of every action that they can check for themselves.
How agency work fits

One client, one deployment

Each client gets its own kernel, data, rules and log. Nothing is shared between clients.

  1. 01

    Deploy a kernel for the client

    One binary and one database file, with Docker and Kubernetes assets. Run it in the client's infrastructure or in yours.

  2. 02

    Draft the setup with the Architect

    Describe the client's company. The Architect drafts teams, modules, agents, rules and pages. You review and promote it.

  3. 03

    Install modules

    Turn on ready-made modules for Support, Sales, Marketing and more. Or upload modules you built to the client's catalog; a second admin reviews each one before it can be installed.

  4. 04

    Build what is missing

    A new agent is a record: a playbook, tools, a trigger, a trust tier and a budget. Changes go through review and a canary that rolls back automatically.

  5. 05

    Keep the client's rules in Git

    Export rules, budgets and kill switches to Git. Check them in CI and apply changes through review.

  6. 06

    Hand over the controls

    Client admins approve risky actions with the exact payload, see a scorecard per agent, and verify the log with ok audit verify.

ZendeskSalesforceStripeGitHubGmailGoogle CalendarSlackGoogle DriveAny MCP serverAny REST API
Built-in adapters, any MCP server, and declarative adapters for REST APIs.
License

What the license allows

OrchKernel is source-available under the Business Source License 1.1.

01

Allowed

  • Use, modify and run OrchKernel in production for your own organisation
  • Operate a deployment for one client organisation
  • Run separate deployments for separate clients
02

Needs a commercial license

  • Offering OrchKernel, or a modified version, as a hosted or managed service where one deployment serves more than one organisation

Multi-tenant hosting runs a kernel per tenant

Each version becomes Apache-2.0 four years after it is first published. Client libraries are Apache-2.0.

Agency questions

Bring one client workflow

Design partners run one real workflow on OrchKernel, with a direct line to the engineers building it.

Become a design partnerSee how it works
Runs on your own servers. The repository opens soon.