Host the software that respects you. and pay the people who wrote it.
Managed Matomo, Listmonk, Nextcloud, Vaultwarden, Uptime Kuma and more, on EU servers. No telemetry, no seat pricing, no upsell emails. Ten percent of every hosting fee goes upstream to the project you're running — and we publish what we sent.
the fee, split — ten percent walks upstream every month
Your hosting fee
Every month, without exception
PAID THIS MONTH: MATOMO · LISTMONK · NEXTCLOUD · VAULTWARDEN · UPTIME KUMA
§3 — How the 10% works
No catch. Here's the mechanism.
01
The amount
Ten percent of your invoiced hosting fee, calculated per project you actually run — not averaged across the whole company, and not calculated on a smaller number.
02
When it's paid
Monthly, on the same cycle as your invoice. Not annually, not "eventually" — it moves on the same clock your payment does.
03
It's published
We total what went where and say so. The line above — PAID THIS MONTH — is the shape of the real monthly ledger, one entry per project.
§4 — The app catalogue
Run one of these. We fund it while you do.
Every app below is the real, unmodified upstream project — installed, patched, backed up and TLS-terminated for you. The pink edge on each card is the ten percent; hover one to watch it move.
Matomo
Privacy-first analytics. No cookie-banner theatre, no data resold.
Listmonk
High-performance mailing lists and newsletters, self-hosted.
Nextcloud
Files, calendar, contacts — one private cloud you actually own.
Vaultwarden
A Bitwarden-compatible vault, run by you, not a vendor.
Uptime Kuma
Status pages and uptime monitoring, no third party watching your stack.
Gitea
Lightweight Git hosting — repos, issues, CI, no seat tax.
Jitsi
Video calls. No account required for guests, no recording sold.
Mattermost
Team chat that isn't training a model on your messages.
Grafana
Dashboards for whatever you're measuring, wired to your own data.
Wiki.js
A wiki that looks like it's from this decade, and stays yours.
§5 — The tool
SaaS Escape Plan
Pick what you're paying for today. We'll swap in the open-source app we host instead, and show you what's left over — and what goes upstream.
Most SaaS pricing is per seat — this slider is the multiplier on the per-person tools below.
Your SaaS stack, per year
Self-hosted with us, per year
You save
Pick at least one tool above to build your escape plan.
How we calculate this
§6 — Why now
Why self-hosting stopped being hard
Self-hosting used to mean running your own mail server and hoping. That reputation is a decade out of date. Matomo, Nextcloud, Vaultwarden and the rest are now maintained, documented, upgraded-in-place open-source products with the same release discipline as anything on a SaaS pricing page — the only thing missing was someone willing to run the server, patch it at 3am, and answer the ticket when TLS expires. That's a hosting problem, not a software problem, and hosting problems are the one thing this company knows how to solve. So we solved it the boring way: we run the actual upstream project, keep it patched, back it up daily, and hand you an admin login on day one. The software doing the work is the same software a thousand other people run for free. The only thing you're paying for is not having to be the one on call — and knowing that a slice of what you pay funds the people who built the thing you're running.
§7 — What we don't do
What we don't do
- No telemetry bolted onto the apps we host — if the upstream project doesn't phone home, we don't add a feature that does.
- No seat pricing — Nextcloud with three users or thirty costs the same tier price.
- No upsell emails engineered to make the free tier worse than it used to be.
- No lock-in: every app here exports in its own upstream format — the same one you'd use if you ran it yourself — so leaving is a data export, not a negotiation.
§8 — FAQ
Questions people actually ask
What does "10% goes upstream" actually mean?
Every month we total what we billed for the accounts running each open-source project — Matomo, Listmonk, Nextcloud, Vaultwarden, Uptime Kuma and the others — and send ten percent of that revenue directly to the project, through whichever donation channel its maintainers have set up. It's ten percent of what you paid for hosting that specific software, not ten percent of profit, and not a marketing line attached to some other budget.
Which project gets paid if I run more than one app?
Each one, proportionally. If your account runs Nextcloud and Vaultwarden, the ten percent from your invoice is split across both projects according to what you're actually running, so neither one loses out to the other.
Do you run vanilla upstream software, or your own fork?
Vanilla upstream — patched and updated on our schedule, never rebranded or modified to lock you in. If you could run it yourself from the project's own source, you're running the same thing here, just already installed, backed up, and behind TLS.
What if a project doesn't have anywhere for us to send money?
Most of what we host does — a foundation, a sponsorship page, or a maintainer-run fund. For the handful that don't yet, we hold that project's share in a running total until they set one up, and say so plainly instead of quietly keeping it.
Is there a minimum term, or can I cancel any time?
Cancel any time from your client area — nothing here locks you into a contract length. Since your data lives in the upstream project's own export format the whole time, leaving is a file download, not a migration project.
How is this different from just self-hosting it myself for free?
Nothing stops you from running Matomo on your own server for the cost of your time — plenty of people do exactly that. What we sell is the tedious part: patching, backups, TLS and monitoring, handled for you, plus the fact that ten percent of what you pay for that convenience goes back to the people who wrote the software, instead of staying with us.