Community To Enterprise Migration
Most teams do not adopt AxonFlow in one step. They start in Community, prove that the control plane helps real workflows, then hit the moment where local validation is no longer enough.
This guide explains that transition in practical terms. It is written for engineers and platform teams who need to decide when to stay on Community, when to use Evaluation, and when Enterprise becomes the right operating model.
The Three Stages
Stage 1: Community
Community is the best place to:
- wire AxonFlow into one or two applications
- validate SDK calls and request flows
- test MCP connectors, policy enforcement, and orchestration
- observe the control plane locally with Prometheus and Grafana
Stage 2: Evaluation
Evaluation is the bridge from “it works on a laptop” to “we can run a serious pilot.” It raises limits and turns on selected governance features, including:
- higher policy and provider limits
- higher execution and SSE limits
- approval queues
- policy simulation
- evidence export
Stage 3: Enterprise
Enterprise becomes the right answer when the organization needs:
- portal-backed operations
- identity and provisioning
- broader enterprise connectors
- Bedrock or custom provider operations
- long retention and stronger operational guarantees
The Signals That You Have Outgrown Community
Community is usually no longer enough when one or more of these are true:
- more than two governed connector estates are needed
- your team needs more than two configured providers
- approval queues are part of the intended workflow
- a compliance or security team wants simulation and evidence, not just logs
- the platform is moving from one engineer’s project to a shared internal service
That is the moment Evaluation becomes valuable. It is not only an upsell tier. It is the tier where production-readiness validation becomes realistic.
What Changes Operationally
| Area | Community | Evaluation | Enterprise |
|---|---|---|---|
| Tenant policies | 20 | 50 | unlimited |
| Organization policies | 0 | 5 | unlimited |
| LLM providers | 2 | 3 | unlimited |
| Pending approvals | 5 | 100 | unlimited |
| Policy simulation | no | yes, limited | yes |
| Evidence export | no | yes, limited | yes |
| Protected portal workflows | no | no | yes |
| HITL approval queue | no (blocks, no queue) | yes, 24h expiry, 100 pending | yes, unlimited |
| Identity and SCIM | no | no | yes |
A Practical Migration Pattern
Community to Evaluation
Move to Evaluation when the engineering team needs to prove:
- approval-driven workflows actually work end to end
- governance changes can be simulated before rollout
- the control plane still behaves well under a more realistic workload
This is usually the step that helps an engineer make the internal case for broader adoption.
Evaluation to Enterprise
Move to Enterprise when the platform is no longer only an engineering experiment and becomes part of a real operating model:
- shared across teams
- connected to identity systems
- expected to satisfy procurement and compliance review
- expected to support broader connectors and provider operations
What Senior Engineers Usually Need To Tell Their Stakeholders
At large organizations, the internal conversation is rarely “does the tool exist?” It is usually:
- can we operate it responsibly?
- can security review it?
- can multiple teams share it?
- can we route real business workflows through it without ad hoc glue?
Community proves the developer value. Evaluation proves production-readiness potential. Enterprise proves organizational fit.
