Marketplace · PaaS
Platform as a Service on VirtEngine
Order a managed platform instead of assembling every server beneath it.
Responsibility stack
Catalogue
Example managed platforms
Three illustrative listings — example providers, not live availability. What changes between providers is the runtime they operate, not the market rail.
PaaS
Illustrative exampleManaged Kubernetes
Example Provider
Example region
- Control plane managed
- Autoscaling workers
- Managed upgrades
Component-priced plan
PaaS
Illustrative exampleManaged Database
Example Provider
Example region
- Replicated
- Automated backups
- Point-in-time restore
Component-priced plan
PaaS
Illustrative exampleAI Inference Endpoint
Example Provider
Example region
- Managed runtime
- Autoscaling
- Model versioning
Usage-priced
More examples
- ML Workspace — managed notebooks with GPU attach
- Application Runtime — build, TLS, scaling
- Batch Scheduler — queues and job templates
A managed-platform plan adds components and how they are measured, limits that bound consumption, and the lifecycle actions the provider supports. Where the responsibility line sits for each service model is the subject of the IaaS vs PaaS vs SaaS article.
Fulfilment
How a platform is provisioned
- 01 Lease
- 02 Provider daemon
- 03 Waldur plugin
- 04 Managed platform
- 05 Platform endpoint
The chain records the lease. The provider's integration creates the platform; the endpoint is what your team uses.
Go deeper: Waldur integration for order routing and lifecycle callbacks, fulfilment for the full path, and x/market for lease state.
Continue