Skip to content

lumnik — defrost the enterprise

Your ERP holds twenty years of orders, customers and stock — data trapped in a system nobody dares to touch and nobody will ever migrate. lumnik un-freezes it: ingested read-only (your ERP is never written to — ingest first, risk nothing), fused into one governed hub, and handed back to the people who need it. A warehouse worker asks the 2003 stock a question in plain language, from a phone, and the answer cites its sources — or honestly declines. When lumnik doesn't know, it says so: the guards refuse to invent an answer.

See it before you install anything

The WOW, step by step — a SOAP Siebel and a CSV export fused into one canonical customer, every disagreement between sources kept in an honest _conflicts ledger, then asked in natural language. Sixty seconds of watching beats any feature list.

The map

  • The hub — declarative connectors (JDBC · CSV · REST · GraphQL · SOAP · file sources · events) ingest legacy data 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.
  • Entities — N legacy sources fused into one canonical, queryable thing; conflicts are preserved, never silently resolved.
  • Ask your data — per-métier chat and read-only text-to-SQL over the live hub, fenced by five deterministic honesty guards and métier scopes.
  • Apps — views, processes, workflows, inbox, and the métier PWA on the phone in the warehouse.
  • lm — the integrator's CLI/TUI (k9s-style) that drives it all.

Where to start

  1. See the WOW — watch first.
  2. Deploy lumnik — one command, self-host.
  3. Quickstart — wire your first connector.

Then browse the Connectors reference.