AxonFlow Hosted Service
Start from the Hosted Starter plan without running Docker. Verify your email in the Portal, review the plan, and continue to Checkout. AxonFlow creates your tenant after you consume the one-use verification link. Governed requests require an active Hosted Starter subscription, starting at $9.99 per month. New subscriptions do not require a license token.
Self-hosted AxonFlow Community remains free.
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. Self-hosted Community is available now.
Hosted Starter covers a small team and a limited workflow set. Use a paid Enterprise proof of concept when the workflow needs more scope, written controls, or a dated production decision.
Quick Start
1. Verify your email and review Checkout
On the Hosted Starter plan, select Start with email verification. The Hosted Portal emails a one-use link that expires in 15 minutes. Open it and confirm the address. Only then does AxonFlow create or resume your tenant and owner session. The link request itself returns an accepted response without revealing whether an account exists; it does not create a tenant or return an API secret.
Review the plan and limits shown in the Portal, then select Continue to secure Checkout. The Portal creates a tenant-bound checkout from your verified owner session. A browser return alone does not grant paid access; refresh the Portal payment status after the signed payment update arrives.
2. Link an SDK or API client
After payment is active, use the Portal's Link your client section. Download and run its Hosted API link command, then enter the displayed 10-character code in the Portal. By default the command saves the approved client's clientId, clientSecret, and endpoint in ~/.config/axonflow/hosted-api.json with owner-only permissions. Use those values in the SDK examples below; keep the file and secret private. Each linked client can be revoked separately; do not paste a tenant ID or payment secret into Checkout.
The older POST /api/v1/register endpoint is a legacy compatibility path, not the website-first signup. When the paid gate is enforced and legacy registration is disabled, it returns HTTP 410. Existing registration credentials continue to authenticate; a documented migration window can temporarily enable the legacy route.
3. Configure your SDK
Set AXONFLOW_TRY=1 to auto-connect, or configure the endpoint manually:
- Python
- Go
- TypeScript
- Java
from axonflow import AxonFlow
# Use credentials from the approved client link
client = AxonFlow(
endpoint="https://try.getaxonflow.com",
client_id="cs_your-tenant-id",
client_secret="your-secret",
)
Or auto-connect with environment variables:
export AXONFLOW_TRY=1
export AXONFLOW_CLIENT_ID=cs_your-tenant-id
export AXONFLOW_CLIENT_SECRET=your-secret
# With AXONFLOW_TRY=1 set, no endpoint needed
client = AxonFlow(
client_id="cs_your-tenant-id",
client_secret="your-secret",
)
client := axonflow.NewClient(axonflow.AxonFlowConfig{
Endpoint: "https://try.getaxonflow.com",
ClientID: "cs_your-tenant-id",
ClientSecret: "your-secret",
})
Or with AXONFLOW_TRY=1:
// With AXONFLOW_TRY=1 set, endpoint auto-connects to try.getaxonflow.com
client := axonflow.NewClient(axonflow.AxonFlowConfig{
ClientID: os.Getenv("AXONFLOW_CLIENT_ID"),
ClientSecret: os.Getenv("AXONFLOW_CLIENT_SECRET"),
})
import { AxonFlow } from '@axonflow/sdk';
const client = new AxonFlow({
endpoint: 'https://try.getaxonflow.com',
clientId: 'cs_your-tenant-id',
clientSecret: 'your-secret',
});
Or with AXONFLOW_TRY=1:
// With AXONFLOW_TRY=1 set, endpoint auto-connects to try.getaxonflow.com
const client = new AxonFlow({
clientId: process.env.AXONFLOW_CLIENT_ID,
clientSecret: process.env.AXONFLOW_CLIENT_SECRET,
});
AxonFlow client = AxonFlow.create(AxonFlowConfig.builder()
.endpoint("https://try.getaxonflow.com")
.clientId("cs_your-tenant-id")
.clientSecret("your-secret")
.build());
Or with AXONFLOW_TRY=1:
// With AXONFLOW_TRY=1 set, endpoint auto-connects to try.getaxonflow.com
AxonFlow client = AxonFlow.create(AxonFlowConfig.builder()
.clientId(System.getenv("AXONFLOW_CLIENT_ID"))
.clientSecret(System.getenv("AXONFLOW_CLIENT_SECRET"))
.build());
4. Send your first request
- Python
- Go
- TypeScript
- Java
import asyncio
async def main():
result = await client.proxy_llm_call(
"", "What is the capital of France?", "chat"
)
print(f"Success: {result.success}")
asyncio.run(main())
result, err := client.ProxyLLMCall("", "What is the capital of France?", "chat", nil)
if err != nil {
log.Fatal(err)
}
fmt.Println("Success:", result.Success)
const result = await client.proxyLLMCall('', 'What is the capital of France?', 'chat');
console.log('Success:', result.success);
ClientResponse result = client.proxyLLMCall(ClientRequest.builder()
.query("What is the capital of France?")
.requestType(RequestType.CHAT)
.build());
System.out.println("Success: " + result.isSuccess());
Signup and client credentials
The Portal requests an email verification link with POST /api/v1/auth/hosted/signup/request-link. Within the outer per-IP limit described below, a syntactically valid request returns HTTP 202 without disclosing account existence or creating a tenant. Consuming the one-use link creates or resumes the verified owner and tenant. If the offer is available, the owner starts Checkout from the Portal; the tenant is taken from the signed-in session, not from a form field.
Once paid access is active, each API or SDK installation uses the Portal's owner-approved device link to obtain its own client credential. The linked secret stays on that client and is not returned to the browser. Revoke an old link from the Portal and approve a new link to replace it. The legacy registration route remains available while paid enforcement is off. Once enforcement is on, it returns 410 unless an operator explicitly enables it for a documented migration window.
Rate Limits
| Limit | Value | Scope |
|---|---|---|
| Governed write events per minute | 25 | Per tenant |
| Governed write events per UTC calendar month | 1,000 | Per tenant |
| New workflow cases per UTC calendar month | 100 | Per tenant |
Governed request limits return HTTP 429 when reached. Signup link requests have two separate controls: the Portal's outer per-IP limiter returns HTTP 429 after five requests in 15 minutes; inside that limit, the per-email throttle keeps the same HTTP 202 response for a syntactically valid request even when it does not send another link. A 202 does not guarantee delivery or reveal account state.
Available LLM Models
The shared hosted service supports bounded evaluation using its configured local model. Model availability and response time depend on the deployed service configuration; check the Portal and current service status before planning a test.
Want to test with your own API keys? Deploy AxonFlow self-hosted and configure any supported LLM provider.
Limitations and Disclaimers
try.getaxonflow.com is a shared hosted service. Governed requests require an active paid entitlement.
- No contractual SLA: availability is best effort unless covered by an Enterprise agreement.
- Data scope: review the hosted Privacy Policy before sending personal, regulated, production, or sensitive data.
- Paid entitlement: unpaid, past-due, canceled, disputed, and allowance-exhausted requests are blocked.
- Starter limits: the launch envelope is 2 verified Portal people, 1,000 governed events and 100 new cases per UTC calendar month, at most 100 retained cases, 1 integration, and 30-day retention.
- Workflow scope: Hosted Starter includes limited governance, FinCrime, payment exception, and support refund workflows.
- Execution boundary: workflow actions are proposals or synthetic results. The shared service does not move money or write to a customer system.
- Higher scope: teams needing more capacity or controls use a paid Enterprise proof of concept or design partnership.
For a free deployment, run self-hosted Community. For higher hosted scope, contact [email protected].
What's Next
Use Hosted Starter for its documented bounded evaluation. Move to one of these paths when the workload exceeds that boundary:
- Self-host AxonFlow Community Edition — runs entirely on your infrastructure, keeps data within your boundary. The recommended path for any real workload.
- Community Edition with an Evaluation License — for production use with real users or clients on the open core; adds production-fit limits and license-gated features. Free 90-day evaluation license.
- AxonFlow Enterprise — production-grade governance, regulatory-grade controls, SLOs, and contractual commitments suitable for regulated industries. Contact [email protected].
Other resources:
- Regulated environments — Assessment guide for regulated industries
- SDK documentation — Python | Go | TypeScript | Java
FAQ
Can I use my own API keys?
Not on try.getaxonflow.com — it runs Ollama only. Deploy self-hosted to use OpenAI, Anthropic, Azure, Gemini, Mistral, or Bedrock.
How do I migrate to self-hosted?
- Deploy AxonFlow locally:
docker compose up -d - Change your SDK endpoint from
try.getaxonflow.comtolocalhost:8080 - Your policies and configurations transfer — only the endpoint changes
What happens when access or a client credential expires?
An expired or revoked client credential stops working (HTTP 401). The owner can link a new client or rotate a legacy service credential in the Hosted Starter Portal. A lapsed subscription blocks governed requests until paid access is restored. Expired case data follows the documented 30-day primary-retention and seven-day encrypted-backup window.
Is my data shared with other tenants?
No. Each tenant has a unique UUID (cs_ prefix), and customer rows are protected by forced PostgreSQL row-level security and server-resolved organization scope. Other tenants cannot read your policies, audit logs, workflow cases, or query history. The infrastructure is shared, so submit only the permitted typed data documented for Hosted Starter workflows.
Each approved client has its own credential bound to the verified tenant. Older registration responses used tenant_id as a compatibility field for the credential identifier; do not use a client-provided tenant ID to select another organization's data or billing account.
Operational Readiness Checklist
Before relying on this page in a production rollout, pair it with the core operations docs:
- Deployment Mode Matrix for self-hosted, Evaluation, Enterprise, SaaS, and In-VPC fit
- Failure Modes And Recovery for degraded-provider, connector, approval, and runtime behavior
- Capacity Planning for sizing and growth signals
- Community vs Evaluation vs Enterprise for limits, support surfaces, and upgrade triggers
