Managed Reachability
Thirp Cloud is managed reachability to named private Services over an outbound Agent and an open data plane — plus Thirp Marketplace for local apps you run and dial from the cloud.
Thirp Cloud for Support is the design-partner path for support organizations — vendors and operators who need bounded remote reach into customer-controlled environments.
Thirp Cloud for Platforms is for organizations that run platforms for others — dial-tone so their agents and apps can reach named private Services without inbound holes.
Thirp Marketplace is for builders and users of applications who want to own their own bits — local apps and MCP servers agents can leverage, with Thirp making the connection easy.
Support organizations (product vendors, appliances, and operators who support many customer environments — including short-stint / contract support).
Reach one named private Service with the customer holding approval and revocation. Bounded window; audit of who / Service / when — not session payloads. No inbound customer port for the relay path.
Organizations running platforms for others that need temporary, named reachability to private Services.
Admit / revoke / bounded access over the Runtime data plane. Building and dogfooding — not public signup, not GA. The name of a Service is not permission.
Builders and users of applications who want to own their own bits.
Run local apps and MCP servers on your machine so cloud agents can use them. Thirp connects without opening your firewall. Early access starts with GPU Offload and Google Sheets — more apps follow.
Thirp Runtime is the open-source relay, Agent, CLI, and embeddable SDK. Run it yourself with file-backed policy or incorporate it into your product.
Field Notes are short public write-ups on real support-access and platform-reach problems — free to read, no newsletter signup. Some notes are about supporting software in customer-controlled environments; Platforms notes are starting to appear as well. Read Field Notes.
