Keep client work organized
A clear workspace model for separating projects and their server details. The current preview uses demonstration content only.
VPS control, client-ready.
A pilot-stage control dashboard concept for small agencies and developers. This preview does not provision, reboot, rebuild, monitor, or bill servers; those features are not live.
Explore the pilot scopeA clear workspace model for separating projects and their server details. The current preview uses demonstration content only.
The intended model is for each customer to own and pay their cloud provider directly. No VPS compute is sold or billed here.
Provisioning and lifecycle controls are planned, not active. There is no server administration, uptime promise, or managed security service.
Site name, tagline, palette, typography, logo, contact details, products, and platform links are configured centrally so a reseller can rebrand the frontend.
Pilot status · preview only
The $15/month one-instance pilot is a proposed price, not an offer for sale. Provider terms and safe credential handling must be confirmed before account linking, provisioning, or checkout. Cloud compute would be billed separately by the customer’s provider.
No server controls, monitoring, managed hosting, or client invoicing are currently available.
Give each client a place in your workflow without juggling separate provider accounts and invoices. The intended design keeps each client’s infrastructure account and compute bill separate.
Keep project server details together and make routine VPS tasks easier to find. The current preview is not connected to a cloud account and cannot change a server.
Explore a branded client workflow for VPS projects. Client billing tools, provisioning, and team features are planned, not live.
No. This is an MVP preview, and account linking or server provisioning is not live. The intended customer-owned account workflow still requires provider-term confirmation and secure credential handling.
No subscription is available at this stage, and no compute is included. The proposed model keeps upstream compute charges separate and paid directly by each customer.
No. Those controls and usage visibility are not implemented. The current site describes the planned scope without presenting it as available functionality.
The frontend is structured around central brand configuration for the business name, palette, fonts, logo, contact details, and platform links. A production white-label rollout still needs operational, security, provider-term, and customer billing work.
No. The proposed product is a self-service control and billing-workflow layer. It does not administer servers, guarantee provider uptime, or provide managed security.
Use the contact link to review the company contact details. Paid signup and pilot onboarding are not open while the provider and security checks remain incomplete.