Self-host vs SaaS

OpenSense is offered as a SaaS today. The codebase will eventually be open-sourced, but is not today. This page exists because the question "can I self-host" comes up before signup more often than I expected.

The short answer

Today: no, you cannot self-host. The repo is private.

In 2027: yes, you will be able to self-host the same binaries we run, with the same Postgres schema, under a non-commercial source- available licence (think Sentry, Mattermost, Plausible). The SaaS stays the supported path for everyone who does not want to be a sysadmin.

Why not open today

I am a solo founder; the SaaS is the revenue engine that lets me work on this full-time. Opening the source on day one would put me in the position of supporting customer-run installs while still trying to ship features. That is not a good time allocation for the first 24 months.

The compromise is commit to open-source by 2027 and commit to the data-portability features now: every customer can fully export their data, the audit trail is verifiable externally, and the API is not a moat.

When SaaS is the right answer for you

• You are a small operator (1–10 sensors). Self-hosting costs more than the SaaS fee in your own time. Buy the SaaS.
• You want EU jurisdiction and EU data residency without operating a server. The SaaS gives you both.
• You want monthly automatic updates without thinking about it.
• You do not have a Linux sysadmin on staff.

When self-host will be the right answer (in 2027)

• You operate in a regulated environment that forbids data leaving your premises (defence, certain government, certain pharma).
• You are an MSP that wants to brand the product as part of your service catalogue.
• You are a hospital network running 200+ sensors and the SaaS pricing crosses the break-even with operating a server.
• You have a Linux sysadmin and an existing Postgres deployment you want to lean on.

What the self-host bundle will include (target)

• Docker Compose stack: Postgres + TimescaleDB, EMQX, Caddy, OpenSense ingest, OpenSense rule engine, OpenSense dashboard, PDF service.
• A bin/admin CLI for account / device administration.
• Per-machine licence key for support; no licence key for the software itself (it boots without one).
• Same data schema as SaaS. We will write a migration helper so customers can move SaaS → self-host (or back).

What the self-host bundle will not include

• Our SaaS hosting. Run it on your own host.
• Email delivery via our Postmark account. Plug in your own SMTP.
• The Telegram bot's identity. Create your own bot for your customers.
• 24/7 support. Self-host support is best-effort, paid SLA on request, business hours only.

What we will not do

• Restrict features in the open-source build that exist in the SaaS. The product is the product; the SaaS is the convenience.
• Build a separate, weaker, "community edition". The open-source build is the same code.
• Track usage from self-host instances. They will not phone home.

How to register your interest

Email grande.chuvash@gmail.com with your use case. Self-host customers will get early access in late 2026.