Eldric ships three clients, one toolset. They work against your own Eldric cluster — or, if you only have a laptop, they talk directly to whichever provider you choose. You decide which.
Open a browser, you have ChatGPT. Hosted by your own Eldric server, themed per tenant, with knowledge-base search, voice in / out, plugins, and signed share-links — all included.
Pipe-friendly for shell scripts, interactive for everything else. Talks to a cluster or directly to any backend you like. macOS today; Windows and Linux in development.
A native desktop GUI that talks to your Eldric cluster or straight to OpenAI, Anthropic, xAI, Groq, Together, HuggingFace, or a local Ollama. One tool, every backend. macOS today; Windows and Linux in development.
The same GUI that you use without a cluster — for solo work, with whatever API key you bring — unlocks multi-tenant projects, agentic RAG, training pipelines, and the matrix-memory architecture the moment you point it at an Eldric server. Two modes, one client, one workflow.
Eldric is the operating system for sovereign AI compute — and the AI server, the AI infrastructure, and the AI platform for every organization built around it. Pick the angle that matches your role.
National AI factories and member-state-funded compute capacity. Run AI workloads under your jurisdiction's data-residency, procurement, and security frameworks — without depending on a hyperscaler.
Public research labs, national HPC fabrics, and consortium-led AI compute programmes. Multi-tenant, multi-discipline, multi-jurisdiction — managed centrally, controlled locally.
Private chat, agents, knowledge bases, training — running on your own hardware. The data never leaves your network. For banks, hospitals, universities, factories, public sector.
Eldric is a complete AI infrastructure platform that sits on top of your compute, storage, and network. Multi-tenant, federated, plugin-driven, with HA built in.
ISP, MSP, telco, regional cloud? Run Eldric on your hardware and offer Private AI to your enterprise customers as your own white-labelled service — they never see a hyperscaler.
These are the things people actually use Eldric for. Each one is a single click in the chat shell.
Talk to an AI like ChatGPT. The conversation stays in your database, on your network.
Upload documents, ask questions across them. Sources are cited inline so you can check the answer.
Speak instead of type. Meeting transcripts, dictation, accessibility input. Telephone-style AI calls are in development.
Drafts replies to email, SMS, WhatsApp, Signal, Teams. A human approves before anything sends.
Fine-tune a model on your own data (LoRA, QLoRA, DPO). Your data never leaves the building.
Read PLCs, OPC-UA, Modbus, MQTT Sparkplug B. Predictive maintenance, alarm triage, OEE analytics, shift-handover notes. Edge-deployed, soft-real-time — ~50 ms tag-to-action on the demo cluster. The strongest production-tested workload today.
One hundred and forty integrations to NASA, CERN, PubMed, NCBI, GBIF, IAEA, and more. Ask in plain English.
Repo search, ticket triage, doc generation, test writing — your own private Copilot, on your own GPUs.
Each team gets its own tenant: separate data, separate model access, separate billing. One server, clean walls.
Tools written against the OpenAI API work unchanged. Point them at your Eldric and go.
Eldric is the same binary on every target. What changes is how much of it you switch on — and the resource budget it gets to play with. A field engineer on a Pi gets classification and short completions. A hospital network running a cluster gets multi-tenant agentic RAG and federated training. A national-AI compute programme running across a thousand nodes gets the same kernel sized to the metal underneath. Same software, scaled to the hardware.
The Pi 4 (8 GB) runs the kernel and a small model end-to-end — enough for classification, short completions, and IoT-style ambient AI on a sealed device.
A developer laptop or engineering workstation runs the GUI client and a local Eldric in tandem. Cloud-free dev loop. Fly without WiFi.
One tower, one GPU, one team. A small business or department gets the whole platform on a single box without a cluster manager.
Mobile robots, AGVs, inspection drones, and in-vehicle stacks carry an embedded Eldric kernel for on-device perception, voice command, and recovery decisions when the radio link is out.
Multi-node deployments across racks, datacenters, or building floors. Rolling upgrades, automatic failover, multi-controller HA, federated learning. The full stack.
HPC fabrics, EuroHPC-adjacent compute, national-AI capacity programmes. Thousands of nodes, the same kernel, the same module surface — just bigger resource budgets and federation across sites.
Other targets ship in the same RPM / DEB / PKG today: edge gateways, kiosks, retail-store back-rooms, ships, oil rigs, mobile clinics. Anywhere you can run a Linux box, you can run Eldric.
Measured, not promised. The demo cluster runs one inference GPU (RTX 4070 Ti, 12 GB) plus one router GPU (RTX 2080, 8 GB). Smaller deployments scale linearly down; larger ones up.
Knowledge-base search at concurrency four still hits a ~7 second p50 latency cliff. Multi-user concurrent search is the next engineering focus — we will publish numbers when it lands. We do not claim sub-second search at scale today. Honest scope · 2026-05-15
Each one links to a fuller page. The common thread: data that cannot leave the building.
Eldric integrates the xLSTM architecture from the lab of Sepp Hochreiter at JKU Linz — the inventor of LSTM, one of the foundations of modern deep learning. We ship the runtime; we contribute training and integration work; we are honest about which pre-trained weights are public and which are still in distillation.
— On Eldric and the xLSTM architectureWe are an independent platform that runs xLSTM models, classical transformers, GGUF inference, and most other backends you can name. We sit in Vienna and follow the European AI research community closely — every claim on this site you can verify in the public code or in published papers.
The science worker ships GLP and FDA 21 CFR Part 11 modes. The whole platform sits on GDPR-compatible infrastructure — by virtue of running in your building.
Eldric installs on a Raspberry Pi 4 for a single-team trial, or across a multi-node cluster for a hospital network. The download is the same; the configuration changes.