Hand out revocable proxy links, not credentials

Register the http and https proxies you already pay for, group them into failover pools, and give each person a link with an expiry, a traffic cap and a kill switch. They never see the upstream address or password.

What it does

One gateway in front of proxies you already pay for.

Revocable relay links

Issue a link with an expiry, a traffic ceiling and a kill switch.

  • No upstream host or password shared
  • Revoke one link, rotate nothing
  • Per-recipient, not one shared secret

Failover pools

Group upstreams so one dead member does not take the link down.

  • Automatic failover
  • Add or drop members live
  • Health-aware selection

Proxy acceleration

Cut latency on the relay path.

  • Connection reuse
  • Race pool members for the fastest
  • Nearest-edge forwarding

Proxy orchestration

Pick how a pool routes, per link.

  • Round-robin / weighted
  • Geo-nearest
  • Sticky sessions and health scoring

Block-resistant relay

Keep our relay reachable when networks fingerprint and drop plain proxies.

  • Resists DPI fingerprinting
  • Camouflaged relay traffic
  • Stays up when plain proxies are dropped

Usage and visibility

See what each link consumes.

  • Per-link traffic counters
  • Period caps
  • Last-used timestamps

How it works

1

Register your proxies

Add the http and https proxies you already pay for. We do not sell IPs.

2

Pool and issue a link

Group them into a failover pool and issue a per-recipient link with an expiry and a cap.

3

They use the relay

The recipient gets relay://<linkId>:<secret>@<relay host> and nothing else.

What it does not do

Being straight about this is cheaper than having you find out later.

Want in?

We are onboarding manually right now. Leave your email and we will reach out.