Correct diagnostics that a chiselled image cannot run docker exec printenv/cat/curl fail with 'executable file not found' on these images, and a Compose healthcheck of CMD curl leaves the container unhealthy forever. Replaced with host-side equivalents verified against a running container. Also fixes the pre-rename image names in Choosing an Image and a stale 'landing next release' claim about signing and SBOM.
Point paid images at ACR; correct signing, SBOM and tag claims The paid line now publishes to a private Azure Container Registry rather than GHCR, which could only share private packages with organisation members. Subscribers are issued a pull-only registry token and need no GitHub, Microsoft or Azure account. Also corrects claims that had gone stale in both directions: - Signing, SBOM and build provenance were described as 'in the pipeline' on three pages while two others already advertised them as shipped. They are live on both lines and verifiable; the tables now say so consistently. - The tag table documented a scheme (3.8.1, 3.8-stable) that no build has ever published. Replaced with the tags that actually exist. - runtime-studio is versioned on Elsa Studio, not the engine, so its tag differs from server and combined. This was undocumented and is an easy way to write a manifest that cannot be pulled. - Troubleshooting still told subscribers to log in to ghcr.io with a read:packages token and described access as following team membership. Every image reference on every page was checked against the live registries.
Correct the reconciliation guidance EnableAutomaticReconciliation is no longer silently ignored — the longhand now takes precedence over the Setup shorthand, so the page no longer tells readers that Setup:AutomaticReconciliation is the only key that works. The upgrade note now covers both defects an operator coming from an earlier image might recognise: the discarded explicit false, and the scheduled cycles that left reconciliation permanently degraded without surfacing on /health.
Fix contradictory guidance on read-only package mounts The Production Checklist said in one paragraph that a package directory may be mounted :ro, and in another that it cannot — the second was left over from before the behaviour changed. Removed, and the Studio note corrected alongside it: Studio needs no writable mounts at all. Also fixes a stale count: three writable paths are listed, not two.
Read-only root and offline startup are now supported Documents behaviour that changed in the images published today. - readOnlyRootFilesystem works. Mount /data (SQLite only), /var/lib/valence-runtime and a tmpfs at /tmp, and the root filesystem can be read-only. Package directories may be mounted :ro. - Offline and air-gapped startup works, via a mounted package directory holding the full transitive closure of the packages you use. - Writable paths are documented, including the one that is easy to get wrong: HOME lives on /var/lib/valence-runtime, so the Data Protection key ring is there too, and an emptyDir signs users out on every rollout. - Kubernetes manifest gains a securityContext with fsGroup 1654. Without it a non-root container cannot write to its own root-owned volumes. BREAKING, and the reason for the new Release Notes page: the default SQLite path moved from elsa.db (relative to /app) to /data/elsa.db. Anyone relying on that default while mounting a volume at /app must move the mount; the page carries migration commands and an escape hatch. Automatic package reconciliation now ships off, so package changes follow your deploy schedule rather than a timer.
Images are now non-root on a chiselled base CVE gating, SBOM and signing are in the pipeline. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Community edition publishes to GHCR as public packages ghcr.io/valence-works/runtime-ce-{server,studio,combined} — free, no account, same build as the paid tiers. What a subscription adds is commitments and immutable tags, not different software. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Publish pricing Community free / Runtime EUR 1,500 / Runtime Priority EUR 4,500 / Maintainer Access EUR 25,000 (3 slots), ex-VAT. Subscriptions are not open yet; prices are published so buyers can plan. Existing subscribers keep their rate through at least their following renewal if prices change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Restructure tiers around triage and backports Community / Runtime / Runtime Priority / Maintainer Access. The commitment is triage with a written disposition, never a fix. Backports to the pinned minor differentiate the upper tiers. Maintainer Access is capped at 3 slots. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Rename product to Valence Runtime Images are now ghcr.io/valence-works/runtime-{server,studio,combined}. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Add Elsa Pro documentation Pulling, running and configuring the container images, plus persistence, Nuplane extensibility, a production checklist and troubleshooting. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Initial Home page