Deployment Modes
P4SaMD is available in three deployment modes. Each mode is designed for a different organizational profile — from teams that want to be up and running in minutes to enterprises that require full infrastructure ownership.
- Multi-tenant SaaS — the fastest way to start. Your organization shares the P4SaMD cloud infrastructure with other tenants, with strict data isolation enforced at every layer. Features and quotas depend on the subscription plan you choose.
- Dedicated SaaS — P4SaMD runs in a cloud environment provisioned exclusively for your organization. You get all the convenience of a managed service with the isolation, customization, and SLA guarantees of a private deployment. Available from the Professional plan upward.
- On-premise — P4SaMD runs entirely within your own infrastructure, on a Kubernetes cluster you control. Full data residency, maximum customization, and no dependency on external networks. Supplied as the Enterprise plan feature set.
Deployment Comparison
The table below summarizes the key characteristics of each mode. Where multi-tenant SaaS features vary by plan, the value shown reflects the most restrictive tier; see SaaS Plans for the full plan matrix.
| Multi-tenant SaaS | Dedicated SaaS | On-premise | |
|---|---|---|---|
| Infrastructure | |||
| Managed by | Mia-Care | Mia-Care | Your team |
| Infrastructure | Shared cloud | Dedicated cloud | Your servers |
| Database isolation | Row-level (shared DB) | Dedicated database | Your database |
| Custom domain | Plan | ✓ | ✓ |
| Data residency region | EU or US zones | Configurable | Full control |
| Operations | |||
| Platform updates | Automatic | Scheduled window | Manual / self-managed |
| Uptime SLA | 99.5 % | 99.9 % | Self-managed |
| Backups | Mia-Care managed | Mia-Care managed | Your responsibility |
| Monitoring | Mia-Care managed | Mia-Care managed | Bring your own stack |
| Features | |||
| All core SDLC features | ✓ | ✓ | ✓ |
| AI-powered features | Plan | ✓ | ✓ |
| Brownfield import | Plan | ✓ | ✓ |
| Single Sign-On (SSO / SAML) | Plan | ✓ | ✓ |
| API access | Plan | ✓ | ✓ |
| Custom integrations | Plan | ✓ | ✓ |
| Audit log retention | 90 days | 1 year | Unlimited |
| Support | |||
| Support channel | Email / ticketing | Dedicated account manager | Dedicated account manager |
| Onboarding assistance | ✗ | ✓ | ✓ |
| Custom SLA | ✗ | ✓ | ✓ |
Choosing a Mode
Multi-tenant SaaS is the right choice if you want to start immediately without any infrastructure work, and your team is comfortable with a shared-cloud model. It scales well for small-to-medium teams and covers all core compliance workflows even on the entry plan.
Dedicated SaaS suits organizations that need full data isolation, a custom domain, or specific data-residency commitments, but do not want to manage their own infrastructure. It is also the recommended path for organizations subject to procurement or vendor-assessment requirements that preclude shared infrastructure.
On-premise is designed for organizations with strict network air-gap requirements, existing Kubernetes infrastructure, or policies that mandate full ownership of all infrastructure and data. It carries the highest operational responsibility — your team is responsible for installation, upgrades, backups, and monitoring.
Where to go next