Machines inside your own network
Blog post from Boxd
Boxd’s Tailscale integration allows organizations to move their machines, including development workspaces, preview environments, and agents, from public internet access into their existing private tailnet while retaining the same hostnames, TLS certificates, SSH access patterns, and subdomain routing. Organizations provide Boxd with a reusable Tailscale auth key, after which Boxd’s edge servers join the tailnet as persistent boxd-proxy devices and route HTTPS, SSH, and exposed ports only through private 100.x addresses. Public access is blocked with nonrevealing 404 responses, while Boxd’s management API, CLI, console, and SDKs remain accessible from anywhere. The implementation isolates each organization’s traffic through separate Tailscale nodes and origin-aware routing, while preserving standard ownership and sharing controls. Teams must approve Boxd proxy devices, configure ACL access, disable device key expiry, ensure users are connected to the tailnet, and account for limitations involving per-machine custom domains, expiring auth keys, and corporate DNS resolvers that may reject Tailscale address ranges.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.