Off-the-shelf systems ask you to adapt your company to the software. DtoMES adapts to your company. Modular architecture, built-in AI, data on PostgreSQL, evolution without rewrites.
Adopt a generic system that covers 80% of your needs but not the 20% that makes the difference, or build a custom one that costs too much and becomes unmanageable. DtoMES is the third way.
Works right away, but locks you in. Customizations are limited and costly, and every vendor update risks breaking your changes. Your process must adapt to the software, not the other way around.
Modular architecture that adapts. Each module is an independent BPL: you customize Production without touching Planning. The code is yours, the architecture is solid, evolution is continuous.
A transparent comparison with established systems. We don't hide what's missing — we show where we're heading.
| Capability | Traditional systems | DtoMES | Notes |
|---|---|---|---|
| Production bill of materials | ✅ | ✅ | 30 catalogued queries, MVP pattern |
| Barcode / traceability | ✅ | ✅ | Reading, assignment, sampling |
| Multi-team planning | ✅ | ✅ | Gantt, scheduler, resources, commitment |
| ERP synchronization | ✅ | ✅ | Hash-based, multi-DB, no triggers |
| KPI dashboard / analysis | ✅ | ✅ | AI-assisted analysis |
| Modular architecture (BPL) | ❌ | ✅ | 16+ independent BPLs, partial deploy |
| Built-in local AI (Ollama + MCP) | ❌ | ✅ | Local embeddings, modules exposed via MCP |
| Semantic search on your data | ❌ | ✅ | PostgreSQL + pgvector, one engine |
| MemoryLens (DEV+USER+SUPPORT) | ❌ | ✅ | Help, tickets, diagnostics built in |
| SBOM / supply-chain compliance | ❌ | ✅ | CycloneDX 1.5, audit-ready |
| Source code you own | ❌ | ✅ | No vendor lock-in |
| Machine IoT connector | ✅ | 🔨 | In development: dedicated ML hardware |
| Touchscreen / Kiosk (HTML) | ✅ | 🔨 | Roadmap: web UI for the modules |
| Large installed base | ✅ | — | MES in production; platform growing |
These are not features: they are architectural choices that change how the system evolves over time.
Each module is an independent BPL. Updating Production means copying one .bpl file. Planning, Laboratory, the menu — everything stays the same. Rollback? Copy the previous file.
Embeddings run locally with Ollama; semantic search lives on PostgreSQL; modules expose tools to models via MCP. AI also co-designed the architecture: late-binding patterns, resolving circular dependencies, the TMLHelper system.
Interfaces and plugins: the Laboratory module supports completely different detail types (Type A, Type B) as separate BPLs. Your process doesn't have to fit a schema: the schema adapts to you.
MemoryLens captures every anomaly automatically. The SupportPanel shows a badge with critical events. A ticket includes screenshot, logs and context. The problem is already documented before the technician arrives.
No vendor lock-in. Open standards (JSON, SQL, PostgreSQL, Delphi interfaces). The built-in SBOM catalogues every component with licenses and versions. If tomorrow you want to switch supplier, you have everything.
Your process doesn't fit standard templates. You have operations, flows and rules that no generic system covers 100%.
You don't want to depend on a vendor for every change. You want the source code and the certainty that your investment won't vanish.
Your ERP (SQL Server, Firebird, COBOL) holds valuable data. DtoMES synchronizes without touching source tables: hash-based, non-invasive.
Not as a buzzword: local embeddings with Ollama, semantic search on your data, modules exposed via MCP. And data never leaves the company.
We don't sell licenses. We build the system your company deserves.