Deployment Modes
P4SaMD is available in three deployment modes, each aimed at a different organizational profile.
- Multi-tenant SaaS: 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.
- Dedicated SaaS: P4SaMD runs in a cloud environment provisioned exclusively for your organization. Available from the Professional plan upward.
- On-premise: P4SaMD runs entirely within your own infrastructure, on a Kubernetes cluster you control, with full data residency and no dependency on external networks. Supplied as the Enterprise plan feature set.
Deployment Comparison
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 fits teams that want to start immediately without infrastructure work and are comfortable with a shared-cloud model. It scales well for small-to-medium teams, and all core compliance workflows are covered even on the entry plan.
Dedicated SaaS suits organizations that need full data isolation, a custom domain, or specific data-residency commitments without managing their own infrastructure. It is also the recommended path where procurement or vendor-assessment requirements preclude shared infrastructure.
On-premise is 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