Launch: Miget – A New Kind of PaaS (No Per-App or Usage-Based Billing)
After years of pain using platforms like Heroku, Render, Fly, and Railway, we decided to build our own. It’s called Miget, and it rethinks both the developer experience and the economics of deployment.
Most PaaS platforms charge you per app, per dyno, per background worker, per staging environment, and so on. Or worse—usage-based billing that’s impossible to predict (hi Railway).
We flipped the model:
You choose a plan (with fixed CPU/RAM), deploy as many apps as you want inside it—frontend, backend, workers, databases-and that’s your bill. No surprises, no meter running in the background. Think VPS simplicity with modern PaaS DX.
Under the hood:
- Fair Scheduler based on CFS principles (like a smarter VPS)
- Kubernetes + microVMs (CloudHypervisor)
- Cloud Native Buildpacks or Docker builds
- Built-in IPv6, SSH, full API (coming soon)
- Transparent billing via Polar.sh
- Usage-based billing opt-in (coming soon)
Built for hackers, indie devs, startups building their MVPs or just tired of being nickel-and-dimed.
Clarification on the name: It’s Miget, pronounced like “widget.” Not “midget.” No relation, no offense intended-just a short, punchy name.
Would love your thoughts, feedback, roasting, or questions. Live now at https://miget.com
So for me, the clarification on the name makes it less understandable :)
Overall, the concept looks fine, but you probably need to refine your communications to be clear on what you are offering. Because if you are adding in usage-based billing and autoscaling... I have no idea what is differentiating you from the others.
At Miget, you always start with a fixed plan: say, 2 vCPUs and 4GB RAM. That’s your hard cap — you can deploy as many apps as you want within that limit. We support autoscaling within your plan, meaning your workloads can scale horizontally as long as you stay within your allocated resources.
We intentionally dislike mandatory usage-based billing because it often leads to unpredictable costs. That’s why we made it optional.
For advanced users or production workloads that do want to scale beyond their plan, we’re working on opt-in usage-based billing. But only if you explicitly enable it. That way, you get a stable, predictable base, and optional elasticity if your needs grow.
So the core idea remains: No surprises. You’re in control.