The two editions
lumnik ships as two builds:
| Build | Licence | What it does |
|---|---|---|
lumnik-open |
Apache-2.0, public repository | ingest, fuse, react, serve the business apps |
| lumnik Pro | commercial | adds Ask (natural-language chat over your data), the model providers, Kafka, the Oracle dialect, and JIT and SCIM for an external identity directory |
The open hub has no chat and no Ask, and no licence key unlocks them: they are not in the build.
lm is one binary for both editions. On an open hub, its Ask commands (lm ask, lm chat,
lm rag search, lm scopes) say so:
$ lm ask "how many customers?"
Error: this hub's build has no Ask: lumnik Open has no chat, no lm ask and no semantic search (lm module list shows no rag module); Ask ships in lumnik Pro
lumnik Open is the build behind the free Hub tier. lumnik Pro is the build behind both paid tiers — see Three tiers, two builds.
Feature by feature
| lumnik Open | lumnik Pro | |
|---|---|---|
| Connectors: CSV (SFTP/S3), JDBC, REST + GraphQL/SOAP shapes | ✓ | ✓ |
| Connector: kafka | — | ✓ |
| JDBC dialect: Oracle (driver included) | — | ✓ |
Fusion: entities, _conflicts ledger |
✓ | ✓ |
| Apps ladder: views, processes, workflows, inbox, PWA | ✓ | ✓ |
| Outputs: webhooks (signed, journaled, replay), email notifications | ✓ | ✓ |
lm CLI / TUI, manifests, the whole integrator surface |
✓ | ✓ |
| Multi-tenancy & RLS, audit trail, backup | ✓ | ✓ |
Search: declare an index (kind: SearchIndex). Querying needs a provider: without one, lm search query answers not installed |
✓ | ✓ |
Search provider: PostgreSQL (up.sh --search) or OpenSearch / Elasticsearch (up.sh --search-cluster), with the PWA's Search tab. Never in the published image |
— | ✓ opt-in build |
Ask: chat and lm ask, semantic search, lm view generate (the AI writes a view) |
— | ✓ |
| Model providers (Ollama & friends) | — | ✓ |
| JIT provisioning for external IdPs | — | ✓ |
| SCIM deprovisioning | — | ✓ |
Switched off is not absent. A Pro hub can run with the AI switched off
(LUMNIK_AI_ENABLED=false):
- the data is kept;
lm module listshowsragandllmasINACTIVE.
An Open hub does not list them at all. Neither shows a Chat tab. How to switch it: Choosing what your hub offers.
Which edition am I running?
$ lm module list
NAME VERSION SCHEMA STATUS REASON
core 0.1.0 Platform ACTIVE
identity 0.1.0 Identity & Tenancy ACTIVE
llm 0.1.0 Model provider INACTIVE disabled:lumnik.ai.enabled
rag 0.1.0 Platform RAG INACTIVE disabled:lumnik.ai.enabled
| What you see | Build |
|---|---|
core + identity only |
lumnik Open |
plus rag + llm (always together) |
lumnik Pro — INACTIVE means the AI is switched off, as above |
plus search_pg or search_opensearch |
a build with a Search provider |
The hub's boot log lists the installed modules too. More: the full answer.
Three tiers, two builds
The commercial ladder has three tiers; the builds are two:
| Tier | Runs the build | Who operates it |
|---|---|---|
| Hub — free, installed on your own machines | lumnik Open | your integrator, exploring and tooling up |
| Pro | lumnik Pro | your integrator, running it for a client |
| Enterprise — on quote | lumnik Pro | your own IT, in your own world |
Enterprise is the Pro build, sold with your identity directory (external IdP, SCIM), a Kubernetes delivery and service commitments.
When a page marks a capability "not in the open edition", it speaks of the build — the one
lm module list shows — not of the tier.
Prices: contact@lumnik.fr. The open edition is the same hub, so an evaluation can start there.
See also
- How lumnik works · How lumnik breathes
- Deploy — the same one-command stack for either build
- Choosing what your hub offers — which tabs and features a hub shows, and the gesture for each
- Security overview — every edition-dependent answer, marked