Live data from Hacker News

Exe.dev

exe.dev

51–60 of 316 posts

Re: Exe.dev

#51

Some actual details here: https://exe.dev/docs/how-exedev-works https://exe.dev/docs/pricing

Thanks! We've added those links to the top text above.

Re: Exe.dev

#53
This is freaking fantastic. However, as a community college instructor I would like to have this self-hosted on a computer in campus. Excluding the CLI niceties, etc., it shouldn't be to hard to get a similar setup with Docker et al, right? (not for production)

Re: Exe.dev

#54

Earlier quoted context omitted.

Hello, exe.dev person here. I have not used E2B (though I really like their web site), though it looks like there are quite a few differences. Our disks are persistent (without manual snapshotting), we have a TLS proxy by default with built-in auth and link sharing. It also looks like they have many features we do not have (yet). I believe the target use is also quite different. You can use exe.dev VMs for running yo…

Thanks for the response. In the "How exe works" page, it's mentioned that exe runs on bare metal with Kata containers, how is it different from firecracker? Were there any advantages?

The mention of Kata is out of date, we are fixing that, thanks! Our underlying VMM is very similar to firecracker (same upstream source). We believe our advantages are in how we run it. Several blog posts are in the works about technical details!

Re: Exe.dev

#55
Dang, everything about this feels really well considered. Semi-throwaway, nearly bare-metal machines that I can put on the internet with basically 0 config? I'll take

Re: Exe.dev

#56

Dang, everything about this feels really well considered. Semi-throwaway, nearly bare-metal machines that I can put on the internet with basically 0 config? I'll take

[exe.dev co-founder] Or don't throw them away! The disk persists. And thank you!
Post reply on HN