Network and hypervisor isolated

A smarter wayto work

my-app · booting
Fast.
Booted in seconds.
Safe.
Sealed at the hardware. Its own kernel, filesystem and network stack.
Yours.
Root is handed to you. Keep it for as long as you need.

Isolation

Its own kernel. A hardware boundary.

Your machine is a real VM, not a container. There is no shared filesystem and no shared process list.

  1. A physical server.
  2. KVM turns its hardware into boundaries.
  3. Each VM boots its own kernel.
  4. A reach for a neighbour stops at KVM.
  5. Delete the machine. The disk goes with it.

Network

Decide what gets in or out.

A machine talks to nothing until you say so. Every attempt is logged, allowed or blocked.

policy · my-appup 00:14:07
deb.debian.orgallow
github.comblock
everything elsedrop
Your turn. Flip a rule, then send a packet.
egress loglive

    Integrations

    Keys never touch the VM.

    Clone a private repo or call ChatGPT and Claude from inside the machine. The credential is added on the way out, by the host.

    Upgrades

    Upgrades don't drop you.

    dpipe owns the connection, not dproxy. Shipping a new dproxy disconnects nobody.

    session connectedconnected for 00:00:00bytes dropped 0dproxy v1

    What it's for

    • Web development

      Build on a machine that isn't your laptop.

    • Malware analysis

      Open something risky, watch what it reaches for, then delete the machine.

    • Sandboxed evaluation

      Let your agent run the code it just wrote.

    • Demos

      Share what you made as a link. It opens in any browser.

    • Desktops

      A full desktop, right in your browser.

    • it's a computer · 2 vCPU / 4 GB

      Anything else

      It's a computer. Size it and use it however you like.

    Try now.

    my-app · idle · ready when you are

    1. PID 1
    2. Fast · Safe · Yours
    3. Isolation
    4. Network
    5. Keys
    6. Upgrades
    7. What it's for
    8. Try now