If your data falls under GDPR, HIPAA, GLP, FDA 21 CFR Part 11, MiFID II, BAIT, or any equivalent — and that data has to stay inside your network — Eldric is the AI platform that fits.
Every persisted artefact carries a tenant ID. The kernel returns 403 on any cross-tenant attempt. Superadmin escape hatch for legitimate cluster-internal calls only.
Every privileged operation appends an entry whose SHA-256 chain links to the previous entry. Verifiable offline.
The license file is signed and verifiable offline against an embedded public key. Worker validation falls back to the local file when the controller is unreachable.
Drain in-flight requests, snapshot state, install, verify SHA-256, restart, validate, move on. One alpha at a time, no downtime window.
Spans, counters, histograms via OTLP-HTTP. Low-cardinality path normalisation so dynamic IDs do not blow up your observability bill.
Multi-round federated training across worker nodes. Controller orchestrates; workers train on local data; gradients aggregate without sharing data.
If your regulatory framework is named above, we have the matching toggle. If it is not, it does not mean we cannot support it — it means we have not had a customer ask yet. Write to office@eldric.ai.
Industrial AI often needs predictable latency, not just throughput. Eldric covers the soft-real-time and near-real-time tiers — the ones most production lines actually need. Hard real-time stays the PLC's job, and we say so.
Deploy Eldric on a workstation or single server next to the PLC. The round-trip stays inside the building; no WAN hop, no cloud-call jitter.
Measured chat round-trip on the reference hardware. Latency stays flat as concurrency rises. Tag-to-action through the IoT worker sits in the same range.
The dedicated xLSTM daemon handles time-series forecast and policy workloads — designed for fast bounded-latency inference on industrial signals. Pre-trained weights still in distillation; runtime ships now.
OPC-UA, Modbus TCP/RTU, MQTT Sparkplug B in the IoT worker. Store-and-forward buffering through disconnect windows. Time-series historian for replay.
Direct GGUF / xLSTM model loading via embedded llama.cpp — no Ollama hop, no extra process boundary. The shortest inference path Eldric ships.
Hard real-time. Sub-millisecond deterministic control. RTOS-grade scheduling. Those are the PLC's job. Eldric sits above the PLC layer, where soft-real-time (10–100 ms) and near-real-time (event-driven streaming) are the right targets.
We are a small Austrian company that does not run a self-service checkout. Every enterprise relationship starts with a conversation. The typical path:
We do not use third-party sales engineers. The person you talk to is the person who knows the codebase.