DorkySandboxes you can talk to

A real, isolated machine with its own filesystem, its own address on the open web, and a boundary that answers only the keys you cut.

Getting started

Dorkyfile services

Declare it in a file

A Dorkyfile is your machine written down. It lists the services the machine runs, the routes it serves, and the upstreams its turns send to. Apply the file and the machine becomes that description.

One command to converge

dorky apply makes a machine match its Dorkyfile. It provisions the machine on first run and reconciles it on every run. Preview any change with --plan before anything ships.

Reachable, and gated

Every machine answers at its own address behind one public door. Deny is the default, so a scoped key reaches only the routes you opened for it and nothing else.

What is Dorky?

Dorky gives you a managed server your agent lives on. It is a real, isolated machine with its own filesystem, its own address on the open web, and a boundary that answers only the keys you cut.

You describe the machine in a small TOML file called a Dorkyfile. It lists the services the machine runs, the routes it serves, and the upstreams its turns send to. Running dorky apply makes the machine be that description. It provisions the machine the first time and reconciles it to the file every time after.

The page you are reading is itself a Dorky machine. It is a single static service, the built documentation, declared by a docs.dorky.toml file and served from docs.dorky.host.

Where to go next

Getting started installs the CLI, signs you in, and applies your first machine.
Dorkyfile services shows how to declare the services a machine runs, ship code and files, and preview exactly what travels.
The machine model explains what a Dorky machine is and what you hold at each tier of access.