VirtEngine provides
The market and settlement layer around the software.
- counterparty identity and verification
- catalogue representation and ordering
- the lease or entitlement agreement
- escrow and settlement
- usage records where the plan is metered
Marketplace · SaaS
Software as a Service on VirtEngine
Software plans can use the same catalogue and settlement rail as infrastructure.
Compare IaaS, PaaS and SaaS Custom listings
Protocol in development Example listings are illustrative
Catalogue plan ↓ Order ↓ Entitlement
Seat per user
Licence per term
Support per tier
Catalogue
Software plans in the same catalogue
Three illustrative listings. No production software vendors are implied. A SaaS listing sells access to software; it does not imply that VirtEngine deploys the application.
SaaS
Illustrative exampleAnalytics Workspace
Example Provider
Region-independent
- 10 seats
- Monthly plan
- Standard support
$50 / seat / month
SaaS
Illustrative exampleDeveloper Tool Seats
Example Provider
Region-independent
- Per-developer licence
- CI minutes included
$24 / seat / month
SaaS
Illustrative exampleMonitoring Subscription
Example Provider
Region-independent
- Host monitoring
- Alert routing
- 30-day retention
$6 / host / month
More examples
- Enterprise Support — named contact and response targets
- Secure Collaboration — encrypted seats and audit log
Boundary
What VirtEngine does — and does not do
The software provider provides
The application itself.
- the hosted software and its operation
- accounts, seats, licences and entitlements
- plan features, limits and support
- fulfilment through Waldur or a custom integration
- the actual service relationship behind the plan
Fulfilment is an entitlement change, not a machine. Waldur integration explains plan, order-field and lifecycle handling; custom fulfilment patterns cover provider-defined plans; and IaaS vs PaaS vs SaaS draws the comparison in full.
Continue