Services · ccrelay
A residential broadband egress that belongs to you alone, plus a stable and compliant environment for using Claude: accounts are managed centrally and each one is bound to its own egress, so access stays stable, consistent and predictable.
Core service 01
The egress IP is registered to a broadband ISP rather than a datacentre ASN, and it is handed to one person only — you never share a line with another customer.
You always reach Claude from the same egress — not broadband today, a datacentre tomorrow and another city the day after. The egress IP does not jump around.
One residential egress kept over the long term instead of a new address on every connection, so your access environment stays consistent and predictable.
Each Claude account is bound to its own egress. Accounts and egresses are managed centrally in the back office, with no cross-talk and revocable access.
Suited to subsidiaries, employees and contracted clients who use Claude long term and care about a consistent access environment.
What we supply is a lawful, stable, dedicated network egress. The point is an access environment that is consistent and predictable — an ordinary residential connection, used the ordinary way — rather than any form of countermeasure or workaround.
Core service 02
You use Claude through the dedicated usage environment ccrelay opens for you: the complete claude.ai web experience appears as it is on your own subdomain, with conversations, files and pages all working normally.
Accounts, credentials and egresses are managed centrally in the back office: credentials stored encrypted, access revocable at any time, and nobody has to keep a login lying around.
Each account is bound to its own residential egress and takes its own line, with no cross-talk between users.
Every account uses its own subdomain, so the browser isolates local data by origin and separate accounts cannot reach into each other.
Key operations leave an audit trail, which makes central administration and troubleshooting possible for a team.
The dedicated usage environment only lets you use the full claude.ai experience over your own egress, stably and compliantly. Every conversation and every feature is still served by the upstream claude.ai service. ccrelay is not Claude, and it is not a re-wrapped API.
Pricing / plans
Claude Pro
The entry tier for everyday individual use, delivered ready to run.
Shown at checkout/ 30 days
Stock and delivery times are shown on the online purchase page
Claude Max 5x
The workhorse tier for frequent use, with more headroom.
Shown at checkout/ 30 days
Stock and delivery times are shown on the online purchase page
Claude Max 20x
The top tier for heavy and professional workflows.
Shown at checkout/ 30 days
Stock and delivery times are shown on the online purchase page
Already have an account? Sign in to the console — contracted clients can activate online or renew an existing subscription from the Purchases & orders page.
Have an activation code? Activate it now, and your account and online entry point are ready as soon as you sign up.
Prices move with upstream policy and line costs; the amount shown at online checkout is the one that applies. Out-of-stock tiers can still be ordered ahead: after payment we deliver within the window stated on the purchase page, and you can ask for a full refund at any point while you wait. For team volumes, a separate residential line or other custom needs, talk to us.
One thing to know before you start: the chained residential setup needs an upstream proxy node of your own (see the setup guide); reaching Claude through the web subdomain alone needs no extra configuration.
FAQ
Ordinary proxies mostly run on datacentre IPs and are usually shared by a crowd of users. What we supply is a residential broadband egress registered to an ISP, dedicated to one person and static, which makes the access environment steadier and more consistent.
No. The dedicated usage environment only lets you use the full claude.ai web experience on your own subdomain, over your own egress, stably and compliantly. Every conversation and feature is still served by the upstream claude.ai service. ccrelay is not Claude, and it is not a re-wrapped API.
We advise against it. Each account should be bound to its own egress, one person per seat. Several accounts or several people on one egress, signing in concurrently, is a classic trigger for account controls and falls outside what we can cover — see the usage policy.
The cards on this page show each tier's current price (prices move with upstream policy and line costs, and the amount shown at online checkout is the one that applies). Once you have signed up and opened the console, you can buy directly from the Purchases & orders page; you can also talk to us for a quote and an activation code.
Yes. Out-of-stock tiers can be paid for ahead of delivery: the expected delivery window is shown before you order, and once stock returns orders are activated in the sequence they were placed. You can request a full refund from the order page at any point while you wait — and if we have not reviewed that request inside the review window, it is refunded in full to the original payment method automatically — or you can keep waiting for the restock.
We prepare your dedicated usage environment and your own egress. Follow the setup guide to configure the network egress on your machine and you are set; the dedicated usage environment itself is reached through your subdomain and needs no extra configuration.