Residential access through a gateway
Customers use a backconnect entry point for residential proxy traffic. Session and routing settings determine how requests use the available pool.
Proxyverse
Proxy operations / CommerceOne workspace for proxy supply and sales.
Proxyverse brings provider connections, proxy inventory, customer packages, and sales into one operating platform. We built the network and management services behind a product that sells residential access and assigned proxies, tracks consumption, and supports reseller integrations.
- Availability
- 99.9% uptime SLA
- Operations
- 45% cost reduction
- Capacity
- 10x scalability
Supply and product
Turn available capacity into a service customers can buy.
Provider integration is one part of the work. The service also needs to organise that capacity into products, allocate access after a purchase, and retain enough account context to explain later consumption.
Proxyverse combines multiple provider connections with static proxy inventory and backconnect access. Its management interface brings customer accounts, purchases, usage, and invoices together, while the API exposes these workflows to integrated applications and reseller accounts.
The workflow
Keep the product visible from purchase to usage.
Rotating access and assigned addresses share the commercial workflow, with different resource rules underneath.
Connect and organise supply
Integrate upstream providers and register static inventory. Group capacity by proxy product and the locations available to customers.
Publish packages
Offer residential, datacenter, and ISP products with their relevant traffic allowances or assigned addresses.
Process the order
Connect payment and invoicing to the customer account, then provide the proxy access associated with the purchased product.
Track consumption and renewals
Return traffic records to account and administrative views so the service can manage usage and ongoing customer relationships.
What we built
One product catalogue, several delivery models.
Assigned datacenter and ISP proxies
Static inventory management keeps track of the addresses available to sell and those already allocated. Product screens can show purchases and proxy details together.
Accounts, invoices, and reseller access
The platform manages customer and reseller accounts alongside payments and invoice records. Its API supports proxy-list generation and account operations for external integrations.
In operation
A dashboard for both customers and operators.
Customers need to see their products and traffic. Operators need to inspect account records, usage patterns, and the inventory supporting those products. Proxyverse provides both views over the same service operations.
The interface includes daily usage, user management, referral and affiliate records, product purchase screens, and API documentation. These views show how proxy delivery and the commercial account were connected in the product.
Product in view
Proxyverse in use.
Explore the product website and account interface. Open an image to inspect it at full size.
01 / Product website. Proxyverse website introducing the residential proxy network.
Open full-size image ↗Engineering stack
Technology behind the platform.
Proxyverse connects its proxy management workflows to a Go engine and Go traffic accounting. Django provides the control plane and API, with separate systems for operational records, analytics, caching, and queued work.
Go
- Proxy engine and connection handling.
- Traffic metering and usage accounting.
Python 3 / Django
- Control plane and application API.
ClickHouse
- Analytics storage and queries.
Redis
- Cache.
PostgreSQL
- Control plane data storage.
NATS
- Message queue.