Ontomesh

The semantic system of record for your enterprise. Derive a formal model of the systems you already run, govern how it changes, and prove where every answer came from. Built from your schema and your logs — without hand-crafting a single Turtle file.

Preview release. Public API surface is stabilising; expect occasional breaking changes until 1.0.

What's in the image

Run it

# Ephemeral run (resets on stop):
docker run --rm -p 5051:5051 ghcr.io/synaptixs/ontomesh:latest

# Persistent run (saved ontologies survive container restart):
docker volume create ontomesh-data
docker run -d --name ontomesh \
  -p 5051:5051 \
  -v ontomesh-data:/data \
  -e ONTOMESH_DATA_DIR=/data \
  ghcr.io/synaptixs/ontomesh:latest

Then open http://localhost:5051 in your browser.

Screenshots — a guided tour

A walkthrough from landing page to ontology-grounded reasoning search, in order.

1. Landing — the marketing entry point.

2. Model your domain — a guided, navy + lime-green Twilight wizard that walks you from a domain to a generated ontology in four phases — Define → Enrich → Build → After.

3. Run report — every run emits a branded HTML report: competency-question results, governance scorecard, semantic-loss analysis, and orphan-class checks.

4. Ask — pose a question — the read-only, ontology-grounded Ask console. Pick a flavor and provider (Ollama / OpenAI), set your sensitivity-tier ceiling, and optionally build an RDF subgraph for live SPARQL.

5. Ask — a cited, reasoned answer — the answer cites its sources, shows the exact read-only SQL that ran, materializes the result subgraph, and streams the full reasoning trace (plan → execute → relations → reason → synthesize).

6. Ask — live SPARQL over the result subgraph — interrogate exactly what grounded the answer with a SPARQL SELECT against the materialized RDF triples.

The wizard ships three themes — Twilight (default), Mono, and Light — switchable from the “All steps” drawer.

What you get

Configuration (env vars)

What ships inside

First-time experience

The first time you load the wizard with an empty session, a welcome modal offers ten starter industries. Pick one to populate the session with a real ontology you can edit, or "Start with a blank session" to build from scratch.

Persistent SQLite vs. Postgres

The image defaults to SQLite-on-disk. For multi-host or multi-replica deployments, set ONTOMESH_DB_URL to a Postgres connection string — the wizard switches transparently. Both backends share the same wire schema.

Source · documentation · deployment recipes

The full developer documentation, deployment guides (Compose / Fly.io / Render / Cloud Run), and source code live in the repository:

https://github.com/synaptixs/ontomesh

Specifically:

• deploy/README.md — picking a deployment target
• docs/integrate.md — connecting to your own database
• compose.yml + deploy/Caddyfile — single-host TLS recipe
• fly.toml · render.yaml · deploy/cloudrun.yaml — managed-runtime configs

Feedback

File a tester-feedback issue — the form has a short three-option dropdown (Bug · Friction · Idea · Docs), optional repro/expected sections, and auto-applies the tester-feedback label. Or message the team directly.

Looking for what changed when? See CHANGELOG.md.

Ontomesh v3.10.2 · Apache-2.0 · OWL 2 DL · instance data · self-checking output · Reasoning Search · gunicorn · Redis SSE · Prometheus · cosign-signed · OWL 2 · SHACL · PROV-O · SKOS · JSON-LD · 1000+ tests · Docker, Compose, Fly.io, Render, Cloud Run