MeshHand runs on a plain Ubuntu server that already has everything a website or a small application needs. Your part is one step: buy a domain and point it at the server. The agent does everything after that.
$ you: A record @ → server, CNAME www → @ ✓ done by you > meshhand reads brief: 4 pages, copy from vault > writes /var/www/yourshop.com/ (index, about, services, contact) > writes nginx server block, enables site, reloads ✓ > certbot: yourshop.com + www.yourshop.com ✓ HTTPS > HTTP→HTTPS redirect, HSTS, www→apex ✓ > robots.txt, sitemap.xml, 404.html ✓ > commits source to vault, pushed ✓ > GET https://yourshop.com/ → 200, 41 ms ✓ LIVE > elapsed 00:47:12 · model cost $1.83
Register the name anywhere. Add an A record for the apex and a CNAME for www. Five minutes at the registrar. Nothing to install, no control panel to learn, no hosting account to open. Everything that used to be a project is already running on the box.
Point the domain. The agent takes it from there.
No hosting fee per site. The server is already paid for. A domain is the only cost.
From brief to live HTTPS for a marketing site. Same day for this one.
Web server, certificates, firewall, scheduler, and agent are already there.
This is the same recipe that put meshhand.com online. The agent remembers it, so the second site is faster than the first.
Any registrar. A record to the server, CNAME for www.
A short brief: purpose, pages, where the copy comes from, the domain. A message or a file in your vault.
Plain HTML and CSS you own, written into the site's folder on the server.
Writes the nginx block, enables the site, reloads. One file, no downtime for anything else on the box.
Let's Encrypt certificate for apex and www, redirect from HTTP, HSTS on, auto-renew already scheduled.
robots, sitemap, 404 page. Source committed to the vault. Live site read back over HTTPS and confirmed.
Edits are a message. Redeploy is one push.
What used to be a hosting signup, a control panel, an FTP upload, a certificate purchase, and a support ticket is now a DNS record and a conversation.
Same pattern, plus a service. The app runs under systemd on a local port. nginx proxies /api/ to it over HTTPS. Secrets stay in a server-side env file. Scheduled jobs use the same scheduler the agent already uses. The book-a-call form on this site works exactly this way.
Nothing here gets bought, installed, or configured again for the next site.
The server is configured once and every site inherits it. The agent keeps the recipe that worked, including the gotchas, so it never re-learns the same lesson.
| The usual path | What it costs you | MeshHand on Ubuntu |
|---|---|---|
| Shared hosting with a control panel | Click-through setup per site, FTP uploads, vendor SSL, no shell, no real scheduled jobs | One config file and one certificate command. Full shell. Real scheduler. |
| Site builders | A monthly fee per site, locked templates, poor exports, no backend | Plain HTML and CSS you own, in git, with any backend on the same box |
| Platform-as-a-service | Per-project accounts, build minutes, cold starts, usage pricing, one more dashboard | Zero incremental cost per site. One server, one login, one place to look |
| A new server per project | Provision, harden, install, certify, wire up deploys, repeat | Done once. Reused for every site after |
| A web agency | Weeks, a quote, a maintenance contract | Hours, and the deploy recipe stays in memory for next time |
Every claim above is something that has already happened on the server this site is served from.
meshhand.com went from copy to live HTTPS the same day. When the www record was added that afternoon, the certificate was expanded to cover it within the hour.
Running unattended since January 2025. A MeshHand install has delivered scheduled work for a Michigan lodge every week with zero missed runs.
21 pages rebuilt and redeployed in one pass on a second server for the MeshHand rename, then again the same night for a homepage change.
The form on this site is a static page, an nginx proxy, and an existing API. No form backend had to be written.
MeshHand's job is the six back-office tasks inside Prophet 21. Building and hosting a site is what the same agent, on the same server, does on the side.
A page or a report the agent built and hosted for you is the first thing you see working. Before Control Tower has approved a single release.
A vendor portal, a branch price sheet, a promo page, a dashboard for the sales floor. Hours, not a project. Ask on the call.
One server is one point of failure. Fine for marketing sites, demos, and small tools. A high-traffic store or anything with an uptime contract needs more, and we will say so.
Tell us what the site or the tool should do. If it is a fit, it can be live before the follow-up.
Book a 30-minute discovery call
MeshHand