The server is still running, but the laptop is at home. Sometimes you only need to inspect a resource or run a command. Capidock brings SSH connections and Coolify instances into mobile workspaces, so that finding the right environment does not become the first troubleshooting task.
Capidock is an open-source Zephyrus product. Here is a practical tour of its current scope, including the boundaries that matter before you connect a real server.
Organise environments before opening a terminal
A workspace groups related instances. You can separate a homelab from a personal project, search instances and move them between workspaces. The guided setup takes you through the first workspace and connection. Name environments clearly: “production” and “test” are more useful distinctions than two nearly identical hostnames.
That organisation is a convenience, not an access-control boundary. Server accounts and permissions still determine what a connected user may do. A purple interface cannot make a destructive command harmless.
SSH for interactive work
The terminal supports password or private-key authentication, including compatible encrypted keys. Shortcuts provide arrows, Tab, Esc and Ctrl combinations that are awkward on a phone keyboard. On compatible Linux/POSIX servers, the app can show system information, uptime, memory and disk usage.
The first connection asks you to confirm the server host-key fingerprint. Compare it with a fingerprint obtained through a trusted independent route; accepting an unfamiliar value without checking defeats the purpose. Later connections verify the saved fingerprint. An unexpected change deserves investigation, even when a legitimate server rebuild might explain it.
Use an account with permissions appropriate to the task. Before running a command, confirm the host and working directory. For a long or delicate maintenance operation, a larger screen and a planned recovery procedure may still be the better choice.
Coolify: visibility, not deployment controls
Connect to your Coolify installation over HTTPS with an API token. Capidock displays application, database and service names and statuses returned by that API. The integration currently supports viewing resources. It does not provide deploy, restart or stop actions.
This distinction matters when choosing a tool for an incident. Looking up resource status is useful; it is not the same as a complete incident-management console or continuous monitoring service. Keep your existing monitoring and administration procedures.
Local configuration has practical consequences
Workspace settings and credentials are encrypted on the device. Capidock requires no Capidock account and has no backend, telemetry or cloud synchronisation. Connections go directly to the servers you configure. Network access and a reachable server are still required: local configuration does not turn remote SSH into an offline feature.
Protect the phone itself and keep its operating system updated. Encryption does not eliminate the consequences of an unlocked or compromised device. Plan how to revoke server credentials and Coolify tokens if the device is lost. Do not assume that reinstalling the app or signing into a new phone will restore settings through a Capidock cloud account; there is no such synchronisation.
A useful first session
- Create a test workspace and give the instance an unmistakable name.
- Use a non-production server and appropriately limited credentials.
- Verify the SSH fingerprint through an independent trusted source.
- Inspect system information, then run a harmless command such as printing the working directory.
- For Coolify, confirm that the expected resources appear and remember the integration is read-only.
- Check your credential-revocation procedure before relying on mobile access.
The interface supports English for the US and UK, Portuguese for Portugal and Brazil, and Spanish for Spain. A robotic capybara supplies the welcome. You remain responsible for the commands.
Explore the product
Capidock on Google Play · Source code on GitHub. Feature descriptions are based on the product's official store materials supplied by Zephyrus. This is an explanation of the product, not an independent security audit or a promise of uninterrupted remote access.