Skip to main content

Enterprise Overview

AxonFlow Enterprise is for organizations that need AxonFlow to operate as a serious internal platform, not just a runtime embedded in one application.

Community gives teams a strong technical foundation. Enterprise adds the operational, identity, governance, and regulated-workflow capabilities that usually become necessary as usage spreads across teams, environments, and business-critical workflows.

What Enterprise Adds​

Customer-Portal Operations​

Enterprise adds web-based operational surfaces for areas such as:

  • Approvals and human review workflows -- a queue-based interface for HITL (human-in-the-loop) approval gates, where designated reviewers can approve or reject pending workflow steps.
  • Policy and governance administration -- create, edit, and manage tenant policies through the portal instead of API calls, with policy simulation and impact reporting to preview changes before they go live.
  • Provider and connector operations -- runtime LLM provider management (add, update, disable providers, configure cost rates, monitor health status) and connector configuration.
  • Audit and compliance dashboards -- audit log search and review, compliance summaries, and evidence export for regulatory frameworks.
  • Usage and operational visibility -- token usage, cost breakdowns, and request volume across tenants and providers.

This matters once AxonFlow needs to be usable not only by application engineers, but also by platform operators, compliance reviewers, and internal stakeholders.

Enterprise Identity​

Enterprise adds organization-scale identity features:

  • Single Sign-On (SSO) -- portal authentication through the organization's existing identity provider, so users log in with their corporate credentials instead of separate AxonFlow accounts.
  • SAML 2.0 -- the protocol layer supporting SSO, with provider-specific integrations for Okta, Azure AD (Entra ID), Auth0, and any custom SAML 2.0 provider.
  • SCIM 2.0 provisioning -- automated user lifecycle management (provisioning, deprovisioning, group sync) driven by the organization's identity provider. Includes group-to-role mapping so IdP group memberships automatically translate to AxonFlow role assignments.

Together, these give security and IT teams the identity controls they need before rolling AxonFlow out beyond a small engineering group.

Regulated Workflow Modules​

Enterprise adds dedicated compliance modules for regulated industries:

  • EU AI Act -- conformity assessments, accuracy tracking, and 10-year audit retention. Supports the risk classification and documentation requirements of the EU AI Act for high-risk AI systems.
  • SEBI AI/ML -- audit exports, 10-year audit retention (AuditRetentionDays=3650 at the Enterprise tier level), and compliance dashboards for organizations regulated by the Securities and Exchange Board of India. Supports string-based tenant IDs for multi-entity securities firms.
  • RBI FREE-AI -- kill switches, board reports, and incident management for Indian banking organizations regulated by the Reserve Bank of India.
  • MAS FEAT -- AI system registry, assessment workflows, and bias monitoring for Singapore financial services organizations regulated by the Monetary Authority of Singapore.

Each module includes protected API endpoints for compliance data export, dashboard data, and workflow management. Compliance audit exports are Tier 3 (admin) operations available through the API rather than through SDKs, following the principle that compliance exports are one-time or periodic admin actions rather than per-request operations.

Expanded Operational Surface​

Enterprise is also where teams typically expect:

  • broader enterprise connector support
  • customer-portal management flows
  • protected operational documentation
  • stronger deployment and administrative guidance

When Community Stops Being Enough​

Organizations usually move from community or evaluation into enterprise when one or more of these become true:

  • multiple internal teams need to use the platform
  • approvals, portal workflows, or admin operations are needed
  • security requires centralized identity and user lifecycle controls
  • regulated workflows need more than baseline audit and policy foundations
  • enterprise rollout needs stronger operational packaging and guidance

How To Use This Page​

Use the public enterprise pages to understand whether the enterprise product is the right fit. If the answer is yes, the protected enterprise docs are where the detailed setup, operational, and admin guidance lives.

The most useful public pages to read alongside this one are:

Last updated on