Skip to content

lumnik — defrost the enterprise

Documentation

Your information systems — the ERP, the LIMS, the exports nobody dares to touch — hold twenty years of history nobody can question any more. lumnik un-freezes that data, read-only.

Then someone asks it a question in plain language, from a phone. The answer cites its sources — or declines and says why.

Read-only first

Your source system is never written to. Ingest first, risk nothing.

Fuse, conflicts kept

Conflicts are preserved in a _conflicts ledger, never silently resolved away.

Ask with guards

Answers cite their sources — or decline. The guards refuse to invent.

Operate for real

Deploy, connect, scope, and run day-2 operations from one docs set.

See the WOW Deploy lumnik Follow the guided path

Choose your starting path

Start here

See the WOW

Watch two legacy sources become one canonical customer, then ask it a question in French.

Open the walkthrough

Install

Deploy the hub

Run the self-host stack, wire OIDC, and get to a healthy local hub without guesswork.

Open deploy docs

First value

Quickstart in 60 seconds

Build lm, point it at the hub, and show value on CSV, REST, or SFTP data.

Open quickstart

Guided onboarding

Walk the full path

Go from an empty machine to scoped métier apps, dormancy alerts, and day-2 operations.

Open parcours

The system in one glance

Frozen data flows one way — left to right, read-only at the door. On the right it meets people, and it leaves again: what changed becomes an event, then a decision, then a message in your own tools. Every page in this documentation sits somewhere on this map:

flowchart LR
  subgraph frozen["Frozen legacy systems"]
    direction TB
    erp[("ERP · JDBC")]
    files[("CSV · SFTP · S3")]
    apis[("REST · SOAP · GraphQL")]
  end
  subgraph hub["the lumnik hub — multi-tenant · RLS"]
    direction TB
    conn["Connectors — read-only ingestion"]
    tables[("Raw tables, per tenant")]
    ent["Entities — fused, conflicts kept"]
    ask["Ask — five honesty guards"]
    ev["Events → decisions"]
    conn --> tables --> ent --> ask
    tables -->|"new rows only ·<br/>REST/SOAP/GraphQL silent"| ev
  end
  subgraph metier["The métier"]
    direction TB
    chat["Chat"]
    pwa["PWA · views · inbox"]
  end
  out["The roads out —<br/>webhook · email · pull"]
  lm["lm CLI/TUI —<br/>the integrator operates the hub"]
  erp --> conn
  files --> conn
  apis --> conn
  ask --> chat
  ent --> pwa
  ev --> pwa
  ev --> out
  hub -.- lm

The product surface

Ingest

The hub

Declarative connectors ingest JDBC, CSV, files, and REST (GraphQL and SOAP are request shapes on the same REST engine) — plus Kafka event brokers in lumnik Pro — into a multi-tenant PostgreSQL where isolation lives in the database (Row-Level Security), not in the URL. Transformers repair the freezer's damage — mojibake, legacy dates — right at the door.

Connector overview

Fuse

Entities

N legacy sources become one canonical, queryable thing. Disagreements stay visible in the _conflicts ledger.

Open entities

Ask

Answers that cite — or refuse

Per-métier chat and read-only text-to-SQL over the live hub, fenced by five deterministic honesty guards and métier scopes.

See the five guards

Act

Apps, workflows, and the roads out

Views, processes, workflows, inbox, and the métier PWA turn the hub into operational surfaces — on a phone, where the work actually happens. And what changed leaves again: a decision reaches your own tools by signed webhook or email.

Browse apps

First session map

1

Watch first

Use the WOW before reading feature lists. Seeing one fused customer beats absorbing ten abstractions.

You know it landed when: you understand what a connector, an entity, and a sourced answer look like in one run.

2

Deploy and log in

Run the hub locally, point lm at it, and verify your first authenticated call succeeds.

You know it worked when: lm login succeeds and lm connector list answers.

3

Choose your shelf

Once the system is alive, branch into Connectors, Apps, Security, or Operations depending on what you need next.

Best next shelves: Connectors, Workflows, Security, Operations.

Reference shelves

If you want the full newcomer sequence rather than the shelf model, go straight to Parcours.