There is one closed delivery — RAGRAF Enterprise. The licence level (Pro or Enterprise) decides what is open in it; there is no separate build per level, so moving from Pro to Enterprise is a new licence file, not an installation. Community is the public product under BUSL 1.1: it does not expire and is not artificially cut down.
54
facade operations
Measured from the code: tools/count_surface.py
61
MCP tools
One server, 21 CLI subcommands
12 / 12
capabilities written
14 declared; three still wait for code and are named in the table
4
years to Apache-2.0
Business Source License 1.1: the licence changes four years after each release
Community
The public product, free level: a local index of code and documents — graph, vectors, schema from migrations and live databases. No licence file.
Who it is for
One engineer or a small team: needs the answer to “where does this live and what will a change touch” without external services.
Search, symbols, function bodies, documents; path:line in every answer
Code graph: callers, callees, impact of a change, slice
Schema from migrations and live databases, drift journal, corpus registry
BUSL 1.1: internal use is allowed, commercial included; resale as a hosted service is not
A licence level inside the same closed delivery: the same core plus a shared index for several machines and a quality loop that measures the index itself. There is no separate build — a signed licence file opens the level.
Who it is for
A team of several people and several corpora: one index for everyone and verifiable retrieval quality.
Shared index: publish a corpus for reading over the network and admit clients
Quality loop: a set of checks and a diff between runs
Secret broker: time-boxed leases, an issuer, one-time hand-out and scheduled rotation
EULA and a signed Pro-level licence file (Ed25519): verified locally, no network needed
The Enterprise licence level in the same delivery: everything in Pro plus the organisation side — your OIDC, journal export to SIEM, an offline licence and delivery attestation. The files are the same as in Pro.
Who it is for
An organization with access and reporting requirements: approval through its own provider, audit, an air-gapped network.
Single sign-on over OIDC (authorization code + PKCE) with external group mapping
Export of access logs and secret-vault audit to an external SIEM
Offline licence and a signed evidence bundle for external audit
The same licence file, Enterprise level; offline licence for a network without access
A level is proven by a signed licence file, not by an installation: that is why the move does not depend on what is already installed.
Pro → Enterprise: the licensor issues an Enterprise-level file and OIDC, SIEM, offline licence and attestation open. No installation, no delivery update and no data migration — the files are the same.
Enterprise → Pro when renewing on a smaller level: a Pro-level file is issued, the Enterprise capabilities close, and index, journals and settings stay where they are.
The term has expired or there is no licence file: Community applies — data and index remain, paid operations refuse with a named reason.
Capabilities compared
Rows are grouped by layer: the index core, the team layer, the organization layer. A status describes the build of that edition, not a promise in a document.
Capabilities by licence level
Capability
Community
Pro
Enterprise
Index core — present at every level
Search and reading — vector and lexical search, symbols, function bodies, documents
included
included
included
Code graph — callers, callees, impact of a change, slice, repository map
included
included
included
Schema and access — tables, reads and writes, access policy, routes, classes
included
included
included
Live databases — structure, tables, relations, sample rows, drift
included
included
included
State and trust — revision, registry, drift journal, freshness, notes
included
included
included
Team and quality — Pro and Enterprise levels
Shared index — publish a corpus for reading over the network
not included
included
included
Quality loop — index checks and a diff between runs
not included
included
included
Secret broker — time-boxed leases, an issuer, one-time hand-out and scheduled rotation
not included
included
included
Organisation — Enterprise level only
Single sign-on — OIDC authorization code + PKCE, external groups
not included
not included
included
SIEM export — access logs and secret-vault audit
not included
not included
included
Offline licence — work in a network without outbound access
not included
not included
included
Attestation — a signed evidence bundle for external audit
not included
not included
included
includedwritten and opened by this edition
not includednot part of this edition
Terms compared
Capabilities are half the answer. The other half: what you take on, how the right is proven, and what happens when a licence ends.
Terms by licence level
Term
Community
Pro
Enterprise
Licence
BUSL 1.1 with an additional use grant: any use inside your organization, commercial work included
EULA
EULA
How you get it
Public repository and install.ps1; tagged releases
The same closed delivery; the Pro licence file sets the level
The same closed delivery; the Enterprise licence file sets the level
How the right is proven
Not needed: there is no licence file
A signed file (Ed25519), verified locally, no network required
The Enterprise-level file plus an offline licence for a network without access
Without a licence and after expiry
Not applicable
Community applies: data and index stay, access is not blocked
Community applies: data and index stay, access is not blocked
Support
Community: issues in the project tracker
Under an agreement with the licensor
Under a support agreement, response times included
Seats
No seat limit
The number of purchased seats
The number of purchased seats
Which level to take
One project, one engineer
Take Community. Paid capabilities become relevant only when a second corpus or a second person appears.
A team and several corpora
You need the Pro level: a shared index instead of a copy per person, and a quality loop to see retrieval degrade before a human notices.
Access and reporting requirements
You need the Enterprise level: sign-in through your OIDC, journal export to SIEM, delivery attestation and work in a network without access.
How to read this table
“Declared, no code” is not a softened “coming soon”: that capability does not exist in the build of that edition, and the operation refuses with a named reason. Three rows are in that state today.
Safety of basic use is never sold separately: excluded secret-bearing paths, local audit and panel sign-in are in the free edition.
The boundary between Community and the closed delivery is the presence of files in the build: what is missing refuses with a named reason, and configuration cannot get around it. Between the Pro and Enterprise levels the files do not differ at all — only the signed licence file does, which is why a level cannot be bought in by installing something.
What is new in 0.3.1
One closed delivery: Pro and Enterprise are licence levels inside it, there is no separate build for Pro
Moving from Pro to Enterprise is a new licence file: no installation
One capability inventory (enterprise/inventory.toml): the edition field names the licence level, not a package