Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Why would I use this over fly.io? It seems to be very similar at first glance


I can't even find their vm details (cpu/memory + bandwidth) and many other things.


Will add those to the landing page - they got lost in the Figma design


Same question here, it seems to be a fly.io clone without the global anycast network.


We do have a caching anycast proxy like fly, render, and other webapp-focused PaaS providers.


I'd like to try out your service, but would not be willing to link my GitHub account, and I do not have a Google account. Any chance of a non-federated sign in method?


What access does it require to your GitHub that you are weary about? (Actual question, I am not involved with Webapp.io at all)


Practically - We don't actually require you to use Docker, and we don't use it under the hood. The configuration (which looks like a Dockerfile) can run multiple containers in the same VM:

FROM vm/ubuntu:22.04

RUN (install docker)

RUN REPEATABLE docker-compose build

RUN BACKGROUND docker-compose up

EXPOSE WEBSITE localhost:8080

You can also just run entirely non-docker services:

RUN BACKGROUND redis-server

- The DSL will watch which files are used for each build step to skip everything you haven't changed, so builds are much faster - You can use us to clone VMs and run Cypress tests in parallel, then promote one of the clones to a preview environment, and another to a production environment - We're more declarative (in my opinion), we don't have a CLI. Everything is done by editing a Layerfile and git pushing it

TL;DR, we focused on a declarative configuration format to quickly build, fork, and hibernate VMs, where Fly is more focused on building/shipping docker containers (though the products do fill a similar niche)


Hey! Best of luck with this. Real quick: we don't use Docker "under the hood" at fly.io either. We take OCI containers as inputs, and transform them into VMs. The only "Docker" running here is the code that allows us to accept our users existing containers.


Sure, I meant "docker" here as a simplification for the OCI format.


It's good to diversify the built-on-Firecracker-as-a-service space.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: