Skip to content
For SaaS companies

Agents in your product. Agents in your company.

OrchStack is the operating system for the AI-native company. At its core is OrchKernel: one gate, one log and one set of rules for your product's agents and your own.

Become a design partnerSee how it works
The problem

Agents that act need answers

Your product's agents now email customers, issue refunds and change records. Each one raises the same two questions: who is it acting for, and who said it could?

01

Keys everywhere

Each agent holds its own API keys to the CRM, billing and email.
02

Approval comes after

Risky actions happen first and get noticed later.
03

Nothing to show

When a customer asks what an agent did, there is no trustworthy record to show them.
In your product

A governed backbone for your product's agents

Keep building agents the way you do today. They reach the gate through the governed actions API or the MCP gateway.

An identity for every agent

Your product's agents get their own identity and act only through the gate, with a TypeScript or Python client or the MCP gateway.

Acting for a person

Delegation only narrows. An agent never has more than the person it acts for, and revoking it stops everything.

A clear answer every time

Each action is allowed, needs approval or is denied, with the reason. Approvers see the exact payload, and the run resumes when approved.

No vendor keys in agents

OrchKernel runs approved actions with its own credentials. Secrets are sealed at rest.

Budgets and kill switches

Set budgets per agent, team and task. A kill switch is the first check at the gate, so the next action stops there.

A record you can show

Every action lands in a tamper-evident log, and any run can be replayed.

Serving many customer organisations from one deployment is multi-tenant hosting. It is in build, and it needs a commercial license from OrchStack. Design partners help shape it.

In your company

Run your own operations with agents

Describe your company and the Architect drafts a blueprint: teams, modules, agents, rules and pages. A person reviews and promotes it. Nothing installs itself.

01

Support

Triage, Support Agent, QA reviewer, churn-risk watcher
See the agents
02

Sales

SDR Outreach, Deal Desk, Proposal Writer, Forecast Analyst
See the agents
03

Marketing

Lead Sourcer, Lead Qualifier, SEO Analyst, Content Writer and more
See the agents
04

Engineering

Incident Responder, PR Reviewer, Dependency Auditor, On-call Summariser
See the agents
05

Product and the founder's office

Release-notes writer, Feedback miner, Chief of Staff, Metrics Reviewer
See the agents
06

Money and audit

Approvals for refunds, budgets, policy as code and the audit log
See the agents

Each module comes with its playbooks, tools, rules and a scorecard per agent. Enable it in one click and map it to your teams.

How to start

Start with one workflow

Design partners pick one real workflow and run it on their own systems with us.

  1. 01

    Pick the workflow

    Choose work an agent should do for real, such as ticket triage, pull request review or a refund flow.

  2. 02

    Run the kernel

    Self-host OrchKernel: one binary and one database file. Connect the systems the workflow needs.

  3. 03

    Set the rules

    Decide what needs approval and who approves it. Trust is earned: sandboxed, standard, trusted.

  4. 04

    Bring your product's agents

    Point your own agents at the gate through the API clients or the MCP gateway.

SaaS questions

Govern the agents you ship

Bring one real workflow. We help you run it on OrchKernel, on your own systems.

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