FYO Forge — Found Your Own Forge
Sign in with Google and Tailscale. Press Found. About twenty minutes later you own a private, verified production platform — in your own account, nothing on the public internet, a receipt for every step. Then launch the next thing on it. And the next.
You built it in a weekend. Now where does it live? On the box you’re afraid to touch? On a platform that owns your pricing and your data? Or behind a month of Terraform, Kubernetes, and the fifteen things around Kubernetes? Launching right has been a separate career. It shouldn’t be.
Join the waitlist
Three things, all free to set up, and FYO Forge walks you through each one and checks it before founding starts. If you have never touched Google Cloud or heard of Tailscale, that’s fine — that’s what the walkthrough is for.
Google Cloud is where your forge runs — in a project that belongs to you, on your own billing. Creating it is a few screens with a credit card, and the app shows you which ones. You pay Google only for what your forge uses, and the app shows you the estimate before anything billable exists.
Tailscale makes a private network between your devices, wherever they are, with nothing for you to run or expose. Your forge joins it as one more device — which is how it can be reachable by you, and by nobody else on the internet. It installs in a minute and signs in with the same Google account.
Your forge gets a name under a domain that’s yours, and every door you open gets a name under it. Use your favorite registrar; if you don’t have a favorite yet, Cloudflare and GoDaddy are the popular ones. The app checks the domain and shows you exactly where to point it.
Twenty-two phases, each one verified against what actually came up and sealed as a receipt. Your only decisions: approve the price before anything billable exists, and trust your forge on your Mac at the end.
Below “has a platform team,” everyone launching software today walks one of three roads. Each one is fine — until it isn’t.
A VPS, docker-compose, maybe Kamal. It works, and it works for a long time.
Then it’s the box you’re afraid to touch. Everything on it faces the internet. Secrets live on its disk. Upgrades are you, at night. There is no second environment, and you are the on-call rotation. It sucks later — and later arrives exactly when you have customers.
Vercel, Railway, Render, Fly. Genuinely easy.
But it’s theirs: their pricing when they change it, their kill switch when an automated system flags you, public by default, your data and code on their terms. Every question that starts with “but I want to own…” is answered “later.” Leaving is a migration project.
A cloud account, Terraform, Kubernetes, and the fifteen things around Kubernetes that make it usable.
A private network, a private cluster, egress, a certificate authority, certificates, DNS, a registry, GitOps, identity, access control, routing, monitoring. This is what platform teams do, and it’s why they’re called teams. Weeks to get right the first time, kept right forever, and nothing verifies it for you.
Yes — and you should know what you’d be signing up for. Terraform is how you write infrastructure down. It doesn’t know what to write. It doesn’t know that a private cluster needs a way to reach its registry, or that a certificate authority’s root belongs in a key service and not on a laptop, or which fifteen components fit together at which versions. It doesn’t verify that what came up is what you meant. It doesn’t upgrade those fifteen things, and when one upgrade breaks, it doesn’t roll back.
Terraform describes infrastructure. FYO Forge decides what the infrastructure should be, builds it, proves it came up right, and keeps it right — and everything it builds is standard, readable, and yours. If you enjoy that work, or have a team for it, use Terraform with our blessing. If you’d rather launch, this exists so you don’t have to become that team first.
A private, production-grade place to launch that one person can found in an afternoon, learn to own, and keep owning without it becoming their job.
It runs in your own cloud account, under your billing, your identity, your keys, your registry, your domain. FYO holds no keys to it and no access after founding.
Nothing about it listens on the internet. You reach it over your own private network — which means you can deploy to production while it is still private, vet it there with real people, and open the public door progressively when it’s ready. Deliberately, one app at a time, and only that.
Every step of founding is checked against what actually came up, and sealed as a receipt you can read later. Not “the script finished.” Proof it’s right.
Certified updates arrive for the whole stack; each one verifies itself and rolls back on its own if it fails. You still own it and you still run it — but the bar to start right, and the effort to keep it right, both drop by a lot.
Everything inside is standard, open, battle-hardened software you could run anywhere, and the copies are yours. Stop paying and it keeps working; you just stop getting new things. Leaving is a supported exit, not a punishment.
I ran my own version of this first: custom integrations across a fleet of small servers. It felt great — until automated management of it melted the whole fleet, with a blast radius I still think about. The lesson was structural: build far less bespoke technology, stand on battle-hardened components, and confine the clever parts to the thing that sets it up.
Kubernetes is under the hood because it is the battle-hardened substrate. FYO Forge takes on the fifteen things around it that were the actual pain, and everything you touch is stock Kubernetes — so what you learn owning a forge transfers anywhere, and stays yours if you ever leave.
If you’ve sworn off Kubernetes, you’re right about the reasons and wrong about the conclusion. Here are the reasons, and what a forge does about each.
FYO Forge is a Mac app. It founds a forge in your Google Cloud account on your Tailscale network in about twenty minutes: a private console, workspaces, doors, certified updates with rollback, receipts, and a rehearsable break-glass path. Early access is small on purpose.