One platform, not one risk
One platform, without putting all your eggs in one basket.
Bringing your service desk, devices, backup and documentation into one place is a big decision, and it is right to ask what happens if that one place has a bad day. Here is what Tenvara does about each risk, in plain terms.
A fair question
Concentration risk is real. So is the risk of a dozen tools that barely talk to each other. The aim is to keep the benefits of one platform and take the sting out of the risks.
Below, each worry gets the honest version: what it is, what Tenvara does about it today, and where to read the detail in the knowledge base.
If it goes down, does everything go down?
The worry
One platform is one thing to keep running, and an outage would be felt across your whole service. That is the first thing most MSP owners ask, and they are right to.
Tenvara is in beta, so rather than quote figures, here is how it is built and what stays in your own hands.
- Your own instance
- Every hosted MSP gets a dedicated instance with its own database, not a seat in a shared pool. We look after its updates, backups and monitoring.
- Or run it yourself
- Self-hosted Tenvara is the same product on a Linux server you run, in your office, your data centre or your cloud account. You choose where it lives and when it updates.
- Updates that wait their turn
- A self-hosted update waits for running device backups and restores, checks it can write what it needs before changing anything, and the System status page raises an alert when work waits too long.
- Passwords you can reach without Tenvara
- The break-glass export is an encrypted copy of the credentials vault that opens in any browser, offline, approved by a second administrator. It is there for the day you need a password to fix the thing that holds your passwords.
- Backups that carry on
- A backup interrupted by a restart or an update carries on from its checkpoint, and every backup carries its own catalogue, so a new server given the storage and the keys can rebuild it.
Would one breach expose everything?
The worry
A platform that can reach every customer's devices and tenants is a valuable target. Putting more in one place raises the stakes of protecting that place well.
So the access model is strict by default, and every sensitive action leaves a trail.
- Strong sign-in
- Two-factor or passkeys for local accounts, and admins can make two-factor mandatory. Or single sign-on with Entra ID, Google Workspace, OpenID Connect or SAML 2.0.
- Staff see only their customers
- A technician scoped to some customers sees only those customers, enforced in the database itself, across every table, report, search and notification.
- Two people for risky actions
- Scripts on many devices, software to a whole customer, vault exports and remote sessions to sensitive devices can be set to need a second person's approval.
- A log that shows tampering
- Sign-ins, settings, exports, remote sessions, scripts and credential reveals go into one hash-chained audit log, checked every day.
- A signed agent that pins its server
- Agents and the scripts they run are signed, remote sessions open only from a request signed by your server, and each agent refuses anyone in the middle holding an otherwise valid certificate.
Would we be locked in?
The worry
Once your tickets, documentation, devices and billing live in one system, leaving it sounds hard. Nobody wants their customers' history held hostage by a supplier.
Your data stays yours, in formats other tools can read, and there are several ways to take it out.
- Export from any list
- Every list exports to CSV or Excel, with the columns you choose, across every page of results.
- A customer's data in one ZIP
- The offboarding export gathers a customer's details, documentation, assets, tickets, contracts and invoices, with credentials sealed under a passphrase and an offline viewer.
- A full API
- Everything the app does goes through its REST API, with the complete OpenAPI contract to download, scoped tokens, and webhooks signed to the Standard Webhooks specification.
- Storage you own
- Customer backups can go to your own S3 compatible storage, locked with Object Lock if you like. Self-hosted, the database sits on your own server.
- Never locked away
- If a self-hosted licence lapses, Tenvara gives 14 days of grace and then goes read-only. Nothing is deleted, everything stays visible and exportable, and backups, restores, agents and monitoring carry on.
You are a young company. What if you change course?
The worry
Tenvara is new. Choosing a young supplier for something this central is a fair thing to think hard about, and we would think hard about it too.
We would rather you go in with your eyes open. Here is where things stand.
- A beta, said plainly
- Tenvara is in early access. MSPs join in small groups, so each group is well supported, and what they tell us shapes what we build next.
- Nothing to pay during the beta
- You are not asked for a card to apply or to take part, and pricing is announced before launch, so you know where you stand before you commit.
- A direct line to the team
- Questions, problems and ideas go straight to the people building Tenvara. Reply to any of our emails.
- Your exits stay open
- Exports, the API and the self-hosted option mean your data is never only in our hands. The section above has the detail.
- Built by people who run an MSP
- We run our own MSP on Tenvara every day, so we know what it means to hand a platform the keys to your customers.
Would we have to change everything at once?
The worry
Swapping a whole stack in one go is a big risk of its own. A bad weekend can turn into a bad month for your team and your customers.
You move at your own pace, one part and one customer at a time, and keep the specialist tools you trust.
- One module at a time
- A new Tenvara starts with the service desk, and Settings > Modules shows what every other module gives and needs. Switch the next one on when you are ready. A module switched off is hidden, its work stops and nothing in it is deleted.
- Keep your security tools
- Microsoft Defender and SentinelOne connect with your own accounts, so their alerts arrive as detections in Tenvara.
- Keep watching your backup vendor
- Datto BCDR, Cove Data Protection and Veeam connect too: Tenvara reads what each protects and raises alerts for failed or missed backups.
- Documentation in step
- The IT Glue and Hudu connectors keep documentation coming across for as long as you run both, and nothing is ever deleted on either side.
- Read only, on the way in
- Importers only read from your old tools. Nothing is ever written back to them, so they stay exactly as they were until you decide.
The other side of the scales
Spreading tools spreads some risks, and adds others.
Neither way is free of risk. A stack of separate tools carries its own, and it is worth weighing them side by side rather than comparing one platform against a perfect world.
-
Several vendors and contracts
Each with its own renewal date, price rises, terms and support queue to chase.
-
Several agents on every machine
Each running with high privileges, each updating on its own schedule, each another thing to troubleshoot.
-
Several logins with admin rights
Each another account to protect, with its own two-factor, its own offboarding and its own audit trail.
-
Integrations to look after
Links between tools that need fixing when one side changes, and customer details copied between systems that drift apart.
-
More places to watch
Every console with access to your customers is somewhere an attacker could try, and somewhere your team has to keep an eye on.
Questions to ask any vendor.
Whoever you choose, these are worth asking before you hand over the keys to your customers. Ask us too: we will answer each one in writing.
Ask us these questions- 1 Is my data kept in a database shared with other customers, or on its own?
- 2 Can I run the product on my own infrastructure if I need to?
- 3 How do I get all of my data out, and in what formats, without asking you?
- 4 What happens to my data and my customers' devices if my subscription or licence ends?
- 5 Who can see my customers' data, on your side and mine, and is every access logged?
- 6 How is the agent signed, and how are new versions rolled out?
- 7 Can I adopt one part at a time, and switch parts off again?
- 8 Does it work with the security and backup tools I already trust?
- 9 Who do I speak to when something goes wrong, and how quickly do they know my setup?
Moving to Tenvara, one step at a time
Start with one area and one customer, run alongside your current tools, and switch each one off only when you are confident.
Hosted or self-hosted
The same product on our infrastructure or yours, side by side: updates, backups, data location and licence.
Questions
What MSP owners ask before they commit.
Something else on your mind? Ask us directly, or read how Tenvara is secured.
Any system you rely on is one. What matters is how it is run and what you keep in your own hands. Hosted, each MSP gets a dedicated instance and database that we update, back up and monitor. Self-hosted, it runs on your own server. Either way you can keep an offline, encrypted copy of your credentials vault, and export your data at any time.
No. Every hosted MSP gets its own instance at yourname.tenvara.app with its own database. Self-hosted, everything stays on infrastructure you control.
You can export every list to CSV or Excel, export each customer's data as a ZIP, and read everything through the REST API at any time. On a self-hosted install whose licence ends, Tenvara becomes read-only after 14 days of grace: nothing is deleted, everything stays exportable and restores always work.
No. A new Tenvara starts with the service desk and the other modules switch on one at a time, and Tenvara connects to Microsoft Defender, SentinelOne, Datto BCDR, Cove, Veeam, IT Glue and Hudu with your own accounts, so you can keep the specialist tools you trust and bring each job across when it suits you.
Two-factor or single sign-on, staff scoped to their customers in the database itself, a second person's approval for risky actions, a hash-chained audit log, encrypted secrets with every reveal recorded, and a signed agent that pins your server's key. The security page has the full list.
Beta members get the full product, and invitations go out in small groups so each one is well supported. Nothing is charged during the beta, and you have a direct line to the team. Start with one customer or one job and move more across as your confidence grows.
Yes. Every import has a dry run that writes nothing, a check that every row is accounted for, and an undo. The moving to Tenvara page walks through a gradual move step by step.
Talk it through with us.
Tenvara is coming soon, and we are inviting MSPs to the beta in small groups. Apply and tell us what worries you most about one platform: we would rather answer it properly now than have it hold you back later.