|
|
|
|
|
by Palmik
1034 days ago
|
|
This looks quite interesting, congrats on the launch! Reminiscent of fly.io. Is it a direct competitor, or is there a major twist to it? How do you handle apps composed of multiple services, if there isn't a configuration? The pricing is a bit confusing by the way, the free tier says "16GB of RAM & 16 vCPU per service" while in reality it seems you only get the 512mb RAM instance. |
|
We have similarities with fly.io (Firecracker MicroVMs on top of BareMetal) and also some key differences:
- we directly integrate with GitHub to automatically build your application on push. We support building native code with Builpacks or from Dockerfile in addition to pre-built containers.
- we put a CDN in front of all your services to provide caching and edge TLS termination
- technically, our internal network is a service mesh built with Kuma and Envoy
- overall, we aim to be a bit higher in the stack, instead of looking at providing low-level virtual machines, we want to focus on productivity features like preview environments
We actually thought zero infrastructure configuration. At this stage, there is some basic setup to do for a multi-service app. You need to configure the HTTP routes. We aim to add as much automatic discovery of the codebase as possible.
Thanks for the feedback on the pricing. $0 is actually the price of the plan and we provide $5.5 of free credit in the plan. It seems the “Up to” was somehow skipped in the “16GB & 16 vCPU per service”, this is indeed confusing.