Budget caps before work starts
Every run shows a preflight estimate and a hard cap before Boetica touches code. Work stops at the cap; it never overruns silently into an invoice.
Pricing
Pricing follows accepted, proof-backed work.
This is a transparency page, not a price list. Boetica does not publish fixed prices until packaging is approved — so instead of a fabricated number, here is exactly how the commercial model works: budget caps before any work starts, evaluation measured on the artifacts you keep, and procurement proof scoped to the path you validate.
How pricing is decided
Four commitments define how Boetica charges, before any number is on the table. They are the same defaults every run inherits.
Measured on accepted, proof-backed work
Commercial evaluation tracks the artifacts you keep — accepted PRs, accepted remediations, created-app milestones, evidence packets — plus the model and tool usage behind them.
Human merge is a default, not an add-on
Review, branch protection, budget caps, and human merge are governance defaults included on every path. Safety is not a paid tier.
Procurement proof is part of enterprise review
Evidence rooms package signed scorecards, trust-boundary attestations, security documents, and acceptance artifacts under scoped, expiring access — before a contract, not after.
How access works
Three ways teams engage. Each describes scope and what is included — never a price — and each opens onto a proof surface you can inspect right now.
Evaluation
Teams validating one proof path end to end
- One scoped app, repo, finding, or trust-boundary review
- A hard budget cap set before any work starts
- A signed evidence packet for the evaluated workflow
- A procurement path if a security review is required
Platform
Teams running governed create, continue, and remediate work
- Create, Continue, and Remediate workflows on one trust boundary
- Governance, branch protection, and reviewer controls
- Evidence rooms and signed, re-verifiable packets
- Run API access under policy gates and budget caps
Enterprise
Organizations requiring procurement, identity, and evidence controls
- A scoped procurement evidence room
- SSO/SCIM and data-governance review
- BYOK posture review where applicable
- Protected security artifacts under scoped, expiring access
What is metered
Commercial evaluation tracks the artifacts you keep — not opaque tokens. Every unit below is something you can open and inspect after the work runs.
- Accepted PR
- A bounded, reviewable pull request your team accepts and merges under branch protection.
- Accepted remediation
- A finding closed by a patch PR with a signed evidence packet and control-family mapping.
- Created-app milestone
- A full-stack app scaffold, preview deploy, or governed milestone produced from a brief.
- Evidence packet
- A KMS/Sigstore-signed, re-verifiable proof packet attached to a change.
- Evidence room
- A scoped, expiring procurement room assembling scorecards, attestations, and security docs.
- Model and tool usage
- The underlying model and tool calls a run consumes, shown in the preflight estimate before the cap.
How budget caps work
A budget cap is a ceiling set before work begins, not a target. Here is the order it runs in, every time.
- Preflight estimate
Before a run starts, Boetica estimates the model and tool usage the task will require and shows it.
- Hard cap set
You set a hard cap for the run. It is a ceiling, not a target — most runs finish well under it.
- Work stops at the cap
If a run reaches the cap, it stops and reports where it got to. It never silently exceeds the cap.
- You keep the artifacts
Whatever proof was produced — the PR, the evidence packet, the scorecard — is yours to inspect and keep.
What procurement gets
Enterprise review receives a scoped, expiring evidence room — not a static PDF pack. Everything in it is signed and re-verifiable.
- A scoped, expiring evidence room instead of a static PDF pack
- Signed benchmark scorecards with re-verifiable hash trails
- The sandbox trust-boundary attestation and red-team result
- Security documents: access, secrets, egress, retention, disclosure
- Control-family mappings (SOC 2 / NIST) on every security change
What we do not claim yet
Naming the limits is part of the proof. These are the things the public site deliberately does not claim until they are real.
No fixed public prices
There are no list prices, "starting at" figures, or per-seat numbers on this page until packaging is approved. Pricing is scoped to the proof path you evaluate.
No public customer logos
The site shows no customer logos or named case studies, because none are approved for public use yet. Proof here is artifact proof, not social proof.
No unearned certification claim
No public SOC 2, auditor, or certification status is claimed until it is real. Control-family mappings and signed evidence are shown instead.
Pricing — frequently asked
Why are there no prices on this page?
Because packaging is not approved for public list pricing yet, and a fabricated price would be a claim we cannot back. Pricing is scoped to the proof path you evaluate, and the commercial model — budget caps, accepted-work metering, and procurement proof — is explained in full here instead.
What does Boetica actually measure?
Accepted, proof-backed work: accepted PRs, accepted remediations, created-app milestones, evidence packets, evidence rooms, and the model and tool usage behind them. Every unit is an artifact you keep and can inspect, not an opaque token count.
How do budget caps protect me?
Every run shows a preflight estimate and takes a hard cap before Boetica touches code. Work stops when it reaches the cap and reports where it got to — it never overruns silently. Whatever proof was produced up to that point is yours to keep.
Is governance a paid add-on?
No. Human merge, branch protection, reviewer controls, and budget caps are defaults on every access model. Safety is part of the platform, not an upsell tier.
What does procurement receive?
A scoped, expiring evidence room rather than a static PDF pack: signed benchmark scorecards with re-verifiable hash trails, the sandbox trust-boundary attestation, security documents, and control-family mappings on every security change. Walk one on the procurement page.