
BasaltDB Moves From Apache-2.0 to a Source-Available License; Community Fork Gabbro Charters Under a Foundation
A LICENSE commit ends Apache-2.0 for BasaltDB 5.0 while the Gabbro fork charters independently — though contributor counts remain disputed.
§1 What Changed
FACT · CLAIM-GROUNDEDBasaltDB committed a LICENSE file change on 2026-11-18 moving version 5.0 and later from Apache-2.0 to the Basalt Source-Available License (BSAL-1.0), prohibiting third-party commercial managed hosting.C1
Within 24 hours, a group of contributors chartered Gabbro under an independent foundation, forking BasaltDB’s final Apache-2.0 tag (4.9.4).C2
Gabbro’s launch announcement claims 40 active maintainers joined the fork, whereas the initial GOVERNANCE.md file committed to the Gabbro repository lists 31 named signers — an unresolved discrepancy that caps this signal’s conviction at C3.C3C4
SignalPost Analysis — Labelled inference, not reported fact (validated fact-sterile against claim ledger)
§2 Why It Matters
ANALYSISDatabase relicensing is never just a legal footnote: it splits wire-protocol evolution, client driver maintenance, and cloud marketplace economics. Even with Gabbro’s unresolved maintainer count (40 claimed vs 31 signed), the mere existence of an Apache-2.0 foundation fork immediately strips BasaltDB of pricing power over managed-service partners.
BasaltDB 5.0 Relicense: Pin, Upgrade, or Fork
DECISION MATRIXCleanest immediate hold while counsel reviews BSAL-1.0 against your deployment.
- Cost Delta
- Keeps Apache-2.0 terms; forgoes 5.0 features[analysis]
- Migration Effort
- Version pin in container images and lockfiles[analysis]
- Lock-In Risk
- Ages without upstream security patches over time[analysis]
- Window / Timing
- Immediate[analysis]
Viable only after legal confirms your product does not trigger BSAL-1.0 restrictions.
Credible open-source exit, but verify active committers beyond launch governance claims first.
- Cost Delta
- Forked at Apache-2.0 tag 4.9.4 under foundationC2
- Migration Effort
- Low at 4.9.4; rises as codebases diverge[analysis]
- Window / Timing
- Gate on first independent Gabbro release[analysis]
§3 Second-Order Implications
Cloud platforms that resold managed BasaltDB under Apache-2.0 must either sign a commercial royalty deal for BSAL-1.0 or throw engineering weight behind Gabbro’s 4.9.4 lineage.
Enterprise legal teams running strict permissive-license policies will freeze upgrades at BasaltDB 4.9.4 while auditing whether Gabbro’s 31 committed signers can sustain security patches.
Independent backup, observability, and migration tools that support both BasaltDB 5.0 and Gabbro cleanly become the neutral bridge during the split.
▲ Better Positioned
- Neutral migration and monitoring tools supporting both lineages
- Permissively licensed competing databases pitching governance stability
▼ More Exposed
- Unmanaged SaaS vendors bundling BasaltDB inside commercial hosted offerings
- Cloud resellers without a BSAL-1.0 licensing agreement
§4 Decision Hooks
Operational options, not financial adviceOpen-Source Relicense Response Playbook
Quick Answers
Fact vs Analysis explicitly taggedHow did BasaltDB 5.0 change its software license?FACT
BasaltDB 5.0 moved from Apache-2.0 to BSAL-1.0, prohibiting third-party commercial managed hosting without a commercial license.C1
Where did the Gabbro fork split from BasaltDB?FACT
Gabbro forked BasaltDB at the Apache-2.0 tag 4.9.4 and chartered under an independent foundation.C2
§6 What to Watch / Invalidation Triggers
FORWARD · FALSIFIABLE| Kind | Observable | Source | Threshold | Check By | Status |
|---|---|---|---|---|---|
| ✗ invalidates | BasaltDB restores an Apache-2.0 community edition or rescinds BSAL-1.0 hosting restrictions | BasaltDB LICENSE | Apache-2.0 edition restored | 2027-05-31 | armed |
| ✓ confirms | At least two commercial cloud hosts announce managed Gabbro tiers | Cloud Host Announcements | >= 2 cloud hosts back Gabbro | 2027-06-30 | armed |
§7 Evidence Ledger
LEDGER4 claims · 2 sources (1 primary) · 0 corroborated · 1 disagreement· verified 2026-11-19 09:20Z
Panel A — Claims (4)
BasaltDB 5.0 moved from Apache-2.0 to BSAL-1.0, prohibiting third-party commercial managed hosting without a commercial license.
Show primary passage (BasaltDB & Gabbro OSS Governance · v1)
LICENSE commit (v5.0-rc1): Basalt Source-Available License 1.0 prohibits offering BasaltDB as a commercial managed hosting service.
Segment: si_bc89e0ab884727d351a9:1:p1 · Source: BasaltDB & Gabbro OSS Governance
Gabbro forked BasaltDB at Apache-2.0 tag 4.9.4 and chartered under an independent foundation.
Show primary passage (BasaltDB & Gabbro OSS Governance · v1)
Gabbro Charter: forked from BasaltDB 4.9.4 under Apache-2.0 with independent foundation governance.
Segment: si_bc89e0ab884727d351a9:1:p2 · Source: BasaltDB & Gabbro OSS Governance
Gabbro’s launch announcement claimed 40 active maintainers joined the fork.
Show primary passage (Meridian Trade Press · v1)
Gabbro spokespeople stated 40 active maintainers joined the fork at launch.
Segment: si_33a7ded9163cbb470f2c:1:p3 · Source: Meridian Trade Press
Gabbro’s initial GOVERNANCE.md file lists 31 named signers.
Show primary passage (BasaltDB & Gabbro OSS Governance · v1)
GOVERNANCE.md initial commit lists 31 named maintainers.
Segment: si_bc89e0ab884727d351a9:1:p4 · Source: BasaltDB & Gabbro OSS Governance
Panel B — Sources (2)
Doc: BasaltDB LICENSE Commit & Gabbro Charter
Doc: Meridian Trade Press: Gabbro Launch Coverage
Panel C — Disagreements (1)
Unresolved core count discrepancy caps deterministic Evidence Ceiling at C3.
Panel D — Primary Document Diffs (1)
Part of Convergence Thread
Open Radar →Forced Migration Windows: Deprecations & Source-Available Splits
Revision Trail (1 immutable version)
- v1 · auto · initial v2 signal assay · 2026-11-19T09:20:00Z