Ashlr Stack docs

Three paths to Stack

Pick the one that matches where you are. You can mix and match — most users start with the quickstart, then come back for the CLI reference.

What Stack is

Stack is a thin control plane over the services your app actually uses. It drives provider login and supported creation or attachment, then attempts credential writes through Phantom, optional .env.example skeleton export, .mcp.json descriptors and .stack.toml split config. Populated env files are not generated automatically; writes and cleanup can be partial.

# inside an initialized project; setup can contact the provider
stack add supabase

What Stack isn't

• Not a secret manager. Persistence uses Phantom. Stack handles supplied values during setup and records dedicated slot names in config.
• Not a deploy tool. We don't rebuild Vercel or Railway — we just give them the keys they need.
• Not a lock-in. Everything writes to standard files: .env, .mcp.json, .stack.toml (TOML). Removing Stack does not migrate credentials or guarantee the app still boots; inspect its runtime dependencies.

The whole map

Everything in these docs, grouped by purpose:

Pre-alpha status