Connections
1
Aqui
Product
A hosted view of live Telepresence connection state, without asking developers to expose their laptop.
Aqui gives teams a browser-based way to understand whether a local Telepresence connection is active, which workloads are ready for intercept, and which workstation the current browser session belongs to. The goal is simple: make connection state easier to inspect, easier to support, and easier to discuss with the rest of the team.
What It Gives You
Useful answers without asking the developer to narrate their terminal.
Aqui is for the moments when a team needs a reliable picture of local connection state: what is connected, what is intercept-ready, and what each linked workstation exposes.
Session Health
Know whether the local Telepresence connection is actually live.
See connection status, cluster context, namespace, and last update time in one place instead of piecing it together from logs and screenshots.
Connection
Connected
Updated 12s ago
Cluster
Healthy
payments-dev
Workload Visibility
See what is ready for intercept and how it is routed.
Workloads, services, and ingress routes are grouped into a browser view that is easier to share with support, platform, or teammates during debugging.
orders-web
ReadyService orders-web (80->3000)
Route app.dev.example.com /orders
Workstation Context
Keep browser access tied to the machine it is meant to inspect.
Aqui keeps connection visibility machine-local, so a second browser on another computer does not silently borrow the wrong workstation session.
- Workstation
- MacBook Pro
- Connection
- payments-dev
How It Works
Aqui stays hosted in the browser, while the local companion keeps the workstation relationship explicit.
The product flow is straightforward: the developer signs in, installs the companion, connects from that workstation, and then Aqui shows the hosted connections view for that workstation.
1
Sign in from the browser
The developer starts from the hosted browser flow so the account and connections view live in one place.
2
Install and connect the local companion
The companion opens an outbound session so the browser can load Telepresence state from that workstation.
3
Inspect connection state from the browser
Once linked, Aqui shows connection status, workloads, and intercept context without asking the developer to expose inbound connectivity to the laptop.
Why Teams Use Aqui
The value is clarity, not spectacle.
Shorter debugging loops
Support and platform teams can see the same hosted connection picture instead of asking the developer to paste terminal output into chat.
Cleaner handoffs
The browser view makes it easier to discuss session health, routes, and workload readiness without depending on one person’s shell history.
More explicit access boundaries
Hosted visibility is tied to the current workstation context, so teams keep a clear boundary between browser access and local Telepresence ownership.