Introduction

Pad launches isolated cloud development environments, called Pads, on demand. Each Pad is a Firecracker microVM you can SSH into, run code in, and expose preview URLs from. When you're done, tear it down cleanly.

Where to start

• : install the CLI, log in, and create your first Pad.
• : what a Pad is, how it's configured, and the lifecycle it moves through.
• : short walkthroughs for common tasks.
• : reference for every pad command.
• : the declarative TOML file that describes how your Pad is built.

How it works

1. You run pad up in a directory with a Padfile.
2. The CLI sends the Padfile to the Pad API.
3. The backend schedules a VM on an available host and runs your setup commands.
4. You SSH in, open preview URLs for exposed ports, or run commands remotely.
5. pad down destroys the Pad and frees the resources.