Private services, reachable from cloud agents

Capy machines join your tailnet as tagged, ephemeral nodes, so agents reach the internal databases and APIs your tailnet policy grants them. Your private services stay off the public internet.

Autumn
Supermemory
Exa
Warp
Pocket
Melius
Infisical
Krea
Goblins
RunPod
Town
Firecrawl
Aside AI
Taste Labs
Revyl
Finta
Autumn
Supermemory
Exa
Warp
Pocket
Melius
Infisical
Krea
Goblins
RunPod
Town
Firecrawl
Aside AI
Taste Labs
Revyl
Finta
Autumn
Supermemory
Exa
Warp
Pocket
Melius
Infisical
Krea
Goblins
RunPod
Town
Firecrawl
Aside AI
Taste Labs
Revyl
Finta
Autumn
Supermemory
Exa
Warp
Pocket
Melius
Infisical
Krea
Goblins
RunPod
Town
Firecrawl
Aside AI
Taste Labs
Revyl
Finta
Tailscale settings in Capy: the tailnet’s OAuth client minting keys for tag:capy marked Connected, and the projects list with capy-mobile turned on
Captain capy

Connect in four steps

Add a tag to your tailnet policy, create an OAuth client that can only write auth keys for it, connect it in Capy, and pick the projects whose machines join.

Read the setup guide
The Tailscale OAuth client dialog in Capy with a client ID, a hidden client secret and the machine tag tag:capy

One narrow scope

The OAuth client needs only Auth Keys write on your tag. Capy checks it against your tailnet before saving.

The Setup steps on Capy’s Tailscale page: create a tag, then create an OAuth client with Auth Keys write access on that tag

Steps in the app

Capy’s Tailscale page lists each step, with links to the tag docs and Trust credentials.

Capy in glasses

Only what your policy grants

Machines carry the tag you chose and reach only what your tailnet policy grants that tag. Scope that tag’s rules to the services agents need.

The connected tailnet row in Capy: an OAuth client minting keys for tag:capy, marked Connected

Tagged, short-lived nodes

Each join uses a single-use key that expires after five minutes. Tailscale removes the node after the machine pauses.

The Projects list on Capy’s Tailscale page, with two projects turned on to join the tailnet

Project by project

Only machines in the projects you turn on join. Machines in other projects never do.

FAQ

FAQ

Setup, access, keys, and how to cut a machine off.

What do agents get access to?+
Only what your tailnet policy grants the tag Capy machines carry, so scope that tag’s rules to the services agents need. A destination can be a hosts alias, a Tailscale IP or CIDR, or another tag. A rule such as tag:capy to internal-db:5432 lets agents reach one Postgres port.
Do my services need to be public?+
No. Machines join your tailnet as nodes, so your private services stay off the public internet, and you keep no static IP allow lists.
How are the auth keys handled?+
Capy mints a single-use auth key from your OAuth client for each join. It expires after five minutes, is written to a root-only file for the join, and is deleted afterwards. Keys never appear in process arguments, environment variables or logs, and auth keys are never captured in project snapshots.
What happens to nodes when a machine sleeps?+
Tailscale removes the node automatically after the machine pauses or is destroyed. A resumed machine rejoins with a fresh key, so your machine list doesn’t collect stale entries.
What if a machine can’t join?+
A failed join never blocks a machine from booting. The machine runs without tailnet access and tries again on its next wake.
How do I cut off access?+
Turning a project off or disconnecting stops new joins. It doesn’t remove machines that have already joined: a joined machine stays on your tailnet while it runs, and can return after a pause, until Tailscale removes its node. To cut one off at once, remove its node in the Tailscale admin console, and revoke the OAuth client if the credential itself should die.
How many connections does an organization need?+
One. Connect once for the whole organization, then turn on the projects whose machines should join. Capy stores the client secret encrypted.

Give agents your private network

Connect your tailnet once, and machines in the projects you pick reach the services your tailnet policy grants.