Servers and connections
Registering a server, testing the connection, setting restricted paths and choosing whether elevated access is allowed.
There is no pipeline to migrate and no agent to roll out. You install one desktop app, point it at a server you already have access to, and start asking.
After this, everything else happens in conversation.
It runs on Windows, on your own machine. Nothing is installed on your servers.
One activation per workstation. Your licence is tied to the machine, so a lost laptop does not cost you a seat.
Host, user and the SSH key you already use. Test Connection detects the operating system and the interpreters available on that machine.
Give it a folder or a repository. It reads the project to work out how it is built and what it needs, then tells you what it found.
Not a hello. Ask about the container that keeps restarting, or the build that will not start. That is the fastest way to know whether it is useful.
Short list, and most teams already have all of it.
Windows 10 or later. About 400 MB of disk. macOS builds are available on request.
SSH access with a user you control. Linux or Windows. No agent to install and no port to open.
Outbound HTTPS from your machine for model calls and licence checks. Your servers need nothing extra.
Start with a normal user. Elevated access is off by default and you turn it on per server only if you want it.
Full documentation ships inside the app, next to the thing it describes, so it stays current with the version you are running. Here is what it covers.
Registering a server, testing the connection, setting restricted paths and choosing whether elevated access is allowed.
Running the scripts you already have, streaming their output, stopping a runaway job, and keeping a version history when the agent edits one.
Letting it read a project so it understands the build, the deploy script and the services that belong together.
Registering a connection, running read-only checks, and how credentials are encrypted at rest.
Where your allowance goes, the day-by-day breakdown, and how to top up.
What is recorded, where it lives, and how to undo a change that has already been applied.
Inspect containers, read logs, check stats, restart services and run Compose stacks, just by describing what you want.
Read more →Test configs before they go live, read the right log, and reload safely, on nginx, IIS or Tomcat.
Read more →Run your existing deploy scripts, watch the output live, and get a straight answer about whether it worked.
Read more →Read-only checks and queries over your existing SSH connection, with credentials encrypted at rest.
Read more →Issue trusted, auto-renewing certificates, wildcards included, and get the paths handed straight back.
Read more →Read EC2, S3, Elastic IPs and EBS, spot what is quietly costing you money, and make changes only after you approve them.
Read more →Read jobs, builds, the queue and console logs, find out why a build failed, and trigger or stop builds with your approval.
Read more →Build, run and fix projects on your own computer, including installing the runtime the project needs.
Read more →Browse your Linux servers as a file tree and edit files in a real editor with syntax highlighting, find and replace and search across the whole box. Over the SSH access you already have, with nothing installed on the server.
Read more →Setup questions reach a person who has actually used this on production servers, not a ticket queue.