Own the deployment
Run it yourself, place it on a Raspberry Pi, or choose a managed environment when that fits better.
Monitoring + remote access / built for small ops teams
Infrastructure keeps odd hours.
Control watches the fleet. TermHop gets you to the terminal. Self-host either one, and keep the important security boundaries visible.
42 O’CLOCK / SYSTEM INDEXREV. 01
01
CONTROLmonitor · alert · govern · recover
02
TERMHOPpair · connect · terminal
03
RUN IT YOURSELFx86_64 · arm64 · armv7
DESIGN RULE outbound by default / explicit when dangerous
Two tools / two trust boundaries
Watch the system. Then work the problem.
Control and TermHop share an operating philosophy, not an all-powerful login.
Available for testing
Control
Monitor remote infrastructure, route useful alerts, recover critical configuration, and govern actions from one control plane.
Explore ControlPublic beta
TermHop
Reach your Linux, macOS, or Windows terminal from a browser while terminal contents stay encrypted between browser and agent.
Explore TermHopBuilt for the awkward middle
Enterprise-shaped responsibility. Small-team reality.
Keep the edge outbound
Remote agents call home. Your monitored sites do not need new inbound management ports.
Make actions accountable
Roles, allowlists, approvals, and audit records are operating primitives—not enterprise add-ons.
Control / connection model
No new inbound management port at every site.
Control’s agents establish encrypted outbound tunnels. The hub can observe and issue governed commands without exposing a remote administration port at every site.
Read the security modelREMOTE SITEControl agent · no inbound port
42 O’CLOCK CONTROLHub · policy · audit · recovery
Next step
Start with Control.
Build the current open-core release, enroll a test node, and see the entire path before you commit to a deployment.