Does OrchKernel make us compliant?

No product can do that alone. OrchKernel gives you approvals, a verifiable log and rules in Git. We hold no compliance certifications today.

How does a money movement an agent proposes actually run?

The agent proposes it. The gate checks kill switches, arguments, delegation, budgets, rules, then risk against trust. If approved, OrchKernel runs it with its own credentials.

Can an approved action run twice?

No. An approved action runs exactly once.

Can we show who changed a rule?

Yes. Rules live in Git and are applied through review, so the history shows who changed what and who approved it.

Use case

Agents near money, with controls you can prove

OrchKernel, the operating system for the AI-native company, holds goodwill credits proposed by agents for an admin and denies refunds to agents. Every action is chained in a log you can verify.

Become a design partner See how it works

The work today

What finance worries about

Agents that can issue refunds need the same controls as people who can.

Billing keys in every agent

Each agent holds its own API key to billing, so each one can move money on its own.

Approval after the fact

Risky actions happen first and get noticed later.

No trustworthy record

When an auditor asks why a credit was issued, there is no record of who proposed it and who approved it.

The agents

The agents that touch money

These ready-made agents propose or read money movements. Each one waits where it should.

From Support, Sales and the founder's office

Money moves only through the gate, and only with OrchKernel's own credentials.

Support Agent

Hands refund requests to a person and promises nothing.

Starts: When triage hands it a ticket.
Waits for: It cannot issue refunds. The Support module denies them to agents.

Churn-risk watcher

Can draft a goodwill credit for an at-risk account, only when the task owner asks for one.

Starts: When a ticket changes, plus a weekday morning sweep.
Waits for: Every goodwill credit needs an admin, whatever the agent's trust tier, and is capped per call.

Deal Desk

Approves proposals inside your discount and terms policy, and escalates the rest with a recommendation.

Starts: When a proposal moves to review.
Waits for: Its playbook escalates proposals outside your policy to a person.

Metrics Reviewer

Reads Stripe and your analytics each day, writes a snapshot and flags numbers that moved further than usual.

Starts: Daily.
Waits for: Nothing. It only reads.

How it stays safe

Controls and evidence

The $240 refund waits for an admin and runs exactly once.

Approvals for money movements

Write a rule for any tool that moves money, such as a Stripe refund. A $240 refund waits for an admin, who sees the exact payload, and runs exactly once.

Budgets and kill switches

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

A log you can verify

Each event is chained to the one before. ok audit verify names the first break.

Replay any run

Any run can be replayed from the log when someone asks what happened.

Policy as code

Rules, budgets and kill switches are exported to Git, checked in CI and applied through review.

Policy dry run

Ask the kernel to explain what a rule change would allow, hold or deny before you apply it.

Models cleared per data class

Financial data reaches only the models you have cleared for it.

OrchStack holds no compliance certification today. OrchKernel gives you controls and evidence; your auditors decide what they mean for your obligations.

StripeZendeskSalesforceSlackAny MCP serverAny REST API

Vendor webhooks are signed and deduplicated.

Finance and audit questions

Start with one money workflow

Bring one real refund or credit flow. We help you run it on OrchKernel, on your own systems.

Become a design partner See how it works

Runs on your own servers. The repository opens soon.