Ready for a days-scale launch
Inputs are final, standard workflows fit, backend resources are ready, and external approvals are complete.
Dashboard launch
The standard frontend can launch in a matter of days after setup when the required inputs, backend resources, and external approvals are ready. This is a typical delivery path, not a fixed guarantee: custom development, changing requirements, DNS, email, payment-provider, or legal review can extend the schedule.
Inputs to prepare
Section titled “Inputs to prepare”| Area | Required decision or asset |
|---|---|
| Subscription | Dashboard and base brand styling on every term; separately quoted customization only with six-/twelve-month prepayment |
| Brand | Final product name, vector logo, square icon, exact colors, and approved interface copy |
| Domains | Customer, API, proxy, status, and documentation hosts plus DNS ownership and TLS plan |
| Contact and legal | Support email/link, status page, documentation, terms, privacy, company, and sender identity |
| Catalog | Package names, stable aliases, descriptions, features, prices, units, cycles, limits, visibility, and coupons |
| Commerce | Currency, balance rules, payment provider, invoice behavior, tax/legal ownership, and server-side payment confirmation |
| Proxy delivery | Advertised hosts/ports, protocols, targeting, session behavior, credential format, and tested upstream routes |
| Access and automation | Registration policy, reseller roles, 2FA expectations, API key restrictions, webhooks, and supported integrations |
Never place production secrets in a branding or launch spreadsheet. Exchange payment, provider, API, email, and webhook credentials through the agreed secret channel.
Delivery sequence
Section titled “Delivery sequence”- Confirm the delivery boundary: included dashboard and base brand styling, plus any separately quoted custom work available on a six- or twelve-month term.
- Configure the backend resources, domains, brand values, links, catalog, account policy, and supported integrations.
- Publish a review environment with synthetic or private test records.
- Run customer sign-in, purchase, payment confirmation, entitlement, credential generation, proxy request, usage, and invoice tests.
- Run reseller creation, allocation, credential rotation, and root-versus-child accounting tests when reseller access is enabled.
- Verify security, responsive layouts, language/theme options, email, status, documentation, legal links, analytics, and support ownership.
- Record acceptance and rollback owners, then move a private package or friendly customer through production before broad launch.
Acceptance checklist
Section titled “Acceptance checklist”Identity and navigation
Section titled “Identity and navigation”- Verify that the name, logo/icon, colors, copy, browser title, and links match the accepted scope.
- Verify that customer, API, proxy, status, and documentation domains resolve correctly with valid TLS.
- Verify login, registration policy, password recovery, 2FA, language, theme, and mobile layouts.
Product and money
Section titled “Product and money”- Confirm every visible package has an eligible live route for each advertised protocol and target.
- Confirm prices, units, periods, coupons, balance rules, invoice states, and payment-provider ownership.
- Confirm paid service is activated from backend state, not only a checkout redirect.
Proxy and accounting
Section titled “Proxy and accounting”- Test generated HTTP/SOCKS credentials through the advertised gateway hosts and ports.
- Test usage, requests, remaining allowance, customer limits, root ledgers, and reseller child allocations.
- Test password rotation, source-IP restrictions, blocked domains, depletion, and expired access.
Operations and recovery
Section titled “Operations and recovery”- Confirm API keys and webhook secrets are stored and restricted; test signature, retry, duplicate, and reconciliation paths.
- Assign customer-visible errors and invoice questions to support; assign provider, route, gateway, and capacity incidents to operators.
- Assign named owners to DNS, configuration, catalog, and custom-code rollback steps.
Plan additional time
The scope includes a unique design, new pages or workflows, new integrations, data migration, or third-party review.
Return to the dashboard overview or review the broader infrastructure and launch guide for gateway capacity and operational checks.