Top
Best
New

Posted by achairapart 22 hours ago

Exe.dev(exe.dev)
https://blog.exe.dev/meet-exe.dev

https://exe.dev/docs/how-exedev-works

https://exe.dev/docs/pricing

382 points | 224 commentspage 5
_init_wasfine 4 hours ago|
Looks like a trap at first. Who succesfully connecter ?
drakmail 10 hours ago||
I really like the experience, after being a stuck I just tried to ssh from my termux on phone and it really worked! Absolutely awesome
engr 7 hours ago||
I just tried this, genuinely groundbreaking! So quick to spin a VM and get going
tarrydev13 11 hours ago||
I'm trying to set it up but getting this error:

> ssh exe.dev

Please complete registration by running: ssh exe.dev Connection to exe.dev closed.

Anyone get a similar issue?

JohnMakin 21 hours ago||
The description of authentication mechanism is confusing me. it’s over ssh, but how is this integrated?

> Private by default, share with discord-style links exe.dev takes care of TLS and auth for you. By default only you can reach your HTTP services, and you have easy mechanims to share them with friends and colleagues.

Is anyone with access to a link able to get in?

achairapart 20 hours ago||
I also don't understand this: Everyone with the right domain can ssh-in the vm?

Edit: Answered below, thank you.

jauntywundrkind 21 hours ago||
You ssh in with any key, and it asks you for an email to verify. You're then at a exe.dev console.

There are a couple different link patterns:

  exe.dev ▶ doc sharing
  Sharing (sharing) - press q to exit
                                                                                                                                                                                                                                                 
  You can share your VM's HTTP port (see the http proxy documentation /proxy) with your friends. There are three mechanisms:                                                                                                                     
                                                                                                                                                                                                                                                 
  1. Make the HTTP proxy public with share set-public <vm>. To point the proxy                                                                                                                                                                   
  at a different port inside the VM, run share port <vm> <port> first.                                                                                                                                                                           
  Marking it public lets anyone access the server without logging in.                                                                                                                                                                            
  2. Add specific e-mail addresses using share add <vm> <email>. This will                                                                                                                                                                       
  send the recipient an e-mail. They can then log into exe.dev with that e-mail,                                                                                                                                                                 
  and access https://vmname.exe.xyz/.                                                                                                                                                                                                            
  3. Create a share link with share add-link <vm>. The generated                                                                                                                                                                                 
  link will allow anyone access to the page, after they register and login.                                                                                                                                                                      
  Revoking the link (which can be done with the remove-link command)                                                                                                                                                                             
  does not revoke their access, but you can remove users who are already                                                                                                                                                                         
  part of the share using share remove <vm> <email>.
JohnMakin 20 hours ago||
Thanks! love the idea, looking forward to playing with this. I understand now from comments that this was brought to this site sooner than intended, sorry if I asked in a rude way.
pacificat0r 6 hours ago||
Who puts pricing under docs/ ?
j0lol 21 hours ago||
Other than a quick boot, what separates this from going on a VPS provider and spinning up servers?
DoctorOW 21 hours ago|
Simpler and easier seems to be the answer. How much does it cost to spread 8gbs RAM across some VMs? Most providers require additional of how many VMs over how many hours, what the specs kf each are specifically, etc. Then once you have it you're setting up an SSH key or shared password depending on use and they make the authentication simpler as well. Maybe wouldn't be great for a huge business but it's you just wanted the ability to play with an isolated server, it might be worth it.
mrs6969 9 hours ago||
just to be clear, this is total resources for all the vm right ?

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

bhavaniravi 20 hours ago||
Are there any fundamental differences between E2B and this?
crawshaw 20 hours ago|
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 your agent. But you can also use it for hosting your site. E.g. blog.exe.dev is an exe.dev VM.

bhavaniravi 18 hours ago||
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?
crawshaw 15 hours ago||
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!
finalhacker 10 hours ago|
I like it. Great cli design. its so cool!
More comments...