Hosted or self-hosted
Same product. You choose where it runs.
Tenvara is available both ways, with every feature. Hosted means nothing to install or maintain. Self-hosted keeps every byte on infrastructure you control.
Hosted by us
yourname.tenvara.app
A dedicated instance with its own database, set up for you when you order. You sign in and the setup helper walks you through the rest.
- Dedicated instance and database per MSP
- Updates applied for you
- Backups of your instance
- TLS certificates and DNS handled
- Monitored by us
- Your own address on tenvara.app
Self-hosted
Docker Compose on your own server
One install per MSP on a Linux server you run, in your office, your data centre or your cloud account. A licence key from your account switches it on.
- Runs with docker compose up
- Postgres, Redis and S3 compatible storage under your control
- Caddy in front with automatic TLS
- Upgrade on your own schedule
- Licence and keys managed from your account
Side by side
What changes, and what stays the same.
The features are identical. What differs is who looks after the server.
Weighing up what one platform means for your risk? Read one platform, not one risk, or see how to move over gradually.
Self-hosting
Three commands and you are signing in.
One compose file brings up the web app, the API, background work, realtime, backup and remote access services, Postgres, Redis and MinIO, with Caddy handling TLS. The installer picks a small, standard or large profile from the server's processors and memory, so a small server runs it comfortably.
Read the full install guide# on your server $ cd tenvara $ cp .env.example .env # domain, licence key, secrets $ docker compose up -d # then open https://your-domain and sign in
Licence and releases
Self-hosted, without the surprises.
A self-hosted install checks in once a day. It never sends customer data, and it never locks your data away.
Signed releases
Release images are signed, and the installer checks every one before it starts anything. Only compiled code ships.
A daily check-in
Counts, version and build hashes only, never customer data. Offline licences cover installs kept off the internet.
Grace, then read-only
If check-ins fail or a licence ends, you get 14 days of grace, then read-only. Nothing is ever deleted, and restores always run.
Agent updates in rings
New agent versions come from the release feed, go to a pilot ring first, soak, and halt on any failure. An agent update holds back while the device is backing up. No installers to upload.
Updates that wait
An update waits for running device backups and restores, checks it can write what it needs before changing anything, upgrades the database first and puts the running version back if that fails.
Sized for you
Two virtual CPUs and 8 GB is enough for about 1,000 devices, and four with 16 GB for about 3,000. Beyond that the backup service moves to its own server.
System status
One page shows what each queue is doing, what is holding one up and how the install is sized, and raises an alert when something waits too long.
Backups carry on
A backup interrupted by an update or a restart carries on from its checkpoint, and you hold a recovery copy of the encryption key that you have checked opens.
Start small
A new install starts with the service desk. Switch on the next module when you are ready: it sets up what it needs and walks you through its steps, and switching one off keeps its data.
Copies that land elsewhere
An ordered copy list sends every repository's second copy to the first location that is not its own, and Make primary swaps locations without leaving anything uncopied.
Repositories that heal
A damaged part of a backup is replaced from the other copy, or read again from the source by the next backup, and stored data is verified on a schedule or when you ask.
Your uplink, your rules
Second copies and Microsoft 365 backups that go offsite over your own connection keep to the window and budget you set, so they fit around everything else on your line.
White-label, either way
Your customers see your brand.
Hosted or self-hosted, brand profiles put your name, logos and colours on the portal, emails, invoices, status pages and the agent's tray and installer, per customer if you want, on your own domain once your DNS points at it.
How white-label works
Hosted or self-hosted, your call.
Tenvara is coming soon. Apply for the beta and tell us which you prefer. Weighing up self-hosting, compliance or where your customers' data should live? Contact us and we will give you an honest answer.