Static pools with explicit assignments
Static proxy management covers the addresses available for sale, their pool membership, and their assignment to customers. Residential, datacenter, and ISP products can be managed within the same service.
MimicProxy
Proxy engineering / Backend integrationProxy infrastructure inside an existing product.
MimicProxy connects residential and static proxy services to an existing business backend. We built the proxy engine, pool management, and traffic accounting so the product could manage customer access and network resources through one integration.
- Availability
- 99.9% uptime SLA
- Products
- Residential, datacenter & ISP
- Integration
- Existing backend & management API
The integration
Proxy management inside the existing backend.
The work started at the boundary between the business application and the proxy network. Customer records, purchased packages, and access settings needed to reach the engine carrying requests. Usage records needed to return to the same account.
MimicProxy supports upstream provider integration and direct management of static proxy inventory. That gives the service a way to offer rotating residential access alongside assigned addresses, with each product retaining its own pool and connection rules.
The workflow
From an account setting to a running connection.
The backend describes what a customer can use. The engine applies those settings when a connection arrives and records the traffic that follows.
Connect the inventory
Register provider connections and organise static addresses into pools that the service can assign or sell to customers.
Define the package
Set the available pool, target location, session lifetime, and number of concurrent threads for the customer’s package.
Handle the connection
Authenticate access and apply routing and session settings for the selected product.
Return usage to the account
Record consumption in real time so the business backend can update monitoring and billing views.
What we built
Different proxy products need different controls.
Control identity and concurrency
Geo-targeting, sticky sessions, and TTL settings define how a connection behaves. Thread limits let the service control the number of open connections per package.
An API for the existing backend
Management operations connect to the product’s current backend. HTTP, HTTPS, SOCKS5, and SOCKS4 support gives customer tools several ways to use the configured proxy access.
In operation
Accounting belongs in the operating workflow.
Usage records connect the network to the commercial product. MimicProxy accounts for traffic as it is carried, providing the data needed to inspect consumption and bill the right customer.
The implementation keeps proxy connections and traffic accounting in Go, with management operations exposed through the Django control plane. The engineering stack below shows the responsibilities of each service.
Product in view
MimicProxy in use.
The product website introduces the service and its proxy products. Open the image to inspect it at full size.
01 / Product website. MimicProxy website introducing its residential and datacenter proxy services.
Open full-size image ↗Engineering stack
Technology behind the platform.
MimicProxy uses Go for proxy connections and traffic accounting. The Django control plane handles service management and API operations, backed by dedicated data stores and a message queue.
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.