Consented residential egress

Exit IPs you can explain
to your compliance team

Verifiable nodes. Per-account logging.

Orbit routes your traffic through real phones and home connections whose owners knowingly opted in. Every node carries a recorded enrolment, every destination is logged to your account, and one bad actor gets suspended — not your whole egress.

No card required to evaluate. Cancel any time.

500,000concurrent device capacity
1,000,000concurrent connections
IPv4 + IPv6exit addresses
60sfastest rotation
✓
Consent is verifiable

Every node carries a recorded enrolment. Nodes that can't prove it never get traffic.

✓
Traffic is attributable

Every destination is recorded per account, so an abuse report resolves to one customer.

✓
Kill switch is instant

Suspend an account and its keys die on the very next request. No cache to wait out.

How traffic moves

Four steps from an HTTP request to a metered, logged, mobile-IP exit.

1

You authenticate

Point curl, your crawler or your test suite at the gateway with HTTP CONNECT or SOCKS5 and a single key.

2

We select a node

The request is matched to a consented device by region, latency and load. Pin a session up to ten minutes when you need a stable source address.

3

The device opens the socket

Your target is dialled from a real phone on real mobile data. The bytes ride back through one multiplexed tunnel — no VPN protocol to fingerprint.

4

You're metered and recorded

Bytes, connections and destinations land on your dashboard in near real time, against your plan allowance.

What you get

Every plan includes all of it. You are not buying a lesser network at a lower price.

HTTP CONNECT and SOCKS5

Both first-class. Use socks5h so resolution happens at the gateway and DNS never leaks locally.

City and region pinning

Request a specific geography rather than whatever the selector hands you. Useful when a test suite asserts on locale.

Sticky sessions

Hold one exit address for one to ten minutes, keeping a multi-step flow — cart, checkout, confirmation — on a single IP.

Full UDP support

NAT traversal is handled at the edge, so UDP works through consumer routers instead of dying on a symmetric NAT.

Dual-stack exits

Both address families are first-class. IPv6 exits are scarce, cheap, and rarely blocked.

Concurrency, not just bandwidth

Plans are bounded on simultaneous connections as well as monthly transfer, so a runaway job fails predictably instead of blowing the budget.

A real API

JSON endpoints for usage, live connections, account state and key rotation.

Exportable audit log

Hand a regulator or a victim's legal team a complete record of what an account reached and when.

Application scenarios

What people actually build on this.

Ad verification

Confirm creatives render and target correctly in the geo and on the carrier they were bought for, not from a datacenter range.

Price and inventory monitoring

Read live prices and stock across regions without every request looking like it came from one warehouse.

Localisation testing

Exercise checkout, payments and content routing from real mobile networks in the countries you ship to.

Security research, authorised

Test how your own systems behave when requests originate from consumer IP space. Bring a signed authorisation scope.

Brand protection

Find counterfeit listings and phishing pages across marketplaces without tripping the same bot defences you are trying to bypass.

Data quality audits

Sample how your own product looks to users on real connections, including ones you have never had a lab setup for.

The boring part, done properly

Anyone can sell you an exit address. The difference between a supplier you can grow with and one you can't is what happens when someone files a complaint.

Suspend first

Any account named in a credible abuse report stops taking traffic immediately. You do not wait for the investigation to conclude.

Report back

Complainants get a resolution notice including the outcome, unless they ask us not to contact them.

Named node owners

Every exit belongs to a person who enrolled it, can see when it is in use, is paid for the traffic, and can withdraw it at any moment.

No covert hardware

We do not run agents on devices we have not been explicitly authorised to use. No pre-installed agents in other vendors' software.

Pricing

Full API access, audit logging and the abuse desk on every plan.

Starter

$29.00/mo
25 GB included transfer
  • 25 GB monthly transfer
  • 25 concurrent connections
  • Residential + mobile exits
  • HTTP CONNECT and SOCKS5
  • Email abuse desk
Start with Starter

Business

$299.00/mo
600 GB included transfer
  • 600 GB monthly transfer
  • 1,000 concurrent connections
  • Dedicated account manager
  • Signed gateway configuration
  • Audit log export
  • 99.9% uptime SLA
Start with Business

Prices exclude bandwidth overage, which bills at your plan's rate. Node owners are paid per gigabyte carried.

Questions worth asking us

Whose devices are these, and do they know?

Real phones and home connections, enrolled by their owners through a visible client that shows a persistent indicator while participating. We do not install anything covertly, and we do not take hardware we haven't been explicitly authorised to use.

What happens when someone reports abuse?

Any account named in a credible report is suspended immediately, before we finish investigating. We then look at the destination log for that account, resolve the report, and tell the complainant the outcome. Typically under one business day.

How do you tell my traffic apart from someone else's?

Every destination, byte and connection count is recorded against your account specifically. That record is also what lets us resolve an abuse complaint to one customer instead of disabling everyone.

Can I stop an account instantly?

Yes. Suspension takes effect on the account's next request. There is no cache TTL to wait out and no propagation delay.

Is there a contract?

No. Monthly plans, cancel whenever. If we ever lose the ability to explain where your traffic came from, that is our problem to fix, not yours to be locked into.

What protocols do you support?

HTTP CONNECT and SOCKS5 on the standard gateway port, plus full UDP. IPv4 and IPv6 exits. Anything that speaks either protocol works unmodified.

Try it against one target

Create an account, grab a key, and check what the exit address looks like from five different regions before you commit to anything.