Service-first DevOps workspace

DevHub

One local macOS control plane for remote services, SSH terminals, and AI-assisted DevOps debugging. Open the service, let DevHub manage the tunnel, keep the investigation beside the system you are operating.

Source SSH config aliases
Unit Named remote services
Transport Managed SSH2 forwards
Work Tabs, terminals, context
AI Agent Sessions and runbooks

Built around the way DevOps work actually happens

Remote development is usually a mix of internal web apps, SSH shells, logs, dashboards, scripts, and notes. DevHub turns those moving parts into one inspectable workspace.

Manage services, not tunnels. SSH forwarding is the implementation detail, not the user workflow.
REMOTE_WORKSPACE

One place for services and shells

Keep code-server, dashboards, notebooks, APIs, and SSH terminal tabs organized by host and service instead of scattering work across windows.

SERVICE_FIRST

Forwarding is automatic

Save the service name, host alias, protocol, and remote port. DevHub creates and restores the local loopback forward behind the scenes.

AI_DEBUG

Agent Sessions preserve knowledge

The local assistant helps debug remote systems, then consolidates the useful parts into scripts, notes, patches, and runbooks.

Service-first remote development

A service is the object you operate. DevHub reads your SSH config aliases, opens the right local forward, and keeps the remote tool available as a named workspace tab.

Stable service context The tab name, host alias, protocol, and port stay explicit.

Service registry

Add services by operational identity

Describe the remote thing you need to use: service name, SSH host alias, remote port, and protocol. DevHub handles the SSH2 forwarding and local URL.

DevHub Add Service form with service name, SSH host, remote port, and protocol
DevHub showing code-server opened as a remote service tab

Workspace tabs

Open real remote tools without leaving context

Run code-server, notebooks, admin UIs, and internal dashboards as service tabs. Keep the related host and terminal access next to the tool you are using.

Work with AI, debug with Agent Sessions

The assistant runs locally under DevHub and works through the same managed SSH context. Use it while you operate services, then capture the investigation as reusable DevOps knowledge.

Local-first assistant Scripts, notes, and runbooks stay inspectable on your machine.

AI beside the service

Ask questions while the remote system is open

Explain errors, plan the next diagnostic command, draft a fix, or summarize the current state without switching away from the service tab.

DevHub assistant explaining remote development workflow beside a service tab
DevHub assistant generating remote GPU debugging steps beside an SSH terminal

Agent Sessions

Turn debugging into auditable work

For deeper incidents, the assistant can prepare narrow checks, run them through managed SSH execution, and preserve the result as local scripts, notes, and runbooks.

For developers and operators who live across SSH hosts

DevHub keeps services, terminals, and operational memory in one macOS workspace.

Mac App Store

Operational modules

The interface is organized around the repeatable parts of remote development: discover hosts, register services, open tools, keep terminals nearby, and preserve debugging knowledge.