Solutions
What people build on Etorm.
A few of the problems Etorm was designed for. Each one links to the page with the details.
Put machines in different places on one network
Laptops, servers in a rack, a box under someone's desk: give each one a WireGuard key and they share one private Ethernet segment, with addresses and names handed out for you. Broadcast, multicast, DHCP and DNS all work the way they do on a local switch.
Run IPv6-only without a fight
Every VPC gets an IPv6 /64 and nothing on the platform needs IPv4. Leave out the IPv4 network and you have an IPv6-only segment, with DNS answering on the segment's own address.
Write your own network service
A DHCP server, a DNS resolver, a firewall, a protocol nobody else speaks. Write it as a small WebAssembly program and run it on your VPC as a process. It gets its own interfaces, answers frames directly and keeps its state between them.
Compute · Write your first program
Keep backups and artifacts private
Push reports, backups and build artifacts into a bucket with curl. Etorm encrypts every object with the bucket's own key before it is stored, and who can read it follows your project's roles.
Storage · Store objects in a bucket
Draw the network instead of writing it
Lay out networks, machines and services on the canvas, reuse parts as modules, and watch the live state on every block. If you prefer text, the same drawing is a Diagram resource you can keep in git and apply with kubectl.
Share a project with your team
Send someone a one-time invitation link with a role. You can see who has access at any time, and the audit log shows every change and every refused request.