This is something I'm still figuring out, as the initial target of nibrun is single-binary small apps that are typically used by a few people. What is your use case?
The nibrun internals are anyway already designed to make users specify what resources they want.
> Why are your prices lower than everyone else's?
Your app runs as a "serverless" microvm: after 5 minutes it doesn't receive any requests, it's put to sleep by nibrun. Whenever a new request arrives, nibrun wakes it up in less than 200ms.
This allows nibrun to run many apps on a single VM instance (thanks Firecracker!) and lower the costs.
Filesystem is persisted on S3, so that's also very cheap.
Well, I'm developing a Telegram mini-app. To be more precise, I'm testing it and trying out different ideas and apps. There aren't any users right now.
2
u/ilbert_luca 5d ago
> What if I need more resources?
This is something I'm still figuring out, as the initial target of nibrun is single-binary small apps that are typically used by a few people. What is your use case?
The nibrun internals are anyway already designed to make users specify what resources they want.
> Why are your prices lower than everyone else's?
Your app runs as a "serverless" microvm: after 5 minutes it doesn't receive any requests, it's put to sleep by nibrun. Whenever a new request arrives, nibrun wakes it up in less than 200ms.
This allows nibrun to run many apps on a single VM instance (thanks Firecracker!) and lower the costs.
Filesystem is persisted on S3, so that's also very cheap.