Hubseat Desktop: your secure gateway to cloud services
A desktop app that authenticates with Hubseat, tunnels TCP to service containers, and keeps production access off public endpoints.
**Hubseat Desktop** is the client we ship for engineers who need to reach Hubseat Cloud services from their machine — safely.
The problem it solves
Databases, caches, and internal APIs should not be exposed on the public internet for convenience. Traditional VPNs add friction; sharing jump hosts and passwords does not scale.
Desktop sits in the middle: you sign in with your Hubseat identity (via **Authsense**), pick a **service container** in your project, and start a **local TCP listener** tunneled through Hubseat infrastructure.
How the proxy works
From the **Proxy** view you search eligible containers, open a connection, and get a `localhost` port mapped to the remote service. Traffic flows over Hubseat’s proxy layer — authenticated and scoped to what your user can access.
When you disconnect, the listener stops. No long-lived holes punched in security groups “just for debugging.”
When teams use it
- Local app development against a staging database
- Running migrations with familiar GUI clients
- Verifying Redis, OpenSearch, or app HTTP ports during an incident
- Onboarding a developer without handing out shared credentials
Relationship to Hubseat Cloud
The cloud console is where you **provision and govern** services. Desktop is how you **attach** to them from a laptop without breaking the security model.
Together they complete the loop: platform teams keep control; product engineers keep velocity.