Sandman
Boring Infra Co.InstallDocsGitHub
A Boring Infra Co. product

Disposable clouds
without the setup.

sandman create provisions an isolated environment on AWS or GCP — then destroy deletes it. No IAM archaeology.

curl install command

curl -fsSL https://boringinfra.company/sandman/install.sh | sh

Homebrew install command

brew install boringinfraco/sandman/sandman

npm install command

npm install -g @itssergio91/sandman

Requires Node.js 18+. Then sandman init gcp or sandman init aws.

-// create a GCP project, link billing, enable APIs, hope you remember to delete it
+sandman create demo --ttl 2h

The teardown is the product.

Intent is a name. Truth is the environment. TTL and destroy make leftover projects a command, not a guilt trip.

Sandman Create
LIVE

DISPOSABLE·Isolated GCP project. Destroy is one command, or the TTL reaps it.

Init first · Destroy when done · Click a step to inspect

One environment. Six steps. Each one is inspectable. sandman create in action.

This is all it takes.

No Sandman account. No control plane. Your cloud credentials, a local CLI, and a name.

1. Init
// Wire up provider credentials
sandman init gcp
2. Create
// Isolated env. TTL optional.
sandman create demo --ttl 2h
3. Destroy
// Tear it down. No guilt trip.
sandman destroy demo

Your creds stay yours.
There is no Sandman cloud.

Sandman talks to AWS and GCP with credentials already on your machine. State lives in ~/.sandman/config.json. Nothing is uploaded to us. Nothing phones home except the providers you chose.

Your machine · Source of truth
// Local ledger. Your account.
const state = "~/.sandman/config.json";
const cloud = "your account";

Real cloud APIs. Your credentials. No Sandman account required.

Hosted control plane · Does not exist
// Nothing to send. Nowhere to send it.
if (sandmanCloud) return null;

No silent upload of your environments. Sandman does not need a hosted backend.

A sandbox you cannot destroy is a liability. Sandman puts a timer on it.

Init. Create.
Connect. Destroy.

Sandman does not replace Terraform. It hides the 40-minute account setup so you can demo, prototype, or let an agent try something throwaway.

1

Init

Point Sandman at a provider — AWS, GCP, Cloudflare, or Vercel. Uses credentials already on your machine. No billing setup from us.

2

Create

Provision an isolated environment by name. Enable services with sandman enable. Set a TTL. Get cost warnings before anything spins up.

3

Destroy

sandman destroy demo tears it down. TTL auto-reaps via doctor --reap. Leftover sandboxes are a command, not a story.

What do you get?

Clean environments on real clouds, a local ledger you can read, and a destroy button for the parts of your account that used to be permanent.

Disposable by design

create, use, destroy. No leftover projects.

TTL that reaps

--ttl 2h. doctor --reap cleans expired environments.

Dry-run first

create --dry-run previews the environment. Nothing writes.

Start throwing away for real this time

Install the CLI. Init a provider. Create something you plan to delete.

curl install command

curl -fsSL https://boringinfra.company/sandman/install.sh | sh

Homebrew install command

brew install boringinfraco/sandman/sandman

npm install command

npm install -g @itssergio91/sandman

Then sandman init gcp. Then sandman create demo.

View on GitHub