AxonFlow Hosted Starter

Hosted Starter is the entry paid plan for governance on try.getaxonflow.com.

Starting price: $9.99 USD per month. Subscription renews monthly until canceled. Taxes can be added at checkout.

Self-hosted AxonFlow Community remains free. Hosted use requires an active paid entitlement after the launch gates described below are accepted.

Availability is controlled operationally

The Portal exposes signup and tenant-bound Checkout, but the offer may remain limited during staged rollout. Review the live Portal before relying on purchase availability. A signup form or Checkout browser return alone is not proof of an active paid entitlement.

Included value

The first paid hosted tier includes a useful, limited workflow set:

• governance checks for supported HTTP, SDK, MCP, and plugin entry paths
• FinCrime case evaluation
• payment exception handling
• support refund handling
• a person-authenticated Hosted Starter Portal for cases, independent review, member access, and service credentials
• secure Stripe billing portal access for invoices, payment method changes, and cancellation

The launch envelope is:

Limit	Hosted Starter
Seats	2
Governed events	1,000 per UTC calendar month
Governed-event burst	25 per minute
New cases across included workflows	100 per UTC calendar month
Retained cases	100 at one time
Standard integrations	1
Audit retention	30 days

The governed-event allowance and burst limit are runtime configuration. AxonFlow will not activate checkout unless the deployed values match an accepted launch configuration. The billing status response is the runtime source of truth for the limits applied to a tenant. Deleting a case does not restore either monthly allowance.

Teams that need more seats, workflows, integrations, retention, or governed volume move to a paid Enterprise proof of concept or design partnership.

Activation flow

1. On the Hosted Starter plan, select Start with email verification.
2. The Hosted Portal emails a one-use link. Confirm the address shown by the link; consuming it creates or resumes the tenant and verified owner session.
3. Review the plan and limits in the Portal, then select Continue to secure Checkout. The Portal creates the subscription session for the signed-in owner's tenant. The buyer does not enter a tenant ID, price, or return URL.
4. A signed Stripe update activates the same tenant. A browser return alone does not grant access; refresh the Portal payment status if the update is pending.
5. Once paid access is active, approve the client-link code in the Portal. The linked SDK, API, or plugin client keeps its own credential locally, then retries the governed action.

The buyer does not copy a tenant ID into Stripe and does not paste a license token into a plugin.

An existing credential can still receive a payment-required response on an unpaid governed request:

{
  "error": "paid_entitlement_required",
  "message": "Hosted governance requires an active paid entitlement",
  "checkout_url": "/api/v1/billing/checkout",
  "checkout_method": "POST",
  "tenant_id": "cs_example"
}

For an existing authenticated client, the Agent also supports this compatibility checkout path:

curl -X POST https://try.getaxonflow.com/api/v1/billing/checkout \
  -u "$AXONFLOW_TENANT_ID:$AXONFLOW_CLIENT_SECRET"

The response contains the short-lived Stripe checkout_url. Open that URL to pay. Do not send a tenant identifier in the request body. New website signups use the Portal owner-session checkout path above.

An existing OpenClaw client can present the returned checkout URL once per session. New installations start from the website and use owner-approved linking after payment. Install the exact version in the current client-version manifest; OpenClaw 2.10.4 passed its npm/ClawHub release gates and fresh pinned host-install check. The plugin release does not change the separate offer-availability, payment, or owner-approval gates.

Hosted Starter Portal

The Hosted Starter Portal is the person-authenticated case and account surface. Request a single-use verification or sign-in link and use it within 15 minutes. The owner can invite one member or reviewer, manage linked client credentials, create and export retained cases, and remove the second person. A reviewer can decide another person's proposed action but cannot approve their own proposal.

The three case modules accept bounded typed data and produce proposals or synthetic results only. Hosted Starter does not move money, retry a payment, issue a refund or credit, or write to a customer system. See Hosted Starter Portal and outcome workflows for the roles, data boundary, workflow journey, retention, export, and deletion behavior.

Billing status and Stripe billing portal

Read subscription state and enforced plan limits:

curl -X POST https://try.getaxonflow.com/api/v1/billing/status \
  -u "$AXONFLOW_TENANT_ID:$AXONFLOW_CLIENT_SECRET"

Create a secure Stripe billing portal session:

curl -X POST https://try.getaxonflow.com/api/v1/billing/portal \
  -u "$AXONFLOW_TENANT_ID:$AXONFLOW_CLIENT_SECRET"

The portal endpoint returns a short-lived portal_url. Use it to update the payment method, view invoices, or cancel renewal.

Renewal, payment failure, and cancellation

• A successful recurring invoice keeps the entitlement active through the paid billing period.
• A failed recurring invoice changes the entitlement to past_due; governed requests are blocked until Stripe reports active paid access again.
• Cancellation stops future renewal. Access continues only through the paid period reported by Stripe.
• A dispute marks the entitlement disputed and blocks hosted governance.
• A refund revokes the associated hosted entitlement.
• Existing one-time 90-day prepaid licenses remain valid until their recorded expiry. They do not need to repurchase early or paste a new token for the monthly plan.

Billing webhooks are ordered and idempotent. Older Stripe events cannot overwrite newer subscription state.

What counts as one governed event

One accepted request to any of these hosted write or decision paths counts as one governed event:

• /api/request
• /api/policy/pre-check
• /api/v1/decide
• /api/v1/mcp/check-input
• /api/v1/mcp/check-output

Retries use the same event identity and count once. Clients should send a stable X-Axonflow-Event-ID header for the logical action. X-Request-ID is accepted as a compatibility fallback. The OpenClaw plugin sends its tool call or run identity automatically.

Read-only billing status and Stripe billing portal requests do not count. The authenticated checkout request does not count.

When the monthly allowance is exhausted, the service returns HTTP 429 and does not run the governed operation.

HTTP, MCP, and SDK behavior

Hosted enforcement is fail closed:

• HTTP and SDK clients receive HTTP 402 before an unpaid governed operation runs.
• MCP clients receive JSON-RPC error -32042, HTTP 402, and the same checkout data.
• A client's general network-error or fail-open setting cannot convert an answered payment refusal into an allow decision.
• Paid tenants retain the configured per-minute burst guard in addition to the monthly allowance.

For correct retry accounting, API and SDK integrations should keep the same X-Axonflow-Event-ID when retrying a logical action.

Launch gates

The platform refuses checkout unless the security acceptance, workflow acceptance, exact module set, Stripe monthly price, and every required plan limit match the reviewed deployment configuration. A documentation publication cannot activate the offer.

Production activation follows a staged cohort rollout with a rollback switch. The deployment, live Stripe price, and public cohort remain operator-reviewed release actions.

Free self-hosted Community

Self-hosted Community does not use the hosted paid gate. Run it on infrastructure you control and point the client at your own endpoint:

export AXONFLOW_ENDPOINT=http://localhost:8080

Self-hosted limits and operations follow the Community deployment documentation rather than the Hosted Starter subscription.

Legacy prepaid users

The retired $9.99 for 90 days offer is no longer sold. A previously issued, unexpired, unrevoked prepaid entitlement continues to authorize its tenant until expiry. At expiry, the hosted API returns the standard payment-required response and the client can start a monthly subscription without changing tenants.

Install your Pro token

This section applies only to a valid legacy prepaid purchase. New Hosted Starter subscriptions do not issue or require a license token.

Existing prepaid users keep their current token configuration through expiry. Do not replace a working token with a monthly subscription token; monthly subscriptions do not issue one.

For OpenClaw, an existing token can remain in AXONFLOW_LICENSE_TOKEN or pluginConfig.licenseToken. Claude Code, Cursor, and Codex can keep their current AXONFLOW_LICENSE_TOKEN or existing token file. Status output labels this access as Prepaid Pro and shows its expiry.

If the token is lost, use the recovery path documented for the client. If the prepaid term has expired, use the authenticated Hosted Starter checkout action rather than requesting a replacement token.