Editions and capabilities

BNLGit ships as two editions from the same source tree.

Lite (planned — source not released yet, see "The Lite source release" below) — core Git hosting, manual BNLRepo pairing and sync, the Sync Cockpit, the drift signal, and lexical search.
Pro — everything in Lite, plus the managed summary worker, spend budgets, model bake-offs, the AI Repo Cleaner, MCP integration, fleet dashboards, and reranking.

The hosted service runs Pro. Pro is an instance-level property, so every account on the hosted beta has the Pro feature set.

Ask the instance, do not guess

Any client can call this without signing in:

GET /api/v1/bnlgit/capabilities

It returns the running edition, the licence status, the feature-flag map, and the drift thresholds. A script or an agent should read this rather than assume.

The feature flags

These are the exact flag names in the response.

Flag	Lite	Pro
`core_git_hosting`	✅	✅
`bnlrepo_pairs`	✅	✅
`manual_llm_sync`	✅	✅
`sync_cockpit`	✅	✅
`drift_signal`	✅	✅
`dual_llm_roles`	—	✅
`analysis_cleanup_menu`	—	✅
`managed_worker`	—	✅
`spend_budgets`	—	✅
`model_bakeoffs`	—	✅
`repo_cleaner_steward`	—	✅
`trusted_retrieval_mcp`	—	✅
`reranking`	—	✅
`fleet_dashboards`	—	✅
`downloadable_pro_bundle`	—	✅

A Pro flag reads true only when the edition is Pro and a valid licence is present. An expired or missing licence turns the Pro flags off rather than leaving them optimistically on.

Note that reranking reports whether the edition permits reranking, not whether an operator has switched it on for the instance — it is off by default. See Search.

Other fields worth knowing

license — enforced, licensed, org, licence ID, seat and repo counts, expiry, and a status reason.
drift_thresholds — the green/yellow/red percentages and failure counts described in the mirror model, so your tooling reads them rather than hard-coding 90 and 70.
credential_redaction — states that credential IDs and references are returned only to repository admins and site admins.
license_files_required — the licence and notice files a compliant distribution must ship.

Edition resolution fails closed

If an instance is configured with an edition value it does not recognise, it resolves to Lite, not Pro. There is no configuration typo that accidentally unlocks paid features.

Licensing


Upstream Gitea / Gogs	MIT, notices preserved verbatim.
BNLGit Lite modifications	AGPL-3.0-or-later.
BNLGit Pro bundle	Proprietary BNLGit Pro EULA, plus third-party notices.

Licences are Ed25519-signed tokens. An instance verifies its own with bnlgit license status — see the CLI reference.

Self-hosted Pro

Pro supports a downloadable, single-customer deployment — a dedicated instance, not shared multi-tenant hosting.

That is not part of this public beta. During the beta we offer the hosted service only. If a dedicated deployment is a requirement for you, mail hello@bnlgit.com.

The Lite source release

Lite's source has not been published yet. It is planned for general availability, released under AGPL-3.0-or-later, alongside GA rather than on a calendar date — so that the released tree is the one GA actually runs.

Until then the licence table above describes what each edition will be distributed under, not what you can download today. There is nothing to clone yet; if you want to hear the day there is, mail hello@bnlgit.com.

Something here wrong or missing? Mail docs@bnlgit.com — these pages are the single public source of truth for BNLGit and we would rather fix them than leave you guessing.