Run Many Apps & MVPs
The portfolio problem
Indie hackers ship small bets. I am a long-term prod member of the Small Bets community. The idea is to run not one huge bet but many, sequentially, sometimes in parallel. Ok: The sometimes in parallel thing is something I don’t get.
As building has now become so incredibly fast, launching feels extremely slow. There are things that cannot be taken away from us, such as writing copy yourself. What can be automated with the help of agents is the integration with other services and the deployment. And this is where agents really are a good fit with Kubernetes.
With a well-oiled deployment machine, the cognitive load of deployment and integration fades. I’m now almost looking forward to it.
One platform, N apps
Kubernetes itself already has many ways to separate workloads: Namespaces, network policies, resource quotas, node pools. Gardener adds to it that you can cheaply run apps in their own cluster if you like. But you don’t have to. A single cluster is a lovely launchpad for your apps.
When an app graduates
I am a placeholder.
Costs, again
Me, too.