All ten modules of Axiom 3 are on Maven Central. Anyone can pull them, read every line, and evaluate them for free. When Axiom moves into production, or into anything that earns revenue, you need a commercial license. Ensemblu also takes on the engineering work around it: private deployments, custom native drivers and architecture reviews.
There's one license model across the whole 3.0 stack. The line is simple: if Axiom runs in production or supports a business activity, you need a signed agreement.
| Use case | Free evaluation | Commercial license |
|---|---|---|
| Reading the source, running the demos | ✓ Yes | ✓ Yes |
| Prototypes and proofs of concept | ✓ Yes | ✓ Yes |
| Courses, tutorials, personal learning | ✓ Yes | ✓ Yes |
| Non-commercial open development | ✓ Yes | ✓ Yes |
| Production systems | ✕ No | ✓ Yes |
| Anything that generates revenue or supports a business | ✕ No | ✓ Yes |
Every engagement is scoped directly with the core architect, with no account managers in between. That's the same principle Axiom applies to code.
Axiom 3 deployed on your own hardware or in an isolated environment, with the native client libraries, JVM flags and build pipeline set up for your infrastructure. Built for institutions that need full hardware control and no dependence on public repositories.
New off-heap protocol drivers built with the same Executioner shape as the five 3.0 drivers, or extensions to PostgreSQL, MySQL, Oracle, SQLite and SQL Server for your own requirements, plus data-oriented processing pipelines around them.
A review of an existing Java persistence or data layer against data-oriented, zero-reflection principles: where the ORM, the pool or the framework is costing you, and what replacing it would take.
Moving a codebase onto Axiom 3, whether from another stack or from Axiom 2.x (axiom-warp-jdbc / axiom-warp-reactive) to the native drivers, MemorySegment parsers and axiom-telemetry.
SchemaGuardEmail contact@ensemblu.com with your use case, the modules and databases involved, and your deployment environment.
A direct conversation with the core architect about what you need: a license, an engagement, or both.
A Commercial Enterprise License Agreement, plus a statement of work for any engineering engagement.
Run Axiom 3 in production under license, with the engineering work delivered against the agreed scope.
The source is public, and every module ships with a sources JAR on Maven Central. Axiom is not under an OSI open-source license, though. It's published under the Limited Commercial License: free for evaluation, testing, education and non-commercial development, with a paid annual agreement required for production or commercial use.
Any use in a production environment, or for any purpose that generates revenue or supports a business activity. If you're unsure whether your case qualifies, ask; we'd rather answer up front.
Evaluation and testing are free, including prototypes and proofs of concept. The license is needed once Axiom runs in production or supports a business activity.
Yes. The commercial agreement covers the Axiom 3 stack: the five core modules and the five native drivers.
The 2.0.0 artifacts stay on Maven Central under the same evaluation terms, but commercial agreements and engineering work target Axiom 3. If you're on 2.x, the migration guide covers the move to 3.0, and migration help is available as a service.
Sponsorship through GitHub Sponsors funds independent development and is very welcome. It doesn't replace a commercial license for production use.
Tell us what you're building, which databases you use, and where it will run. You'll get a direct reply.