like you give 2 cpu. 8gb memory for 20vms. Which I believe you wont be able to use 20 of them at the same time if they share 2 cpu only
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 your agent. But you can also use it for hosting your site. E.g. blog.exe.dev is an exe.dev VM.
(We have also built some interesting tech behind this that we are excited to write up, I have a doc two pages long of blog posts we want to write.)
https://blog.exe.dev/meet-exe.dev
Secure Connection Failed
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.Firefox nightly
148.01a
I'll check for updates
Edit: still broken
148.0a1 (Build #2016134322), 757b8230f44e4152aeb7b9031ff95219471ab993 GV: 148.0a1-20251226204324 AS: 148.20251224050247 OS: Android 15
Edit: also same on OnePlus Nord N30
147.0b7 (Build #2016133535), 455e50920c4926534376b719df4cf1ed714bc61d GV: 147.0-20251222164020 AS: 147.0 OS: Android 14
What TLS error do you get? Untrusted CA?
I am not sure. I even tried Google Chrome
This site can’t provide a secure connection blog.exe.dev sent an invalid response. ERR_SSL_PROTOCOL_ERROR
https://i.imgur.com/HOwb7g3.jpeg
also tried mozilla firefox on desktop
Secure Connection Failed
An error occurred during a connection to blog.exe.dev. SSL received a record that exceeded the maximum permissible length.
Error code: SSL_ERROR_RX_RECORD_TOO_LONG
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem.
ssl labs says everything is fineWe do not want to end up in the state AWS is in, where any production work requires navigating the differences between how AWS manage v4 and v6. And that means rolling out v6 is going to be a lot of work for us. It will get done.
I added a public tracking bug here: https://github.com/boldsoftware/exe.dev/issues/16