Product, operations, and engineering reference for the managed hosting control plane.
Use this hub to understand what each page should expose, which external system owns each action, and how the dashboard should stay clean as new server workflows are added.
Understand the model
Start with the async infrastructure broker model and the systems that own each part of the stack.
Open02Start hereFollow provisioning
Trace the queue-driven server creation flow from request to health checks.
Open03Start hereReview platform topics
See how VPS, Coolify, and WordPress each map to a distinct dashboard surface.
OpenSections
Available documentation
Each section maps to a real product surface or source-of-truth boundary, so the docs stay useful as the dashboard grows.
Getting started
The fastest reading path for product, design, and engineering context.
Architecture
Next.js, Supabase, BullMQ, Redis, provider APIs, Coolify, Cloudflare, and monitoring.
Dashboard
Layout rules, page roles, and the operational UI direction for the client portal.
VPS management
The VPS list, server detail page, and provider-side responsibility split.
Provisioning
Async jobs, retry-safe steps, external waits, and customer-visible progress states.
Integrations
What Coolify, Hetzner, Netcup, Cloudflare, Uptime Kuma, Supabase, and Resend own.
API boundaries
Rules for keeping provider, application, and local dashboard data separated.
Coolify applications
How application deployments, domains, databases, and backups should stay inside server detail flows.
WordPress lane
How the managed WordPress product differs from generic VPS and app-hosting paths.
Source-of-truth model
VPS creation, lifecycle, region, public IP, specs, traffic, renewal context
Applications, databases, services, deployments, domains, certificates, app backups
Customer relationship, labels, job history, support state, billing context, UI events
Provider servers
Hetzner + Netcup
App resources
Coolify
Health signals
Uptime Kuma
Dashboard rule
The server list should stay a provider-style VPS inventory. Coolify resource detail belongs behind each server where it can be managed with enough context.