Cloud/VPS commerce with operational honesty

A real storefront UX for serious VPS resale operations.

VPSGods now presents a materially improved customer-facing shell: pricing/catalog polish, account surfaces, provisioning-state design, billing-history layouts, and explicit disclosure about what is runtime-wired today versus what still needs deployment integration.

Explore catalog UX Read deployment truth

4Dedicated customer UX surface groups: catalog, account, provisioning, billing

3Runtime services the Ubuntu automation now wires together: web, API, and worker

24.04Ubuntu target with hardening automation, smoke checks, and backup wiring

Shared design system in active use

Storefront polish without fake runtime promises.

Cards, tables, forms, badges, navigation, and empty states are now consistent across public and admin experiences, while deployment copy stays explicit about the public web app being deployed and the admin app still remaining outside the automated runtime path.

Catalog pricing emphasis and comparison-ready layout
Account and billing surfaces designed for real authenticated workflows
No hardcoded localhost links or fake “live” customer data

Runtime link disclosure

Runtime links are configured as same-origin routes. Use this only when your reverse proxy really serves the API on the same origin as the deployed Next.js web surface.

Deployment topology disclosure

On the Ubuntu 24.04 deployment path, nginx now serves this public web app at the site root while forwarding API routes like /api, /docs, and /healthz to the backend service. The admin shell still requires separate deployment work.

Catalog + pricing UX

Provider catalog presentation that feels commercial and trustworthy

Launch

$6/month equivalent

A storefront-ready entry point for single-team reseller operations that still need real billing and payment integrity discipline.

Provider-normalized catalog and pricing presentation
Top-up driven billing foundations with invoice artifacts
Customer/account shells that stay honest when runtime auth is not wired

Scale

$18/month platform fee

For operators who need provider governance, install/update runbooks, and serious admin visibility without pretending the hard parts are solved by magic.

Webhook integrity reporting plus safe repair workflows
Explicit reset/reinstall safety controls with dry-run output
Shared UX system across storefront and internal operations console

Enterprise

Customengagement

For staged rollout, risk review, and tailored deployment plans where production truth matters more than glossy claims.

Controlled provider onboarding and environment separation
Operational hardening guidance and smoke tests
Documented backup/restore expectations and rollback guidance

Catalog presentation

Offer cards, comparison rhythm, and pricing emphasis now feel like a real infrastructure storefront instead of an empty placeholder page.

Account surfaces

Sign-in, profile, and organization controls use production-grade spacing, hierarchy, and disclosure without pretending session wiring exists where it does not.

Provisioning visibility

Order state surfaces distinguish submitted, provider-accepted, provisioning, active, and operator-review states so retries and delays remain understandable.

Billing history shells

Payment and invoice views now have table, badge, and empty-state primitives that are ready for real data instead of sample transactions.

Auth + account surface

Account access that looks ready for production and says when it is not wired

Password

Organization profile

Company name, primary owner, support contacts, and billing references belong here once auth/session wiring is connected.

Security disclosure

This Next.js shell does not claim live session auth today. Runtime auth still lives in the API and should be integrated deliberately rather than implied.

Review auth-capable API surface See billing layout

Order + provisioning status

States that explain what operators and customers should infer

Status	Meaning
Submitted	Order request accepted, idempotency recorded, waiting for provider workflow.
Provisioning	Worker is actively reconciling provider-side creation and internal state transitions.
Active	Provisioning succeeded and runtime metadata can be surfaced back to the customer account.
Operator review	A payment, provider, or inventory inconsistency needs human attention before the order can progress safely.

No fake sample orders

When this surface is deployed with real customer auth, live order rows can fill this structure. Until then, the layout stays honest and empty.

Billing + payment history

Table scaffolding ready for real billing artifacts

Surface	Current truth
Wallet / prepaid balance	Supported conceptually by the billing domain; not rendered with live account auth on this Next.js shell yet.
Payment history	UI shell is ready for real entries, but this page intentionally shows an honest empty state until runtime account integration exists.
Invoices / artifacts	Table layout supports invoice references and statuses without fabricating rows.
Webhook settlement posture	Operationally important details remain in the backend/admin flows and are disclosed as such instead of faked here.

Billing-state empty pattern

No fabricated transactions

This storefront intentionally shows structure without sample ledger rows or pretend invoices. The design system now supports real payment history and invoice rendering once account-authenticated runtime data is connected.

Check backend health endpoint

Deployment truth

Product promises grounded in what the repo actually wires today

Implemented truth

The Ubuntu 24.04 install/update automation now deploys the public apps/web runtime alongside the API and worker.

Implemented truth

The internal apps/admin surface is still not deployed by the provided automation in this repository.

Implemented truth

TLS automation is not implemented by the provided scripts yet; operators must handle certificates deliberately.

Implemented truth

Secrets are preserved by default on upgrade and only regenerated or rotated when the operator passes an explicit flag.

Implemented truth

Reset and reinstall scopes now distinguish data reset from full clean-slate wipes so destructive intent is explicit.