How it works

Think of the gateway as a reception desk and your slot as a seat reserved for your own Claude account. Your computer sends the question; the desk chooses one of your selected seats; Anthropic runs the model.

Model requests go over HTTPS. Your files, tools and history stay local; model context can contain their contents.

One question, step by step

ccfleet local runs original Claude Code on your computer. Local tools may read a file and include relevant text in the model request. The request goes over HTTPS to our gateway with a separate Fleet connection key.

The gateway checks your key and ownership, then chooses one of your selected own slots. The gateway uses a restricted inference-only SSH connection to that slot. The slot uses its bound native Claude credential over HTTPS to Anthropic. The answer streams back along this route; permitted tools execute on your computer. Credentials are not copied to your laptop or the gateway.

Your seat and your account

Each customer receives a dedicated VPS and dedicated exit IP. The slot has a private Linux home directory and one bound Claude account. You sign in yourself through Anthropic; native Claude owns authentication and renewal. Renewal can fail or be revoked, so the page may ask you to Sign in again.

Your slot card distinguishes reported ready, renewal pending, sign-in required and account maintenance. Stale observations do not claim readiness. A heartbeat does not prove provider acceptance. Read-only diagnostics check connections without a model request or project scan. Machines keep their clocks on UTC; slot cards display reset times in your own time zone.

Choose the accounts your model connection may use

Think of a connection as a saved delivery address plus a key, and a slot as one signed-in account environment. The website manages these choices; the CLI is an alternative way to save them. You do not need to configure both.

Only one account

Select A only

Every request uses A. Owning B does not add it automatically; if A is unavailable, this connection reports the error.

Priority

A first, B second

Each request prefers the highest-priority eligible slot. A safe failure can use B. After A recovers and its brief cooldown ends, a later request may use A again.

Sticky

A first, B second; keep each conversation on one account

Once a normal response starts on B, later requests in that conversation prefer B while the assignment is remembered and B remains eligible. A new conversation starts from your priority order.

On the website: open Your slots → Connect Claude. Give A priority 1 and B priority 2; leave any excluded slot blank. Priorities must be unique. Choose your routing mode, then save. Only your own held slots are selectable, and each needs a usable Claude sign-in before it can receive requests.

In the CLI: after pairing, choose one of these examples. Replace A and B with your actual slot names. --replace is an explicit replacement of an existing saved connection; it creates a new key.

ccfleet gateway setup --slots A --replace
ccfleet gateway setup --slots A B --routing priority --replace
ccfleet gateway setup --slots A B --routing sticky --replace

For one launch, ccfleet local --slot A pins a slot already selected for that connection and disables backup switching for that launch. It cannot add an unselected slot or someone else's account.

Safe switching has limits. A known failure before sending, or a supported explicit upstream rejection marked safe to retry, can try the next selected slot. If sending has begun and the result is uncertain, the gateway stops instead of guessing. Once public response headers are sent, a broken stream ends without switching or replay, even before any text appears. An invalid connection key or malformed request needs correction, not another account.

Sticky selection needs a usable conversation identifier. Native Claude Code supplies supported identifiers; compatible clients can send X-CCFleet-Session. Without one, priority order applies. The gateway remembers an assignment in bounded runtime memory for up to 24 hours after a normal response starts; restarts, configuration changes or eviction can reset it. Switching does not move files, merge credentials or combine plan limits. Your conversation history stays local.

Understand the address

Base URL: https://ccfleet.io
POST https://ccfleet.io/v1/messages

The Base URL is the service address saved by your client; saving it does not create a local server or store messages there. /v1/messages is the Messages API-compatible path on our service. The path name does not mean this hostname is owned by Anthropic. Our gateway receives the HTTPS request, selects your slot, and that slot connects to Anthropic. The connection key authenticates you to CC Fleet; it is not a Claude credential or an Anthropic paid API key.

Privacy: your laptop encrypts the connection to the gateway, but the gateway decrypts it to route the request and can read model messages and replies. The slot keeps its native Claude credential. Local tools may include file contents in model context; keeping files local does not mean that no file content can leave the computer.

Machine administrators have root access and can inspect your slot. They may also alter relayed replies, which can influence local tool actions. Choose local permissions accordingly and keep only data you trust them to handle.

For diagrams and the comparison with CC Host, read the comparison guide. The recorded verification on October 11, 2026 used one actual live account; multi-slot routing and faults used controlled peers, not two live accounts. See verification scope for the evidence.

Who can read what

The gateway can read model requests and responses. HTTPS protects each connection, but the gateway decrypts messages to route them. The gateway, the selected slot and Anthropic process model context, including any prompts, file contents and tool results it contains. Local files stay local as files; relevant contents can still be sent to the model.

The Fleet server receives slot sign-in state, the bound Claude email and plan, quota observations, hourly token counts and paired-device facts. Those heartbeat reports do not contain prompts, conversations, file contents or the Claude credential. Separately, the direct HTTPS gateway receives and processes model requests. The server stores only a hash of your connection key; the native Claude credential remains on the slot.

The relay removes selected headers and top-level structured metadata. It does not redact arbitrary prompts or tool results. Native system prompts may include local OS, working directory or environment details. This is not anonymity or a zero-metadata guarantee. MCP servers, hooks, plugins, tools and updates may connect directly from the laptop.

Machine administrators have root and can technically inspect any slot. The operator console does not display native credentials or full file contents, but that does not remove root access. Read Privacy for the full data scope and retention.

Updates, outages and returning a slot

Local Claude updates separately from the slot and the Fleet client. Automatic updates are disabled during a CC Fleet launch; update your local Claude installation separately, outside that session. Machine security updates install daily; necessary reboots are scheduled by the operator. Check Status for website and machine availability, and the fleet performance panel for combined relay measurements. It shows average upstream timing and transfer completion when enough users contribute data, without listing individual accounts.

The gateway machine resources panel shows the Fleet gateway VPS and Fleet service resource use. A busy CPU, low available memory or a nearly full data filesystem can indicate pressure. These readings alone do not prove where a slow request spends its time.

The slot-machine details list each monitored machine as Operational, Degraded or Down, with the machine-level reason and last report. Stable labels such as Machine 1 protect holder names; your slot card links to the matching label. A completed slot release clears your chosen name and returns the machine under its reserved pool-N name.

Model requests need the configured gateway and an eligible slot. A gateway outage reports an error. Giving a slot back stops its processes and deletes the Linux account and all slot files. It is offered again only after the machine confirms deletion; local files and history are not deleted.

Slot providers, IP types and rates

The homepage’s Slots & pricing section shows up to three real configuration examples. Open the full public slot catalogue for machine providers, network types, current availability and Alpha price breakdowns. Search host/IP-provider brands or a public label such as Machine 7, filter by provider and IP type, and browse pages of up to 20 machines. The purple Residential, blue ISP and gray Datacenter badges name network types; their text and color do not rank quality or guarantee Claude compatibility. Browsing does not reserve a slot. Sign in and use Browse available slots to choose and claim a machine within your allowance.

Alpha pricing. Each machine has its own monthly USD rate in the public slot catalogue. Alpha pricing passes through recorded VPS and exit-IP costs, plus a monthly service fee of 10% of resource cost, with a $2 minimum per slot. Your Claude subscription or Anthropic API usage is billed separately.

Recorded costs are normalized to a calendar month. A 30-day cost is multiplied by 365/360; an annual cost is divided by 12. For a customer quote, round the normalized USD resource cost to cents, half up; calculate 10% of that amount, round the service fee half up to cents with a $2 minimum, then add the two displayed amounts. Resource costs of $8.68, $10.83, $22.28 and $27.44 therefore give totals of $10.68, $12.83, $24.51 and $30.18 per month. The fee remains $2 through $20 of resource cost.

The public breakdown shows VPS cost, separately recorded exit-IP cost, service fee and total. When hosting includes the exit IP, it shows the recorded bundled resource cost without inventing a split. A normalization rounding line explains any cent-level difference between individually rounded components and the rounded combined resource cost. Missing costs or costs not converted to USD make pricing unavailable. The host and IP-provider brands remain visible. ISP, Residential and Datacenter describe network types, with the same pricing formula and no separate residential premium; none guarantees quality, speed or Claude compatibility.

Alpha — Early Access. The service is still being tested and has not launched commercially. The operator has personally used one residential slot with encouraging results; reliability across providers, configurations and multiple users is still being evaluated. Alpha pricing is introductory and may change for future billing periods. You will receive an updated quote before renewal if pricing changes; an already agreed billing period retains its agreed price.

Agree the price and paid period with the operator; the website does not charge automatically, renew automatically or rewrite past payments.

Retired machines are removed from the rental catalogue. A temporarily offline machine that remains in service still appears on Status. Retirement does not release an existing holder or delete their account and payment history.

An ISP slot can use a separate approved exit proxy; provider HTTPS remains encrypted through that tunnel. Your account page shows the same labels before you choose a slot.

Documentation — the gateway explained simply, account choices and platform comparison.