SignalPost

Commercial signals, assayed. Deltas, not events.

DESK № 0142SAT, 21 NOV 2026
2 BREAKING11 ASSAYED3 CONVERGING24 TRIGGERS ARMED18 NOISE REJECTED
CURATED SHOWCASE FIXTURE: Fictional entities and synthetic primary sources (is_fixture = 1), validated locally by SignalPost’s 26-validator suite.
PLATE XII · The Forked Basalt Pillar — A hexagonal basalt column splitting between a garnet-sealed trunk and an open keystone arch.
Quiet AlphaRules & LicensesThe Rule

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.

SignalPost DeskSP-261119-RL-05v1Updated 2026-11-19 09:20ZUtility 45/100Evidence sha256:8eccffe…c9665d
Share Assay:Card PNG ↗

§1 What Changed

FACT · CLAIM-GROUNDED

BasaltDB 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

Key Figures (Deterministic Δ)

Computed from claims, not LLM math
BasaltDB 5.0 licenseC1
BSAL-1.0 Hosting banned
Before: Apache-2.0
Gabbro fork baselineC2
Gabbro (Apache-2.0) Lineage split
Before: BasaltDB 4.9.4

SignalPost Analysis — Labelled inference, not reported fact (validated fact-sterile against claim ledger)

§2 Why It Matters

ANALYSIS

Database 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 MATRIX
Pin to BasaltDB 4.9.x (Apache-2.0)stay

Cleanest 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]
Upgrade to BasaltDB 5.0 (BSAL-1.0)negotiate

Viable only after legal confirms your product does not trigger BSAL-1.0 restrictions.

Cost Delta
Commercial license needed for third-party managed hostingC1
Migration Effort
Standard major-version upgrade[analysis]
Lock-In Risk
License moves from Apache-2.0 to BSAL-1.0C1
Window / Timing
After legal review[analysis]
Migrate to the Gabbro Forkswitch

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]
Lock-In Risk
40 maintainers claimed vs 31 named signersC3C4
Window / Timing
Gate on first independent Gabbro release[analysis]

§3 Second-Order Implications

  1. #1likelyrests on C1C2· Affects: Cloud database hosts and PaaS providers

    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.

  2. #2likelyrests on C1C4· Affects: Enterprise platform engineering and legal compliance

    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.

  3. #3plausiblerests on C1C2· Affects: Database tooling vendors

    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 advice
complyIf you embed or host BasaltDB for paying customers → consider: pin dependencies to Apache-2.0 tag 4.9.4 and review BSAL-1.0 hosting terms before upgrading to 5.0.
waitIf you are deciding whether to migrate to Gabbro → consider: wait to confirm whether at least two cloud hosts publicly commit engineering backing to Gabbro.

Open-Source Relicense Response Playbook

0/4 doneCHECKLIST · LOCAL

Quick Answers

Fact vs Analysis explicitly tagged
How 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

Why does SignalPost note a maintainer discrepancy on Gabbro?FACT

Gabbro’s launch post claimed 40 active maintainers joined the fork, whereas its initial GOVERNANCE.md file lists 31 named signers.C3C4

§6 What to Watch / Invalidation Triggers

FORWARD · FALSIFIABLE
KindObservableSourceThresholdCheck ByStatus
✗ invalidatesBasaltDB restores an Apache-2.0 community edition or rescinds BSAL-1.0 hosting restrictionsBasaltDB LICENSEApache-2.0 edition restored2027-05-31armed
✓ confirmsAt least two commercial cloud hosts announce managed Gabbro tiersCloud Host Announcements>= 2 cloud hosts back Gabbro2027-06-30armed

§7 Evidence Ledger

LEDGER

4 claims · 2 sources (1 primary) · 0 corroborated · 1 disagreement· verified 2026-11-19 09:20Z

Panel A — Claims (4)
C1documentedBasaltDB & Gabbro OSS Governance

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

C2documentedBasaltDB & 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

C3reportedMeridian Trade Press

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

C4documentedBasaltDB & Gabbro OSS Governance

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)
BasaltDB & Gabbro OSS GovernanceOSS Governanceprimary · auth 4/5 · transformative_brief_allowed · 2 ver

Doc: BasaltDB LICENSE Commit & Gabbro Charter

Meridian Trade PressSecondary Reportsecondary · auth 2/5 · link_and_excerpt · 1 ver

Doc: Meridian Trade Press: Gabbro Launch Coverage

Panel C — Disagreements (1)
⚠ unresolvedClaims C3 vs C4
Gabbro Launch Announcement
Claims 40 active BasaltDB maintainers joined the Gabbro fork at launch.
Gabbro GOVERNANCE.md (Primary Repo)
Lists 31 named committers on the initial governance roster.

Unresolved core count discrepancy caps deterministic Evidence Ceiling at C3.

Panel D — Primary Document Diffs (1)
BasaltDB LICENSE: v4.9.4 → v5.0-rc1
− Licensed under the Apache License, Version 2.0 (the "License").
− Commercial and hosted redistribution permitted with attribution.
+ Licensed under the Basalt Source-Available License 1.0 (BSAL-1.0).
+ Offering BasaltDB as a commercial managed hosting service requires a separate commercial license.

Part of Convergence Thread

Open Radar →
▲ converging · developing

Forced Migration Windows: Deprecations & Source-Available Splits

Revision Trail (1 immutable version)
  • v1 · auto · initial v2 signal assay · 2026-11-19T09:20:00Z

Keyboard Shortcuts

⌘K / Ctrl+KOpen Quick Jump command palette
/Focus search (or open /search/)
g then dOpen Executive Digest (/digest/)
g then tOpen Tools & Calculators (/tools/)
g then wOpen Watchlist & Triggers (/watch/)
j / kNext / previous row in Signal Matrix
?Toggle this shortcuts dialog