Skip to content

lumnik — defrost the enterprise

Documentation

lumnik reads the data in your ERP, LIMS and exports — read-only. It fuses the data, shows it to the right team, and answers questions in plain language (Pro). An answer shows its sources, or declines.

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.

Not a migration, not BI

The ERP stays. lumnik reads it, and puts its data to work beside it.

Deploy lumnik See the WOW Follow the guided path

Your first day, in order

1

Prepare the machine

Prerequisites: Docker, a few tools, and Ollama for Pro.

2

Deploy the hub

Deploy: one command starts the hub, its database and its login server.

3

Load a first export

Quickstart: install lm, log in, load a CSV, see the rows.

You know it worked when: lm connector list shows the connector your export registered.

4

Run the WOW

The WOW: two legacy systems become one customer, then a view, a decision, a lifecycle.

The full path, day by day: Guided path.

The system in one glance

The system in one picture — data flows left to right, read-only at the door:

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"]
    direction TB
    conn["Connectors — read-only ingestion"]
    tables[("Raw tables, per tenant")]
    ent["Entities — fused, conflicts kept"]
    ask["Ask (Pro)"]
    ev["Events → decisions"]
    conn --> tables --> ent --> ask
    tables -->|"new rows"| ev
  end
  subgraph metier["Business users"]
    direction TB
    chat["Chat (Pro)"]
    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

  • Sources: JDBC, CSV and files, REST, GraphQL, SOAP — plus Kafka in lumnik Pro — through declarative connectors.
  • Tenants: each tenant sees only its own rows (RLS).
  • Repair at the door: transformers fix broken accents and legacy dates.

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

Ask a scope's data in plain language. The SQL behind the answer runs read-only, and guards refuse to guess (lumnik Pro).

When Ask refuses

Act

Apps, workflows, and the roads out

Views, processes, workflows and the inbox become business apps, on a phone too. What changed leaves again: a decision reaches your own tools by signed webhook or email.

Browse apps