How can you promise fixed resources and billing while also listing autoscaling as a feature? Likewise, in your intro above you both disparaged usage-based billing, and also said you were offering it soon.
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.
How can you promise fixed resources and billing while also listing autoscaling as a feature? Likewise, in your intro above you both disparaged usage-based billing, and also said you were offering it soon.
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.
Great question, let me clarify:
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.
I don't know about anyone else, but I pronounce midget and widget exactly the same. eg... soft I sound for the 'i' and a j sound for the 'g'.
So for me, the clarification on the name makes it less understandable :)
Hey, thanks for the comment - you're right.
It’s pronounced /ˈmɪgɛt/ – like it’s spelled, with a hard “g”. No relation to “midget”, no offense intended.
Thanks again for pointing it out!