How-to5 min read
How to point your own domain at your VM, with a real TLS certificate
It is a real VM at a real provider, so a domain and a real certificate are a DNS record away.
Your machine is a real VM at a real provider with a real public address. That means putting your own domain in front of it, with a proper certificate, is the same short job it is on any server.
Point a record at the box
In your DNS provider, add an A record for the name you want, pointing at the machine's address. Give it a few minutes to propagate, then confirm it resolves:
dig +short app.example.comGet a certificate
With the name resolving to the box, a tool like certbot can obtain and renew a Let's Encrypt certificate for it. From there you are terminating TLS on your own machine, for your own domain, exactly as you would anywhere else.
This is for services you host on the machine. Getting to the built-in tools — the editor, the terminal, the dashboard — already runs over the gateway and needs none of this.
More posts
How-to4 min read
How to run Claude Code in a browser, on any device
The agent CLI is already installed and running on the machine — you reach it through the same tab as everything else.
How-to4 min read
How to keep an AI agent running 24/7 after you close the tab
Detach from a session instead of ending it, and a long job keeps running while you are gone.
How-to5 min read
Running Docker on a cloud dev machine, with root on a real VM
You have root on a real VM, which means Docker runs the way it does anywhere else.