Skip to content

The read layer for the software you run

Your software stays put.
Your data gets back to work.

Filtration Lyon 1008P-1008
City
Lyon ERPThe CRM says Villeurbanne
Segment
GOLD ERP
Email
contact@filtration-lyon.example CRM
Fictional demo data, as lumnik merges it. The ERP and the CRM disagree on the city: the record keeps both. See the documentation.

lumnik reads your ERP, your exports and your APIs without ever writing to them. It merges their data, repairs the exports and serves it all to your teams and your tools.

  • Read-only
  • Self-hosted
  • Open source
See the scenarios Try lumnik Open

Replayed scenarios

Sound familiar?

Each situation was replayed on a lumnik hub. The scenario shows what was declared, the commands that ran and the results they gave.

Repair an export Open

One order status spelled fourteen ways

The team declares four statuses. lumnik lists the other spellings that need review. Open the scenario → Merge the sources Open

One customer in two systems with no shared id

The email matches the records. If the link remains uncertain, a person decides. Open the scenario → Track rejected rows Open

An unreadable line of the export does not pass in silence

The unreadable row is set aside with its values and the reason it was rejected. Open the scenario → Alert and decide Open

Auditing how long orders stay in each status

The ERP keeps only today's status. lumnik remembers since when. Open the scenario → Serve the teams Open

The CMMS is switched off and the hub still returns the same bytes

After one final read, the old server can be switched off. Open the scenario → Ask your data Pro

Ask refuses a margin with no cost and a best supplier with no criterion

Each figure comes with its SQL. When data is missing, Ask refuses to answer. Open the scenario →
All the scenarios

How

Five moves. Nothing written to your software.

Read

Connectors read your files, your databases and your APIs. Nothing is ever written to your software.

Repair

In an export, dates, accents, amounts and old formats are corrected during ingestion. An unreadable row is set aside with the reason it was rejected.

Merge

Several sources become one record. Their disagreements stay visible.

Watch

Every read is timestamped. A record left unchanged past its declared limit appears in the decision inbox.

Serve

One app per team on the phone, an API, SQL, webhooks. With Pro, questions in plain language.

Nothing is lost without being counted. On every run, rows read equal rows written plus rows set aside.

Try it

lumnik Open installs in one command.

Free and open source, under the Apache-2.0 license. A machine with Docker is enough.

 install lumnik Open
$ git clone https://github.com/icreated/lumnik-open.git && cd lumnik-open
$ ./deploy/selfhost/up.sh --build
…
==> hub is healthy
  Hub:       http://localhost:8080   (health: /q/health)
  Keycloak:  http://localhost:8180/realms/lumnik

In lumnik Open

  • Connectors: files, PostgreSQL databases, REST, GraphQL, SOAP
  • Merged records and the ledger of disagreements
  • Views, processes, workflows and a decision inbox
  • Team apps for phones
  • Signed webhooks and emails
  • lm, the integrator's command line

Pro adds

  • Questions in plain language
  • Kafka, Oracle and search
Step by step

Trust

What your IT team can verify.

  • Read-only. lumnik never writes to your systems.
  • Isolated by the database. PostgreSQL separates every organization's rows.
  • Self-hosted. The hub runs on your servers. With Pro, the AI model can too.
  • Reversible. Plain PostgreSQL tables, a standard pg_dump.

Verify it in five minutes Beta Where lumnik stands lumnik Open · Apache-2.0

Business teams We may already have replayed a case like yours. The scenarios → IT & security Read-only access, self-hosted, with database isolation. The guarantees → Integrators & partners Describe a system in YAML. Reuse the integration for the next customer. Integration as code →