Simple plans for app balances at every stage

Each newly completed ordinary transfer or Console balance adjustment counts once. Exact idempotent retries, validation failures, insufficient-balance failures, reads, reversals, and XferAPI-managed expiration work do not consume monthly quota.

Every authorized API-key request uses the Workspace-shared token bucket, including reads, metadata, lists, batch reads, successful calls, and business failures after authorization. Console transfers, adjustments, and reversals use the same bucket; ordinary Console page reads and control-plane actions do not. The requests-per-minute value is sustained refill, while burst is immediate capacity; neither is monthly quota.

No. A new workspace starts on Free without a payment card. You can choose a paid plan later from the Console.

It keeps working. Existing workspaces, ledgers, assets, platform account definitions, and complete account ranges remain available and editable. The current plan only blocks creation of another resource while its relevant limit is reached. Traffic quota, rate, burst, and entries per transfer change when the downgrade takes effect.

A user may create up to two Free workspaces they own. Workspaces joined as a member do not count. Existing workspaces remain operational if later downgrades leave that owner above two, but another Free workspace cannot be created while the owner is at or above the limit.

No. Managed private deployment has an agreed environment and commercial scope. Contact sales to discuss deployment, upgrades, support, and operating boundaries.