The AI agent thatcan't break your rules
Not because the agent behaves — because a rule engine inspects every operation before anything commits. Rogue, dangerous, or invalid operations never land. Agents without that engine can run away; this one structurally can't.
- Pay invoice — $8,120 (cap $5,000) — A typical AI agent: Paid in full. No one was asked. On Perstack: Held before execution. Waits for your approval. (Mechanism: Approval checkpoint)
- Post invoice #4211, again (already posted) — A typical AI agent: Booked twice. On Perstack: Blocked by rule. It never commits. (Mechanism: Pre-commit rule check)
- “clean up old records” (production data) — A typical AI agent: Bulk-deleted production data. On Perstack: No such operation exists. Agents call named operations only. (Mechanism: Allowed operations only)
- call an external system (borrowed credentials) — A typical AI agent: Reached systems it was never meant to touch. On Perstack: Agents hold no credentials. External calls go through the gateway. (Mechanism: Credential-free gateway)
- “Sorry — I missed that rule.” (09:41) — A typical AI agent: An apology, after the damage. On Perstack: Checked before execution, recorded forever. Nothing to apologize for. (Mechanism: Tamper-proof audit record)
What “AI-native” means
A business system where work starts from business events: the AI does the processing, and a rule engine decides what may commit. People don't disappear — their role moves from working the screens to approvals, exceptions, and owning the rules.
Human-native
AI-native
How it works
How the workchanges hands
You do not rebuild your software, and you do not write prompts and hope. You describe the work; Perstack gives AI a system to run it in.
Describe
“An invoice arrives. Match it to the order and post it. Over the cap waits for a manager.”
Like training a new hire
It becomes your rules
- OperationPost an invoice
duplicate → blocked
- ApprovalPay an invoice
waits for you
Rules you read before it runs
AI runs it
This week: 40 invoices
- 38posted by AI
- 1waits for your click
- 1duplicate — blocked
Two decisions, not forty
Tune and widen
+ Foreign-currency invoices
Next month, hand over more
Agent governance
Readable work. Faithful execution.A complete record.
The written procedure is the definition that runs. Execution can only follow it, and every run lands in the append-only record — audit moves from sampling to the full population. Anything that needs judgment comes to you.
The working definition
v13 — changes recorded- OperationPost an invoice
- ApprovalPayment waits for a person
- RuleDuplicates are blocked
- RuleForeign currency waits too
The run record
append-onlywho · when · what · why
- 09:14posted — passed
- 09:22payment — approved: you
- 09:31post — duplicate blocked
- 09:40definition revised — v12 → v13
← from the record, back to the rule
Who writes the rules?
You do — in plain language. The first draft is generated from your description; you read it, change it, and every change is recorded. Rules live in the definition, not in a prompt.
Any workflow
Soft at the edges.Hard at the core.
Work arrives in any shape — email, chat, a scanned page — and the AI reads it as it is. The work itself is touched only by operations that pass your rules.
Your world
Event sources
- Your applicationyour UI · web · …
- EmailGmail · Outlook · …
- ChatSlack · Teams · …
- On a scheduledaily 9:00 · month-end · …
- Web formssignups · inquiries · …
- Other systemsAPI · CSV · …
- …
The backend
- Business data
- Rules — your definition
- Run recordappend-onlywho · when · what · why
PERSTACK
Reaching out passes the rules too
Getting started
Bring one workflowthat already hurts
Rough notes are enough. No requirements document, no process map, no company-wide AI plan.
What to send
The workflow
What starts it, what finishes it, which handoffs make it slow.
One hard rule
The thing the AI must never do.
The system edge
The database, SaaS, or internal API it reads or writes.
What comes back
A short memo, before any commitment:
- Fit or not — if a lighter tool is enough, we say so
- A first definition: trigger, finish line, rules, approvals
- A sample of the run record you would inspect
Before you buy
Fit
Pick one operation
We map it into a first definition together. If it does not fit, that is the answer.
Month 1
Production
Core workflow live
Schema, integration, core operations — about 2 person-weeks of build.
Month 2
Steady state
Exceptions and routine
External edges, exception paths, monitoring, and the runbook.
Pricing
Flat rates.No token meter.
A plan buys one workflow running under your rules. Busy months queue and retry inside the plan — they do not bill.
Starter
$300/month
- One workflow system
- Definition, rules, approvals, and run records
- Standard throughput; no metered overage
Pro
×1$1,000/month
- Everything in Starter
- More queueing and retry capacity
- More workflows and volume
Enterprise
Custom
- Multiple workflows under the same commit control
- Security and procurement review before rollout
- Workflow design review with us
Give AI one workflow.It can't break your rules.
Rough notes are enough: what starts it, one rule that cannot break, the system it touches. A short memo comes back — fit or not, a first definition, a sample run record.