SaaS Control Plane
Tenant lifecycle, plans, mock billing, limits, support access and readiness evidence for selling HostelCore as a multi-company SaaS.
service-level lifecycle gate
349 EUR monthly mock billing
current limits enforced by backend
no real Stripe or card processing
| area | status | evidence |
|---|---|---|
| Lifecycle | past_due | payment failure moves tenant to past_due |
| Onboarding | in progress | 5/7 controls completed |
| Plan limits | allowed | 6 enforced limits |
| API scope denial | denied | api_scope_denied |
SaaS Readiness Controls
Service-level tenant isolation
All SaaS actions are checked by tenant-aware domain services.
Plan entitlements
Properties, users, beds, reservations, API keys and webhooks are enforced before mutation.
Mock billing only
Invoices and payment events are deterministic metadata; no cards or Stripe credentials exist.
Support access
Grants expire, cannot be reused and create critical audit events.
Worker dry-run
0 mutations when previewing SaaS jobs.
Future adapters
Stripe, domains and email are explicit integration boundaries, not active claims.