Install & operate

Self-host or cloud

The analysis engine is identical: every metric, funnel, cohort and evidence query lives in the Apache-2.0 core, and a CI gate proves that the core does not import a single commercial module. What differs today is how much of it the self-hosted server puts on screen.

What differs#

Self-hostedCloud
PriceFree, foreverFree, then from $12/mo
LicenceApache-2.0Commercial
Where data livesYour serverEU (Hetzner, Germany)
Metric engine and evidence queriesYesYes
Overview, digest and replay pagesYesYes
Portfolio, users, lifecycle, heatmapsAPI onlyPages + API
Sessions, journeys, goals, globe pagesNot yetYes
MCP serverModule in the core, not mounted yetYes, with read-only keys
Signed agents and server-side crawler visitsNot yetYes
Teams, roles, invitations—Yes
Quota and billingNot neededIncluded
Backups, upgrades, uptimeYoursOurs
Email and Slack deliveryYour own keysIncluded

Choose self-hosting when#

  • Visitor data must not leave your infrastructure — a legal requirement, not a preference.
  • You are already comfortable running a small service and taking its backups.
  • Your volume is large enough that per-event pricing stops making sense.
  • You want to read the code before you trust the numbers. That is the point of an open core.

Choose the cloud when#

  • You would rather not own another process, another backup job and another certificate renewal.
  • You need team members, roles and invitations.
  • You want digests delivered without setting up your own mail provider.
  • Your time is worth more than $12 a month. For most teams this is the honest answer.

What self-hosting actually costs#

Less than people expect, because there is nothing to install alongside it. No Postgres, no ClickHouse, no Redis, no Kafka. One process and an embedded database file:

bun install -g @vitrus-dev/cli
vitrus init
vitrus site add "My site" example.com
VITRUS_PASSWORD="a long secret" vitrus start

The password guards the dashboard and the read API; the tracker and ingest stay public. Without it, anyone who can reach the port can read your analytics — vitrus start warns you.

A €4 VPS handles a few million events a month comfortably. What it costs you is the upgrades, the backup of one file, and being the person who gets paged. See self-hosting.

Moving between them#

Both directions are possible; neither is one click today. The event schema is identical, so a migration is an export and an import at the database level. If you need this, get in touch — it is on the roadmap and real demand decides its order.

Something wrong or missing on this page? Open an issue or ask in Discussions.