Saxeo Pro plans

Saxeo Pro is a four-tier subscription: Free, Pro, Private, and Business. A plan raises your limits, extends how long metadata is retained, unlocks capabilities, and adds support. It is billed in USDT, auto-debited from the same prepaid balance that pays for your compute.

Two things a plan is deliberately not:

• It does not change the price of compute. Every request is metered at list plus margin on every tier, the same rate on Free as on Business. A plan buys limits, retention, capabilities, and support, not cheaper compute. Free is a real pay-as-you-go tier, not a crippled trial.
• It does not change how private your prompts are. Signed receipts and privacy by default are on every tier, including Free. A plan gates access to the confidential (TEE-attested) execution path, never whether your prompt is protected at all.

The tiers

Fees are set by the deployment operator, so the authoritative numbers are always whatever GET /v1/billing/plans returns. The figures above are the standard pricing.

The three rows marked advertised are not enforced by the gateway today, and most of the capability rows are not either. Which gates actually exist today lists every row and says which side of that line it is on.

What each tier includes

The capabilities form a clean chain (Free is a subset of Pro, Pro of Private, Private of Business), so each capability is advertised from a specific tier and stays included above it. What the gateway actually refuses is the shorter list in the next section.

• Compliance audit packs and higher limits: Pro and up. Signed, content-free audit packs over your agent runs. Signed spend statements are listed alongside them but are not gated: they work on every tier.
• Confidential (TEE-attested) execution, the double-blind lanes, and region pinning: advertised at Private and up. These are three different guarantees and only one of them hides your prompt from the machine running the model:
  • The confidential tier runs on hardware-attested Intel TDX, where the host provably cannot read the prompt and the proof travels in your receipt.
  • The double-blind lanes hide who is asking from the vendor. The vendor's servers still process your plaintext prompt. They are not confidential execution, and they are not host-blind.
  • Region pinning is honored only when the pin matches the region this deployment declared, and refused otherwise.
• Vault issuer tools, org seats, and OpenTelemetry export: Business. Issue and manage assets in Saxeo Vault, add team members, and export metering telemetry to your own observability stack.

Which gates actually exist today

The table above is what a plan advertises. Enforcement is a separate, smaller thing, and the difference is worth stating plainly rather than implying the whole table is wired up.

Two capabilities are checked in the gateway, and only when the operator sets SAXEO_PLAN_GATES_ENFORCED=true. With it off, plans are billable and both checks are skipped, the same staged rollout as billing enforcement itself.

If you are on a plan for a capability in the No column, you are paying for an entitlement the gateway does not currently police. That is a gap we are closing by adding the checks, not by softening this page: when a row flips to Yes it flips here and in src/plans.rs in the same change.

Discovering plans

GET /v1/billing/plans is public, so an agent or anyone evaluating Saxeo can read the catalog before holding any credential.

curl https://www.saxeonetwork.tech/__api/v1/billing/plans

{
  "currency": "USD",
  "paid_in": "USDT (auto-debited from your prepaid balance)",
  "note": "Compute is metered at list plus margin on every tier. A plan buys limits, retention, capabilities, and support, not cheaper compute. Signed receipts and privacy-by-default are universal.",
  "gates_enforced": false,
  "plans": [
    {
      "id": "private",
      "name": "Private",
      "fee_micro_usd": 199000000,
      "fee_usd": 199.0,
      "retention_days": 90,
      "rate_limit_per_min": 600,
      "max_concurrent_sandboxes": 12,
      "features": {
        "signed_receipts": true,
        "privacy_by_default": true,
        "metered_compute": true,
        "confidential_and_double_blind": true,
        "region_pinning": true,
        "audit_packs": true,
        "vault_issuer": false,
        "org_seats": false,
        "otel_export": false
      },
      "support": "email support"
    }
  ]
}

Your subscription

GET /v1/billing/subscription (session-authed) returns the plan you are on, when the current period ends, whether it renews, the full plan spec, and your balance.

{
  "plan": "private",
  "period_end": "2026-10-01T00:00:00Z",
  "auto_renew": true,
  "spec": { "id": "private", "name": "Private", "fee_usd": 199.0, "...": "..." },
  "balance_micro_usd": 250000000
}

Subscribing and changing plans

POST /v1/billing/subscription with { "plan": "pro" | "private" | "business" | "free" } (session-authed).

curl https://www.saxeonetwork.tech/__api/v1/billing/subscription \
-H "Authorization: Bearer $SAXEO_SESSION_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "plan": "private" }'

A paid plan charges its full monthly fee from your prepaid balance immediately and starts a fresh 30-day period. If your balance cannot cover the fee, the request returns 402 with the amount owed and your current balance; top up and try again. There is no proration when you switch plans, and the current period is not refunded.

Switching to "free" cancels auto-renew. Your current plan keeps its capabilities until the period ends, then drops to Free.

Cancelling

POST /v1/billing/subscription/cancel (session-authed) turns off auto-renew. The plan keeps its capabilities until period_end, then the renewal worker drops it to Free. There is no refund of the current period. You can also do all of this from the portal under Subscription.

Honest scope

A plan is a billing and entitlement record on this gateway. It changes your limits, retention, and which capabilities you can reach. It does not change the privacy contract: prompts, completions, and submitted code are never persisted on any tier, and every plan artifact, like every Saxeo artifact, is metadata only.