Loading...
Every project is a different server, a different codebase, a different client asking for a live URL by end of day. Klystrr gives you one consistent workflow for all of them — SSH connection, build, PM2, Nginx, SSL — done once, repeatable forever.
The problem
As a freelancer, you are not just writing code — you are also the one who deploys it. And deployment, done manually, consumes more time than it deserves.
Every new client project means: SSH into a new VPS, install Node.js, configure PM2, write an Nginx server block, install Certbot, request a certificate, test HTTPS, debug whatever broke, and remember to share the URL.
The repetition is not the worst part. The worst part is that the repetition creates opportunities for mistakes — a missed npm install, a stale PM2 process, an Nginx config pointing to the wrong port. These mistakes take time to debug, and the client sees a broken deployment before you catch it.
The solution
Klystrr gives you a deployment workflow you configure once per project and run without thinking. Connect the client's VPS, link the GitHub or GitLab repository, set the commands — and every subsequent deployment is a single click.
PM2 process management, Nginx reverse proxy, and SSL are handled automatically. You get a shareable HTTPS URL from the first deployment. The setup takes minutes. The payoff is every deployment after the first.
Key features
Manage multiple projects across different servers from a single Klystrr dashboard. Switch between a client's React frontend, your own API project, and another client's backend — without switching terminals, SSH keys, or mental models.
The workflow is always the same: install, build, start. PM2 manages the process. Nginx routes traffic. Certbot issues the certificate. You define the commands once and Klystrr executes them the same way every time.
From the first successful deployment, your project is live at project-name.klystrr.app over HTTPS. Share the URL with your client for review while you continue development. No temporary tunnels, no raw IP addresses with ports.
Every deployment produces a detailed log: each command, its output, its status. When something fails, you know exactly what step failed and why — without SSH-ing into the server to investigate. Faster diagnosis means faster fixes.
Every deployment is recorded — timestamp, commit, success or failure, full log. If a client asks "what changed last Tuesday," you have the answer. If you need to understand why a deployment two weeks ago broke the app, the log is there.
Store environment variables per project in the Klystrr dashboard. They are injected at deployment time — no more manually editing .env files on the server, no more accidentally deploying with missing variables.
How it works
Add the client's VPS (or your own) to Klystrr with the IP address and SSH key. One-time setup per server.
Name the project, link the GitHub or GitLab repository, and select the deployment branch.
Enter the install, build, and start commands. These are exactly the commands you would type manually — you just type them once.
Set any required environment variables in the dashboard. No manual .env editing on the server.
Click Deploy. Klystrr runs the full sequence — pull, install, build, start via PM2, configure Nginx, issue SSL. Watch the log in real time.
Once the deployment succeeds, share project-name.klystrr.app with your client. HTTPS, live, immediately.
When you push a code update and need to redeploy, click Deploy again. The same sequence runs. No manual steps.
Real scenarios
The client has a $6/month Droplet on DigitalOcean. You connect it to Klystrr, deploy their React frontend and NestJS API as two separate projects, and deliver two HTTPS URLs on the same afternoon you finish the code.
You manage five clients, each on their own Hetzner or Linode VPS. In Klystrr, each server and each project is separate. You deploy a hotfix for client A without touching client B's server configuration.
A client's project receives weekly updates. Instead of SSH-ing in, pulling, rebuilding, and restarting PM2 each time, you push to GitHub and click Deploy. Five seconds vs. five minutes.
Before pitching to a new prospect, you deploy a demo version of a similar past project to a cheap VPS, get an HTTPS URL, and send it over. No "I'll set up something for you" — it's ready now.
A client requests changes after the initial delivery. You make the change, push to the branch, and redeploy in Klystrr. The updated URL is live before the client refreshes their browser.
They are paying for the working application. Stop spending hours on setup that should take minutes.
Start using Klystrr free — no credit card requiredOne dashboard. Every project. Consistent deployments every time.
Building a startup? See Klystrr for Startups →