Start free. Scale when the automation proves its value.
Automate a first process or run it across the company. Clear monthly limits, with model spend included.
Every plan includes rehearsal mode, policy enforcement, run evidence and audit history. Need uncapped volume? See Enterprise.
Build one automation and run it against your own systems.
- Runs
- 100 per month
- Model spend
- $5 per month
- Build turns
- 100 per month
- Live automations
- 1
- Dedicated database
- Pooled with row-level security
- Every guardrail, including the forbidden list
- Full audit trail and run traces
- The build agent, against your own schema
Several automations in production, with approvals and audit.
- Runs
- 2,000 per month
- Model spend
- $50 per month
- Build turns
- 500 per month
- Live automations
- 10
- Dedicated database
- Pooled with row-level security
- Approvals with business roles
- Scheduled and webhook triggers
- Boundlane Exchange, the template marketplace
Production volume, SSO, and the option of a dedicated database.
- Runs
- 20,000 per month
- Model spend
- $300 per month
- Build turns
- 3,000 per month
- Live automations
- 50
- Dedicated database
- Available
- Single sign-on with your own IdP (OIDC; SAML by arrangement), and SCIM provisioning
- Optional dedicated database
- Externally anchored audit chain
On these plans, model spend is included in the price and enforced as a ceiling, not billed on top. At the limit, builds and runs stop rather than continuing onto an invoice — no usage is metered, and nothing is passed through at cost. Enterprise is the plan where they do not stop.
Company-wide governance, without a ceiling.
Team and Business stop at their limits. Metered rather than capped — a run is never stopped by a counter. Dedicated database, BYO model endpoint. Usage is measured and settled against a negotiated agreement.
With it: a dedicated database, your own model endpoint, negotiated support terms, and deployment in your own cloud account scoped individually. Priced against volume and isolation rather than seats.
Questions worth answering first
Work stops. A run or a build turn is refused with a quota error rather than run and charged for, the counters reset at the start of the next calendar month, and moving up a plan raises the ceiling immediately. Enterprise is the exception, and deliberately so: stopping a payment run because a counter tripped is a worse outcome than a conversation about an invoice.
The platform and the model spend both. There is no separate model bill, no seat count and no charge for a run that was refused. What the price does not include is more than the plan says: the model-spend figure is the most a workspace can consume, not a starting balance.
Because it is the cost that varies with what your automations do rather than how many you have. A run that reads three records and one that reads three thousand are the same run and very different money, so both are counted.
No. A deployment on Vercel authenticates to the AI Gateway with the token the platform injects. Bring your own model endpoint on Enterprise if your data cannot leave a boundary you control.
One message to the build agent and everything it does in response — reading your schema, editing the package, running the promotion gate. Building an automation typically takes a handful; refining one takes a few more.
On Business and Enterprise, your data can live in its own dedicated database rather than a shared one, and Enterprise can bring its own model endpoint. Deployment into your own cloud account is something we scope individually with Enterprise customers — the install tooling exists and a deployment can be planned and verified from outside your network, and the operating model is agreed per customer rather than sold off a page. Talk to us early if you need it.