Licensing & Tiers

Business Model

How Syntropy uses a Fair Source and Managed Cloud hybrid model to balance developer trust with sustainability.

The transparency paradox

In the multi-agent AI ecosystem, there is a fundamental tension between Intellectual Property and Developer Trust.

Enterprises cannot deploy black-box AI orchestration systems into production. They require strict determinism, auditability, and mathematical guarantees. If the core logic resolving agent state is hidden behind a proprietary API, trust is impossible.

However, offering the entire framework as unrestricted open-source allows massive enterprises to extract value without supporting the maintainers, threatening the sustainability of the project.

Syntropy solves this using a Fair Source / Managed Cloud hybrid model.

1. The Fair Source engine

The core Syntropy mathematical lattice and execution runtimes (both Python and Elixir) are released under the Business Source License 1.1, a Fair Source license.

What this means:

  • Free for development and evaluation: The engine is completely free for internal development, academic research, personal projects, and testing — for everyone, at any company size.
  • Free production for small organizations: Production use is included while your organization's gross revenue and funding each stay under US $1M (aggregated across affiliates).
  • Mathematical auditability: Principal engineers can inspect the codebase to verify the lattice axioms (Commutativity, Associativity, Idempotency) and ensure the determinism claims are mathematically sound.
  • Commercial boundary: Production deployment above the threshold legally requires a commercial license — included with Cloud Pro, or licensed directly for self-hosted Enterprise.
  • No competing hosted services: Regardless of size, no one may offer Syntropy itself (or a substitute for it) as a hosted, managed, or embedded service to third parties. Applications built on top of Syntropy are unaffected.
  • Delayed open source guarantee: Every released version automatically converts to the Apache 2.0 license four years after its first public distribution. Adopting Syntropy is never a bet on the vendor.

This model uses transparency to build trust, while using corporate legal compliance to guarantee sustainability.

2. Syntropy Cloud (managed observation)

While the lattice engine is available to self-host, deploying and managing distributed Elixir/OTP clusters and real-time WebSocket pipelines is a massive operational burden.

Syntropy Cloud Pro is our managed SaaS offering on app.syntropyos.dev. Create a workspace, subscribe with Stripe, and connect local Python workers to the hosted cluster. Self-hosting the open core remains available under the Fair Source license. The subscription covers:

  • Zero-DevOps cluster hosting.
  • The real-time Mission Control dashboard.
  • 7-day historical replay retention.

Developers simply add SYNTROPY_API_KEY=xyz to their local Python workers, and the lattice orchestrates visually in the cloud.

3. Enterprise integration

For large enterprises, the Enterprise tier includes today:

  • Role-Based Access Control (RBAC) with granular admin/member/viewer roles.
  • Indefinite replay and audit retention on the Postgres-backed runtime.

On the Enterprise roadmap (contact us if these gate your adoption):

  • Single Sign-On (SSO) through Okta/SAML identity providers.
  • VPC Peering for secure, direct AWS/GCP connections.
  • Audit export for SOC2/HIPAA compliance workflows.

The lattice runtime itself stays source-available on every tier — Enterprise deployments run the same auditable engine anyone can inspect. What Enterprise adds is the commercial production license plus a proprietary control plane: multi-tenant management, access tooling, and dedicated infrastructure. By combining an open, auditable mathematical core with a commercially licensed control plane, Syntropy aligns developer trust with B2B sustainability.