SecuriveFor MSPs
Backup for managed service providers
Every client isolated, one console to run them all, your brand on the login page, and billing that matches what each tenant actually consumed.
No credit card · 14-day trial · Migration assistance included
The problem
What goes wrong today
One login each
A console per client
Managing twenty clients through twenty separate portals means nobody has a single view of what is failing this morning.
Guesswork
Billing that doesn't match consumption
Without per-tenant usage figures, clients get billed on an estimate — which either burns margin or starts an argument.
Someone else's brand
Your client sees your supplier
A portal carrying another vendor's name tells your client exactly who to call to cut you out.
How it works
What Securive does about it
Hard isolation per tenant
Each client gets its own datastore, its own encryption key and a quota enforced at the filesystem — one tenant physically cannot consume another's storage.
One console for every client
See failures, unprotected machines and storage across the whole book of business in a single view, then drill into one tenant.
White label on your domain
Your name, your logo and your colour, served from your own hostname with a certificate issued automatically. Your clients never see ours.
Per-tenant usage and billing
Actual consumption per client, so invoices reflect reality and margin is visible per account rather than in aggregate.
Scoped client access
Give a client's own staff restore rights to their machines only — not to the console, not to each other's data.
API for your PSA
Usage, job status and alerts are available over the API, so tickets and invoices come from the systems you already run.
Specifics
The technical detail
- Tenancy
- Isolated datastore and key per client
- Quotas
- Hard, enforced at the storage layer
- Branding
- Logo, colour, custom domain per tenant
- Roles
- Provider staff · tenant admin · restore-only client
- Billing data
- Per-tenant consumption over API
- Onboarding
- New tenant provisioned in minutes
Known limitations
Published deliberately. You would find these during a proof of concept anyway — better to find them now.
- White label and multi-tenancy are on Scale and Enterprise. They are not available on the smaller tiers, because the isolation they require has a real infrastructure cost.
- A custom domain needs a DNS record you control and a verification step — deliberately, so nobody can point a hostname at another provider's tenant.
- Billing integration is API-first. There is no built-in invoicing engine; the data is exposed for the PSA or accounting system you already use.
Recovery scenarios
What actually happens on the bad day
One client is hit, the rest must be unaffected
Tenants are isolated at the storage layer with separate keys, so an incident in one client's estate cannot reach another's restore points.
Contained to one tenant, recovered from copies the attack could not delete.
A client leaves and wants their data
Export that tenant's restore points and delete the datastore. Isolation means nothing else is touched.
Clean exit, no residue, no risk to others.
You just won a client with 80 machines
Provision a tenant, set the quota, connect their hypervisor. Branding and access rules are inherited from your template.
Onboarded in an afternoon.
Comparison
Against how you do it today
- Consoles
- Today: One per client
- Securive: One for the whole book
- Isolation
- Today: Shared repository, logical separation
- Securive: Separate datastore, key and hard quota
- Branding
- Today: Your vendor's
- Securive: Yours, on your domain
- Billing
- Today: Estimated
- Securive: Per-tenant actual consumption
- Client access
- Today: All or nothing
- Securive: Restore-only, scoped to their machines
Questions
The things people ask before they switch
Each tenant has its own datastore, its own encryption key and a quota enforced at the storage layer rather than in application logic. One tenant cannot read, fill or delete another's data.
Yes. Set your logo, colour and a custom domain; a certificate is issued for it automatically. Your clients see your brand from the login screen onward.
Per-tenant consumption is available in the console and over the API, so you can bill actual usage through your existing PSA or accounting system with whatever margin you set.
Yes — a restore-only role scoped to specific machines. They can recover their own data without seeing the console or any other tenant.
Create the tenant, set a quota, connect their hypervisor or M365 tenant. Storage, keys and access scoping are provisioned automatically — minutes, not a project.
Find out whether your backups actually restore.
Connect one hypervisor, set one policy, and let a scheduled drill try to bring it back. If it doesn't, you'll know in a day rather than during an incident.
No credit card · 14-day trial · Migration assistance included