Two adoption paths · One enforcement engine

Start open source. Scale into company operations.

Talon OSS enforces policy for AI use cases on supported model and action paths. Talon Enterprise is being designed to fit the identity, security, approval and production systems your organization already runs—without replacing the open-source policy, action or evidence engine.

Availability: OSS is Apache 2.0. The Enterprise integrations below are proposed, not released product features or commitments to support every named provider.

Editions

Complete core enforcement. Enterprise-scale operations.

Available · Apache 2.0

Talon OSS

A self-hosted, independently useful control plane. Start with one production AI use case and grow without an artificial licensed use-case limit.

Included in the open-source coreCompany/use-case policy · Cost limits · Policy-valid failover · Sessions · Supported exact HTTP actions and local approvals · Signed evidence and offline verification
Explore OSS code and releases →
Planned · In development

Talon Enterprise

Organizational integration and operating assurance for companies with identity providers, SOC teams, existing approval processes and multiple AI use cases.

Proposed extensionsCorporate OIDC and group lifecycle · SIEM integration · Existing approval workflows · Delegated operations · Supported DR and scale profiles · Commercial support
Discuss a design-partner pilot →

Enterprise never introduces a separate authorization/evidence engine. Local human approvals, exact-action semantics and signed evidence are not paid-only functions.

Planned Enterprise integrations

Fit the systems your company already operates.

01 · Identity

Corporate SSO and domain

OIDC with verified organization/issuer binding, mapped groups, separate operator and reviewer rights, and deprovisioning. An email suffix alone never confers access.

02 · Security

SIEM and SOC workflows

Route correlated enforcement and administrative events into one qualified customer SIEM. OSS retains canonical signed evidence, generic telemetry and independent verification.

03 · Human decisions

Existing approval systems

Connect a chosen Teams, Slack or ITSM workflow to canonical exact-action approvals. A message is not a credential and approving does not dispatch an action.

Read the edition and integration boundaries →

Capability status

Shipped OSS core versus planned Enterprise integrations.

CapabilityOSSEnterprise
Model policy, budgets, fallback, sessionsIn OSS source; verify releaseSame core; edition in development
Exact HTTP action control, local human approvalIn OSS source; verify releaseSame core; no separate engine
Signed evidence and offline verificationIn OSS source; verify releaseSame canonical evidence
Corporate OIDC, RBAC and deprovisioningLocal identity profilePlanned; not released
SIEM-specific delivery and incident integrationGeneric export/telemetryPlanned; target selected by pilot
Teams / Slack / ITSM approval adaptersLocal reviewer and approval servicesPlanned; target selected by pilot
Multi-deployment operations, DR and supported scaleLocal single-instance profilePlanned; customer/profile dependent

This directional matrix is not a release certification. Check the latest OSS release and limitations before deployment. Enterprise is not yet advertised as generally available. No unverified SSO, SIEM or ITSM support is claimed.

Start with one real workflow

What would block adoption in your company?

Bring one enforced use case and the required identity, SIEM, human approval or key-management integration. We'll scope the real boundary rather than a speculative connector checklist.

Discuss a design-partner pilotDirect conversation · not a booking form