Editions and Support

Editions and Support

⚠️ Pre-launch. Prices below are published so you can plan, but subscriptions are not open yet and nothing here is a contractual commitment until the published terms go live.

---

What you're actually paying for

Elsa Workflows — the engine — is open source under the MIT License and always will be. Nothing is moving behind a paywall.

Valence Runtime sells three things the open source project does not provide:

1. Commitments on the build you are already running — the Community images are the same build. What a subscription adds is a patch cadence you can rely on and tags you can pin to
2. A committed security patch cadence — CVEs patched to a published timeline
3. A bug queue the maintainer actually works — your reports are triaged within a committed window, answered in writing, and weighted above the community queue. On the upper tiers, accepted fixes are backported to the version you run
4. Direct access to the maintainer — on the capped Maintainer Access tier only

You can keep using open source Elsa, and the Community images, for free indefinitely.

---

Tiers

	Community	Runtime	Runtime Priority	Maintainer Access
Price / year	Free	€1,500	€4,500	€25,000
Availability	Open	Open	Open	3 slots
Registry	Public, no account	Private, token issued	Private, token issued	Private, token issued
Hardened, signed, SBOM	✅ same build	✅	✅	✅
Security patch commitment	—	✅	✅	✅
Immutable version tags	—	✅	✅	✅
Bug reports triaged	Public queue	5 business days	2 business days	1 business day
Queue priority	Lowest	Standard	High	Top
Backports to your pinned minor	—	—	✅	✅
Advance security notice	—	—	✅	✅
Direct channel to the maintainer	—	—	—	✅
Quarterly check-in call	—	—	—	✅

All prices are per year, in EUR, excluding VAT. Valence Works is based in the Netherlands: EU reverse charge applies for business customers outside NL, Dutch VAT within.

Subscriptions are not open yet. Valence Runtime is in Early Preview. Prices are published so you can plan and budget — get in touch to discuss a tier or request preview access.

On price changes. These figures are new and untested. They may change. If they do, existing subscribers keep their rate through at least their following renewal, and will be told before any change takes effect. Nobody who signs up early is penalised for it.

Not sure which tier? Most teams running Elsa in production want Runtime. Move up to Runtime Priority if you pin to a specific version and cannot take a whole new minor to get a fix — that is what backports solve, and it is the only reason to pay the difference.

Community images are free, public, and need no account. Pull ghcr.io/valence-works/runtime-ce-{server,studio,combined} without logging in. They are the same build the paid tiers receive — nothing is stripped out. What a subscription adds is commitments and immutable tags, not different software.

Images previously pulled from Docker Hub as valenceworks/elsa-pro-* still work, but are no longer updated.

Community — free

The same images the paid tiers get, free and public, plus the open source engine and a public issue tracker. No patch commitment, no triage commitment, and no immutable tags — so a Community deployment cannot be pinned to an exact build. Right for evaluation, development, and self-supporting use.

Runtime

Hardened images, a committed security-patch cadence, immutable tags and the private registry — plus your bug reports get triaged within five business days and weighted above the community queue. Right for teams running Elsa in production who want their defects actually looked at.

Runtime Priority

Everything above, with two-business-day triage, higher queue priority, advance notice of security fixes — and backports to the minor version you actually run, so a fix reaches you without taking a whole new minor. Right for anyone pinned to a specific version in production.

Maintainer Access

Everything above, with one-business-day triage, top queue priority, a direct channel to Sipke Schoorstra, and a quarterly check-in call. Limited to three subscribers — when the slots are full, there's a waitlist. Right when Elsa is strategic infrastructure.

Project work — implementation, architecture review, migrations, training — isn't bundled into any tier. That's Expert Services, quoted per engagement.

---

Triage is committed. Fixing is not.

Every bug report gets a written answer within your tier's window. No tier promises a fix, or a date.

Time to fix an arbitrary defect depends on its cause, your environment, and third-party components. A promise that can't be honoured is worse than none — for you as much as for us.

What is committed: every report receives one of four written outcomes.

Outcome	Meaning
Accepted	Confirmed as a defect, placed on the roadmap against a target release
Needs information	Can't reproduce it as submitted — here's what's needed
Won't fix	Not a defect, or out of scope — with the reason stated
Already fixed	Resolved in a release, which is named

Your reports are weighted above community reports in the work queue. On Priority and above, accepted fixes are backported to the version line you run.

The one place a time commitment goes beyond triage is security patching, which carries a published cadence.

---

Where to go

The triage commitment attaches to the channel, not to the kind of problem. On a paid tier you can report anything in the images through your private channel — including defects that turn out to sit in the engine.

Your problem is	Go to	Commitment
Elsa engine bug or feature request	elsa-core issues	None — open source
Image / packaging / deployment	Issues here	None — best effort
A question	Discussions	None — best effort
Anything, on a paid tier	Your private intake channel	✅ Triage window per tier
Billing, licensing	Commercial contact — pending	Best effort
Security vulnerability	Security contact — pending	Please don't use public trackers

Filing an engine bug on elsa-core is the right thing to do — that's where fixes land. It just doesn't start a triage clock. On a paid tier, do both.

---

Not included in support

Available as consulting instead:

• Custom feature work and bespoke integrations
• Designing and building your workflows
• Debugging third-party systems and non-Elsa infrastructure
• Self-modified builds, or third-party Nuplane packages
• Unsupported versions
• Performing migrations and upgrades (guidance is included; doing it is not)

Ask — an out-of-scope request gets a quote, not a refusal.

---

Licensing

• Elsa Workflows — MIT, unaffected by any of this
• Community images — free to use; terms to be published
• Paid images — Valence Works Commercial License; require a current subscription

The commercial license grants unlimited deployments within one legal entity — no per-seat, per-server or per-execution limits. Tiers differ by triage speed, queue priority and backports, not by deployment size. There are no license keys, activation, or telemetry in the software; your registry credentials are the license.

Images you have already pulled keep working. There is no kill switch.

---

← Home