Decide: self-hosting free on every tier #68
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda#68
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #37. A decision, not engineering.
What Relay does
Self-hosting is free on every tier, including Free, and they argue for it
publicly in
relay.md/updates/we-dont-charge-for-privacy: "We charge for theconvenience and infrastructure we provide. We do not charge for the architecture
that guarantees your privacy."
Their seat caps still apply and are enforced remotely, and their self-hosted
server still authenticates against their proprietary control plane — so their
self-hosting is partial in a way ours is not.
What we do
Gate self-hosting behind a signed licence at Business/Enterprise (Phase 12,
deferred and currently running last).
The tension
Our entire position is privacy. Charging for the deployment mode they give away
is the one place our pricing reads worse than theirs on our own strongest
ground, and
docs/positioning.mdalready says to price at parity and competeon the claim.
What it would cost
Nothing to build — it deletes Phase 12. No licence file, no signing key, no
offline verification, no key rotation.
docs/commercial-model.mdargues theopposite case (self-hosted is worth far more per customer), and that argument is
on the record and should be weighed rather than skipped.
Why it is filed as an issue
So it is decided deliberately rather than by default. Either answer is
defensible; drifting into one is not.
Decided 21 September 2026: self-hosting stays paid. Closing.
This issue was filed on a false symmetry — that Relay giving self-hosting away
on every tier made our licence gate look like a worse deal at the same price.
It does not, and the reason is architectural.
Free self-hosting is not generosity on their side, it is compensation.
Their server reads plaintext, so self-hosting is the only privacy their
architecture can offer. They cannot charge for the sole route to the thing a
privacy-minded customer came for. We include that privacy in the hosted service,
so we are not selling the same product at a worse price — we are selling a
different one.
It is also not a complete answer even for them. Per their own deployment
template, a self-hosted Relay Server on the public internet is one their control
plane can mint itself a token for; privacy needs the customer to run a VPN as
well, and a public-facing server is grounds for removal from their network.
So the comparison is:
At the same price our customer gets hosting, support and privacy together. A
Relay customer wanting the equivalent runs their own server and their own VPN
and still holds a Relay account with seats enforced remotely.
Matching their free tier would discount the claim, not the product —
contradicting
docs/positioning.md's "price at parity, compete on the claim".Recorded so it is not re-litigated:
docs/positioning.md— new section "Their free self-hosting is not abenchmark, and we do not match it", with the side-by-side answer to use when
someone compares the two feature tables.
docs/commercial-model.md— the open question under "What this does notdecide" is now settled there.
One guard kept in the positioning text: E2EE removes the main reason to
self-host, not every reason. Metadata, residency, procurement rules and air-gap
survive it — which is exactly the market the paid tier serves. Do not say
"nobody needs to self-host any more".
Phase 12 stands as planned.