Skip to content

Customer dashboard overview

ProxyRequest includes a complete customer dashboard as well as the managed proxy backend. It is not a disconnected template: the frontend uses the same users, packages, orders, invoices, usage records, proxy credentials, API keys, and webhooks as the backend.

ProxyRequest customer sign-in with annotated brand identity and login formOpen full size

The supplied frontend includes the public account entry point, not only authenticated administration screens.

  1. Brand identity covers the customer-facing name, icon, color system, and related links.
  2. The sign-in flow connects customers to their live ProxyRequest account and entitlements.

Customer account

Sign-in, registration support, profile, password, 2FA, language, theme, and notification controls.

Proxy product

Package catalog, purchases, proxy generation, credentials, source-IP allowlists, blocked domains, and usage analytics.

Commercial records

Balance, funding entry points, invoices, coupons, and the entitlement state produced by completed purchases.

Reseller workspace

Managed customer accounts, package allocations, usage, and credential delivery for reseller operators.

SubscriptionDashboard delivery
MonthlyDashboard plus base brand styling connected to your backend deployment
Six months prepaidDashboard plus base brand styling; separately quoted customization is available
Annual prepaidDashboard plus base brand styling; separately quoted customization is available
Custom design or behaviorAvailable only with a six- or twelve-month term and always scoped and quoted separately

Base brand styling covers your product name, logo or icon, primary colors, customer-facing domain, and standard contact, status, and documentation links. Business-specific copy, new designs, layouts, pages, workflows, and integrations are customization work: they are available only with a six- or twelve-month term and are quoted separately. See branding and customization for the exact boundary.

ProxyRequest customer dashboard with annotated package usage analyticsOpen full size

Customer analytics reads the same package and accounting state used by the proxy backend.

  1. Usage analytics lets the customer scope traffic by package and date without operator access.
  • Customers buy or receive packages, generate credentials, monitor usage, manage their account, and review invoices.
  • Resellers perform the same work for managed customer accounts and allocations.
  • Your operators configure supply, routing, packages, accounting, and infrastructure in the separate admin interface.
  • Your services can use the API and signed webhooks when an existing billing, CRM, or support system remains authoritative.

Continue with customer workflows, reseller workflows, or the launch checklist.