GOVERNED WORK. YOUR SCALE.

Scale the work.
Keep the proof.

Keep the coding agents your engineers already use. Decapod gives their work clear ownership, defined boundaries, and evidence tied to the exact code delivered. Local is free. Cloud makes the governance database available across the team, with managed access, transparent licensing, and usage controls.

01 / LOCALAvailable now

Decapod Local

Free forever

Your repository. Your agents. No subscription.

  • Repo-native governance with a local database
  • Governed tasks, boundaries, and durable context
  • Global engineering Constitution with sensible defaults
  • Workspaces, handoffs, and commit-bound evidence
Install for free

No account, payment details, or Cloud subscription needed.

02 / CLOUDComing soon

Decapod Cloud

UNDER WRAPSCloud pricing reveal coming soon

Monthly or annual billing

A shared governance database with managed access for engineering teams.

  • Live governance data shared across engineers and coding agents
  • Shared context, explicit ownership, and evidence across machines
  • Google or GitHub sign-in with verified repository identity
  • One identity across organizations, with repository-specific access
  • Cloud Admin for team access, spending controls, usage alerts, and billing

Cloud enrollment opens soon. Prices and included allowances will be disclosed before purchase. Paid overages are off by default and require separate admin approval and a spending cap.

Beyond 10 repositories or 25 contributors? Custom pricing

TEAM PRICING

Built for your team.
Priced for your scope.

See how team size, repository access, and billing terms affect your subscription. Coding agents never add seats.

2+0%
3+2% 6+4% 106%
5+2%
5+2% 10+4% 20+6%

Each person assigned to a repository counts as one paid assignment. Volume discounts also reflect distinct people across your team.

Volume savings from2%
Custom pricing
YOUR TEAM CONFIGURATION

10

paid assignments across repositories

2 repositories × 5 contributors each

Billing period
Cloud subscription

Prices and included usage allowances will be published before enrollment. Paid overages require an admin opt-in and a spending cap.

CLOUD CAPACITY

Usage you can see.
Costs you can trace.

See usage across transfer, compute, storage, and request traffic. Set alerts and stricter operating limits for each category. Included allowances and platform safeguards still apply. Paid overages remain disabled until an authorized admin opts in and sets a spending cap.

Included by default

Every Cloud subscription includes published resource allowances.

Limits & alerts

Receive early warnings and set stricter operating limits in Cloud Admin.

Overages are opt-in

Only an authorized admin can enable paid excess usage and set its spending cap.

What counts as cloud usage?

Set alerts and operating limits for all four categories. Alerts never authorize charges, and customer limits cannot expand purchased allowances or override service safety controls.

Network transfer

Set transfer limits and alerts for outbound usage, including exports and large responses.

Measured transfer · included allowance at launch

Compute & operations

Set workload limits and alerts for database operations and request processing.

Measured work · included allowance at launch

Retained data

Get alerts as your database or evidence storage fills, and set retention-related usage limits.

Retained storage · measured over time

Request pressure

Set rate and concurrency alerts and stricter limits; service safety controls still apply.

Protective limits · independent of billing
No surprise overage charges.

Paid overages are off by default. Billing admins can review published rates, approve excess usage, and set a spending cap. Without approval, new work beyond included limits is throttled or declined without extra charges. Approved excess use is itemized by resource. Alerts and operating limits never grant billing permission.

Resource allowances and overage rates will be published before billing opens. Monthly consumption and retained storage have different measurement periods.

GOOD TO KNOW

Clear terms.
Real control.

Clear answers on licensing, usage, and approvals.

Do we need to change our coding agents?

No. Keep Codex, Claude Code, Cursor, Antigravity, or a combination. Your engineers keep working in those tools; the agents call Decapod for coordination and validation. Each call exits when finished, with no resident Decapod service.

What is a contributor–repository assignment?

One human assigned to one repository is one paid assignment. The same human assigned to two repositories uses two assignments. Contributor-volume savings count distinct people only once per customer.

Do coding agents count as seats?

No. Agents, subagents, and worktrees are not additional human seats. Their Cloud activity still consumes measured resources.

How does workforce sign-in work?

Sign in with Google or GitHub. A single person can belong to multiple organizations, with explicit repository-specific access and paid assignments. GitHub repository linking requires verification of the corresponding GitHub identity.

How are subscription savings calculated?

Repository count and distinct contributors each determine a volume tier. The preview shows the minimum for your selection; final pricing uses verified assignments. Annual billing adds 8 percentage points to volume savings, up to 20% total on the base subscription. Resource overages receive no discounts.

Can we set limits and alerts for each resource?

Yes. Cloud Admin supports configurable limits and warnings for network transfer, compute and operations, retained database/evidence storage, and request pressure. These settings can warn you early or restrict your own usage; they cannot raise included allowances or bypass platform safety limits. Alerts never authorize billing.

Will Cloud charge me automatically if I exceed a resource limit?

No. Paid overages are disabled by default. Without your organization's authorized admin explicitly enabling them in Cloud Admin, new usage beyond included limits is throttled or declined with no overage charge. Admins can opt in after reviewing disclosed per-resource rates and setting a spending cap. Only authorized excess usage is billed, itemized by resource.

What will we know before subscribing?

Cloud prices, included resource allowances, and any excess-use rates will be disclosed before enrollment. Charges for excess use are off by default and require separate approval from an authorized billing admin, with a spending cap.

What if we're bigger than the sliders?

Talk with sales for more than 10 repositories, more than 25 contributors per repository, or specialized deployment and capacity needs.

SAME AGENTS. CLEAR BOUNDARIES.

Start locally.
Grow with Cloud.

Start with Decapod Local at no cost. Add Cloud when your team needs a shared governance database, managed repository access, and centralized usage controls.

Read the quickstart