SysManage Enterprise SaaS
The multi-tenant, hosted edition — manage many fleets from one platform, with each tenant's data in its own physically isolated database.
Run a fleet-management business, not just a fleet.
Enterprise SaaS takes everything in SysManage Enterprise and delivers it multi-tenant and hosted — so a managed-service provider, a platform team, or a multi-division enterprise can manage dozens or hundreds of separate fleets from a single deployment, while guaranteeing that no tenant can ever see another's data. The isolation isn't a policy you trust; it's a database boundary you can point at.
Four ways to run SysManage
SysManage meets you wherever you are — from a free open-source server to a fully multi-tenant SaaS platform. Enterprise SaaS is the newest tier, sitting alongside the established on-premises offerings.
Community Edition
The full open-source platform. Single server, single database, self-hosted.
Professional
AI health analysis, container management, and advanced monitoring for growing teams. On-premises.
Enterprise
The full Professional+ feature set — compliance, vulnerability scanning, federation, secrets, automation. On-premises.
Enterprise SaaS
Everything in Enterprise, delivered multi-tenant and hosted, with a dedicated isolated database per tenant.
Community, Professional, and Enterprise are single-tenant deployments. Enterprise SaaS is the multi-tenant edition — see the architecture for how the two topologies differ.
Why Enterprise SaaS
🔒 Isolation you can prove
Every tenant lives in its own PostgreSQL database. There is no shared table, no tenant_id column to forget, and no connection from one tenant to another. When a customer asks “can anyone else see our data?”, the answer is a boundary you can point at, not a policy you ask them to trust. See the security treatment.
🗝️ Credentials that expire themselves
Each tenant's database credentials are leased on demand from OpenBAO — short-lived, auto-expiring, and scoped to one tenant. There is no shared master password to leak, and a captured credential is narrow and brief by construction.
🌍 Data residency, per tenant
Because a tenant is a single self-contained database, you can place it where it must live — a specific region or jurisdiction — and back it up, export it, or delete it completely without ever touching another tenant. Right-to-be-forgotten becomes a per-database operation.
⚡ Self-service onboarding
Provision a new tenant from the control-plane UI in minutes. A least-privilege provisioner creates the tenant's database and registers it — no manual cluster surgery, and the server never holds superuser rights.
🛰️ One pane, many fleets
Administer every tenant from a single control plane. Operators switch tenant context to work inside a fleet; server-wide jobs fan out across all tenants. Identity is shared; data never is.
🧩 The whole Enterprise toolkit
Enterprise SaaS includes the full Professional+ engine set — compliance, vulnerability scanning, reporting, automation, secrets, and more — running per tenant. Nothing is given up for the multi-tenant model.
Who it is for
- Managed service providers (MSPs) managing the fleets of many separate customers, who need airtight isolation and per-customer billing, backup, and offboarding.
- Platform and SaaS companies offering infrastructure management to their own users as a hosted product.
- Large enterprises and holding companies with independent divisions, subsidiaries, or jurisdictions that must not share a data store.
- Regulated organizations that need per-tenant data residency, independent backups, and clean, provable deletion.
Editions at a glance
| Capability | Community | Professional | Enterprise | Enterprise SaaS |
|---|---|---|---|---|
| Core fleet management (open source) | ✓ | ✓ | ✓ | ✓ |
| AI health analysis & advanced monitoring | — | ✓ | ✓ | ✓ |
| Compliance, vulnerability scanning, federation, secrets, automation | — | — | ✓ | ✓ |
| Multi-tenant — many isolated fleets | — | — | — | ✓ |
| Dedicated database per tenant | — | — | — | ✓ |
| OpenBAO-brokered per-tenant credentials | — | — | — | ✓ |
| Per-tenant data residency, backup & deletion | — | — | — | ✓ |
| Self-service tenant provisioning | — | — | — | ✓ |
| Deployment model | Self-hosted | On-prem | On-prem | Hosted / multi-tenant |
The open-source schema and partitioning are the same across editions; the multi-tenant routing engine (MULTITENANT_SAAS) is what the Enterprise SaaS license unlocks.
Ready to run many fleets, securely?
Enterprise SaaS is licensed per deployment. Talk to us about provisioning, data-residency options, and migrating from an on-premises Enterprise install.
Contact Sales →Learn more
🏗️ Architecture
Control plane, per-tenant silos, partitioning, and the routing seam.
Multi-tenancy architecture →🔐 Security
The defense-in-depth isolation model and why it is hard to attack.
Multi-tenant security →⚙️ Deployment
Stand up a multi-tenant deployment and provision your first tenants.
Deploy multi-tenancy →