Pricing for evaluation and rollout

Start with a complete technical trial, choose Team for managed use, or scope an Enterprise deployment.

Trial and Team limits match the application plan catalog. Enterprise terms are agreed before purchase. Taxes are shown at checkout.

Deployment, access and retention

Trial: Includes real allow, deny and human approval workflows. Retries and denied calls count toward the allowance; discovery does not. Built-in packs do not count as custom policies.

Team: Human approvals and audit exports included. Add or remove servers from Billing at any time; Paddle prorates the change. Subscriptions that started at $99 / month keep unlimited servers. For sizing: five developers × 80 calls × 22 workdays = 8,800 monthly calls; this is an example workload, not a plan cap.

Enterprise: Private infrastructure, support scope and any availability commitments are specified in your agreement. Contact the team with your deployment requirements.

Why we price by protected server

Each protected MCP server is a production system—a database, deploy pipeline or payment API—whose credential AgentGate holds and whose calls it authorizes. That is where the value is, so that is what Team counts. We do not charge per agent, because every agent should have its own identity for a clean audit trail. We do not charge per call, because a control you pay more to route through is a control teams learn to route around.

Plan your workload

For example, five developers making 80 calls on each of 22 workdays generate 8,800 monthly attempts. Team has no tool-call ceiling; per-agent rate limits protect service stability. Trial allows 1,000 attempts per UTC calendar month, including denied calls and retries. Built-in policies do not consume custom-policy slots.

Audit retention is enforced by the worker. Unresolved execution evidence is held for investigation. See the Trust Center for the data lifecycle.

Checkout, tax and confirmation

Team checkout runs through Paddle as Merchant of Record: Paddle collects payment details, calculates and remits applicable sales tax / VAT for the buyer's location, and issues the invoice; AgentGate does not run separate tax logic. A checkout confirmation and receipt are sent by Paddle on successful payment, and subscription state updates when AgentGate's backend verifies the signed Paddle webhook. "Fair-use gateway volume" on the Team and Enterprise plans is a qualitative expectation, not a metered or auto-enforced numeric cap; the billing schema stores no monthly call ceiling for these plans today, so unusually high volume is handled by direct contact rather than automatic throttling.

Moving from Team to Enterprise

1. Submit one workflow and the private-deployment requirements.
2. Review the gateway boundary, data lifecycle, operations owners and evidence report.
3. Agree scope and migration date; keep the existing deployment active until validation succeeds.