Why BSL and not Apache 2.0 for Core?
Business Source License 1.1 lets us keep the source available while preventing hyperscalers from hosting Neksur as a managed service without contributing back. Every release becomes Apache 2.0 four years after its release date — that is contractual, not promissory. You can read, modify, self-host, and study the source today.
What does "Change Date" mean for the commercial tiers?
Every Neksur release — Core and the three commercial tiers (Multi-Engine, Defense-in-Depth, Intelligence) — has a Change Date exactly four years from its release date. After that date, the code is Apache 2.0 permanently, regardless of our business state. There is no cliff: you keep the software you deployed.
Can we mix self-host Core and managed SaaS?
Yes — explicitly supported. Run Core self-hosted for highly-regulated tables that cannot leave your VPC, managed SaaS for the rest, with shared policy definitions and a single audit log. The Contract layer is the same whether you self-host or we operate it.
What happens at the design-partner cohort cap?
We are running a Q3 2026 cohort of six design partners. Once the six spots are filled, the cohort closes and the next intake is Q1 2027. Design partners get the Defense-in-Depth tier free for 12 months from proof of concept, plus a 50% discount on the first 24 months post-GA.
Do you have published price points or is this all "contact us"?
The four tiers have published floor prices ($0 / $48k / $150k / $250k annual). Final price depends on engine count, table volume, deployment model, and SLA. We tell you the price on the first call; we do not multi-week-sales-cycle.
How do I tell which tier I need?
Match the audit question. Can a non-compliant write enter the catalog → Core. Does my governance hold across engines → Multi-Engine. Does my auditor require defense in depth on the write path → Defense-in-Depth. Do I need detection beyond enforcement → Intelligence.