Platform quickstart

This quickstart proves the complete operator path from upstream supply to a customer request. It deliberately links to the deeper admin-panel pages instead of duplicating deployment-specific settings.

What you will prove

By the end, one test customer can connect through your gateway with credentials tied to a real package and allowance. You can then find the resulting request and traffic records in the operator analytics surface.

Use test capacity first

Use provider test credentials or strict spend limits, a non-production gateway, and a test customer. Do not use a live customer account for the first end-to-end request.

Before you start

You need administrator access to the ProxyRequest dashboard, one compatible HTTP or SOCKS5 upstream, a gateway server with working DNS and ports, and a machine from which you can send a test request.

Launch a basic proxy product

1. Configure deployment identity. Set the customer-facing domains, branding, currency, operator access, and the commercial mode you will test. Confirm that dashboard, API, and proxy DNS resolve to the intended deployment. See operator access and automation.

2. Register a gateway node. Create the cluster and server record, expose the required HTTP or SOCKS5 port, and wait until the node reports healthy. Follow Register a gateway safely.

3. Add and validate an upstream provider. Import a supported provider or add a compatible endpoint manually. Test its credentials, protocol, and location data before assigning it to customer traffic. Follow Provider configuration.

4. Create the product. Add a pool if you need to combine supply, then create a package with its provider allocation, gateway scope, targeting options, price, expiry, and limits. Complete the package acceptance test.

5. Create a test customer and allowance. Create the user and order, assign the package, and allocate a clearly labelled 10 GB test allowance. Confirm whether the deployment presents decimal GB or binary GiB before converting the value to bytes. See Customers and accounting.

6. Generate customer credentials. Generate access for the test customer and package. Record the assigned proxy host, port, username, and secret without exposing the secret in frontend code or logs.

7. Send the first request. Use the generated credentials with the Proxy Gateway Quickstart. Verify the returned exit IP and any targeting requested by the package.

8. Inspect usage and accounting. Find the request in operator analytics, confirm that traffic is attributed to the expected customer and package, and verify that the ledger balance changes after the normal aggregation delay. Follow the investigation workflow.

Continue from the validated path

• To launch the full customer surface, complete the infrastructure and launch checklist.
• To keep your existing frontend and billing, map the validated resources into a hybrid or headless integration.
• To automate provisioning, create restricted API keys and signed webhooks only after the manual path works end to end.