Road to 5.0 GA

Eldric 5.0.
Almost shipped.

The 5.0 GA tag is approaching. This page collects the prep you can do today — hardware sizing, supported distributions, license-tier matching, install path — so the cutover is uneventful when the release goes out.

We don't publish commit dates. The 5.0 cut goes out when the GA criteria are met on the live cluster and the last few hard rows close. If you want a heads-up for when that lands, write to office@eldric.ai.

Where we are this week

Live status against the GA criteria.

Three concrete signals updated weekly as the gates close:

Smoke pass rate. The 106-check end-to-end suite now sits above the GA threshold (≥ 99/106 green) on the demo cluster — a recent registry fix collapsed six interrelated reds in one ship. The remaining open items are tracked as preview-feature WIPs in the features catalogue and don't block the cut.
Industrial transports. Modbus, WebSocket and the publish half of MQTT-Sparkplug-B are GA. OPC-UA ships at preview through 5.0 RC1 — the C++ source is in, the open62541 library bundles into the RPM at the next cut. MQTT-subscribe stays preview through 5.0. Details on xLSTM & IoT and known issues.
Cross-distro packaging. Fedora 42+, Fedora 40, RHEL 9+, Rocky 9, Alma 9, CentOS Stream 9+, ARM64 and macOS ship signed packages at the cut. Ubuntu 24.04 and Debian 12 native DEBs follow shortly after GA; today's WSL2 / container path is documented per-distro: Fedora 40 · RHEL 9 · Ubuntu 24.04 · Debian 12.

Hardware sizing

What to plan for.

Eldric scales across a wide range of hardware. Pick the row that matches your deployment shape:

Deployment	RAM	Storage	GPU	Typical role
Edge node (Pi 4 / NUC / Jetson)	4–8 GB	32 GB+	optional	branch office, factory line, autonomous platform
Single-team workstation	16 GB	256 GB	recommended	solo developer, small team evaluation
Department server	32–64 GB	1 TB+	1× consumer or pro GPU	10–50 user deployment, single tenant
Multi-node cluster	per-node 64 GB+	per-node 2 TB+	1–2× per inference node	multi-tenant, multi-department
Enterprise cluster	per-node 128 GB+	per-node 4 TB+	data-centre GPUs	multi-region, federated, regulated

The minimum-edge footprint at GA is 4 GB RAM + 32 GB storage. Hardware below that floor (Pi Zero, Pi 3, BeagleBone) is not officially supported.

Supported distributions

Where 5.0 installs at GA.

Distribution	Status at GA	Package
Fedora 42+	✅ supported	RPM (signed)
RHEL 9+ / Rocky 9+ / Alma 9+	✅ supported	RPM (signed)
CentOS Stream 9+	✅ supported	RPM (signed)
ARM64 minimal (Pi / generic / Jetson)	✅ supported	RPM (signed, aarch64)
macOS 13+ (Intel + Apple Silicon)	✅ supported	PKG with auto-update
Fedora 40, RHEL 9	✅ supported	RPM (signed) — Fedora 40 · RHEL 9
Ubuntu 24.04, Debian 12	🟡 native DEBs shortly after GA	WSL2 / container today — Ubuntu 24.04 · Debian 12
Windows native	5.1 deferred	WSL2 path works today
Android native	5.1 deferred	—

License tiers

Which tier matches your shape.

Free. One controller, one router, two workers. Full kernel features for evaluation and small-team work. Suitable for indefinite use at the size cap.
Standard. Scaled-up node counts, multi-tenant up to a small cohort, Modbus + WebSocket transports for IoT, the full RAG / training / agent worker stack.
Professional. OPC-UA + MQTT industrial transports, the advanced-retrieval previews (compressed memory, distilled router), federated learning, advanced cluster operations.
Enterprise. Source access, multi-region capacity, hardware binding, priority support. The tier for regulated and very-large deployments.

Per-tier details on pricing. License files come from license@core.at and ship as a single signed JSON drop-in.

What to do today

A pre-flight checklist.

Pick the row above that matches the deployment shape you want. Map it to hardware you can stand up — or use what you already have if it fits.
Try the alpha line. The 5.0 alpha (current) is installable today via get started. Anything you run on alpha will upgrade cleanly to 5.0 GA via the rolling-update orchestrator.
Decide on a tenant model. One tenant per team is the most common shape. Per-department, per-study or per-customer tenancies all work; the per-tenant export means you can re-shape later without data loss.
Plan your data ingress. Read apply Eldric to your domain and your data for the pattern. Decide whether you want to ingest documents into a knowledge base, train a small model on your historical traffic, or both.
Have a license tier in mind. For evaluation you don't need a license at all; the free tier ships with every install. For production scaling, write to license@core.at with your target shape and we'll size a license to fit.
Read the release notes for the 5.0 scope. Features lists everything that ships; WIP markers tag what's deferred to 5.1.

When 5.0 ships

What happens at the cut.

At the GA cut, three things change:

The repo flips. repo.eldric.ai/5.0/ serves 5.0 GA RPMs and PKGs. The alpha line stays available at its own paths for customers who haven't upgraded yet.
The release notes finalise. /release-notes.html updates with the final version-stamped headline and any last upgrade-path notes.
The roadmap pivots to 5.1. Items deferred from 5.0 (customer-named roles, full federation, offline-mode automation, ENRN v8, dream-engine orchestration) become the 5.1 inclusion list.

We don't pre-announce a specific date. The cut goes out when the GA criteria are met and the smoke pass rate stays at GA-quality for the soak window. Watch what's new for the announcement.

Eldric 5.0.Almost shipped.