one key · every service · every environment

One key.
Every service.
Every environment.

Stack Start is the infrastructure layer between your AI agent and the services it needs to build. Connect your provider accounts once, get one key that resolves to your entire stack across dev, staging, and production, and let your agent start building immediately.

※ live demo · one key, every serviceidle
NeonClerkResendVercelSentryPostHogR2UpstashBrowserbaseInngest
ss_demo
.env · paste these two lines
STACKSTART_KEY=ss_demo·0000·0000·0000·0000·0000·0000·0000
STACKSTART_ENV=development
live demo·resolves the public demo bundle. No signup required.·Sign up for a 14-day Pro trial.
※ one key resolves to
NeonCloudflareClerkResendUpstashSentryRender+ 16 more
the first hour of every project

Your agent is ready to build. Your infrastructure isn't.

Agents got 10x faster. The infrastructure underneath them did not move. Here is the first hour, before and after.

● before stack start

Sixteen tabs and a sticky note.

  • Six dashboards. Six sign-ins. SMS verify. Twice.
  • Paste the keys into .env, Cursor, Vercel, CI. Each one. As tradition demands.
  • Half are scoped to dev. The half you needed for prod.
  • Mail sender isn’t warmed. Open a ticket. Touch grass.
  • Tell your agent to build. It politely cannot reach the database.
Time to first commit4–6 hrs
● with stack start

One stack. One key. Building.

  • Pick a stack. We wire every service in parallel because life's short.
  • One master key. One line into your editor. That's the whole onboarding.
  • Dev, staging, prod resolve from the same key. Yes, really.
  • Senders warmed, regions set, credentials valid the moment you paste.
  • Your agent connects. It ships the feature you actually opened the laptop to ship.
Time to first commit90 sec
how it works

Three steps. Then your agent does its job.

step 01 / 03

Select or build.

Pick a stack we've already vetted (Starter, SaaS, Agent Native) or build your own from 23 services we believe in. No infinite menu. No paradox of choice.

stackstart › select
› saas (5 services)
› agent native (7)
› build your own à la carte
step 02 / 03

Connect once.

Click connect on each provider. We sign in on your behalf, build the resources, warm the senders, hand back one master key. Takes longer to describe than to do.

provisioning…
neon · iad1 240ms
clerk · prod 620ms
resend · warmed
ss_4f9c·a02e
step 03 / 03

Paste. Ship.

Two lines in your editor. Your agent reads the key, asks for the environment it needs, gets a full bundle. The thing nobody designed an onboarding flow for.

# .env.local
STACKSTART_KEY=ss_4f9c…
$ claude build signup
db, auth, mail wired
deployed · preview
the part no vibe tool has

One key. Every environment.

Same key, three environments. Your code reads STACKSTART_ENV and gets back exactly the credentials that match. Dev one minute, staging the next, prod when you push the button. No more three .env files. No more asking which one you committed.

※ one master key
ss_4f9c·a02e·b711·8d24
resolved environment · development
$ stackstart resolve --env=development
DATABASE_URL=neon://dev-db.iad1…
CLERK_SECRET_KEY=sk_test_4f9c…
RESEND_API_KEY=re_dev_a02e…
REDIS_URL=redis://dev.upstash…
SENTRY_DSN=https://dev@sentry…
two builders · one product

Whoever you are, the wall is the same.

You opened the editor to build a thing. Let's build the thing.

Nobody opens Cursor hoping to wire six dashboards. Pick a stack, mint a key, paste two lines. Your agent reads the key and starts on the product. The boring part of the project is, technically, the part you skipped.

  • One key, every editor
    Cursor, Claude Code, VS Code, shell, your weird one-off CLI. Paste it once. Everything resolves.
  • No more three .env files
    Change one env variable. Get the right credentials. Dev, staging, prod, all from the same key.
  • No Sunday morning debugging
    Senders warmed, regions set, credentials valid the moment you paste. The boring stuff, handled while you were typing.
cursor · my-app
# .env.local
STACKSTART_KEY=ss_4f9c·a02e·b711
// agent, automatically:
db.query() → neon
auth.session() → clerk
mail.send() → resend
signup flow shipped
“wait, isn't this just…”

No. And we'd know, we use those too.

“…just Heroku / Render?”

Those host your app.

A PaaS runs your code on its boxes. We don't want your code. We provision the services you already want, on your own accounts, and hand you one key. The day you outgrow us (we hope you do), your stack keeps running. Nothing to migrate.

“…just a secrets manager?”

Vaults store. We resolve.

A vault is a vault. You still sign up at every provider, click through every wizard, paste every key in. We do that part for you, then derive scoped keys per environment on top. The secrets are managed even though, technically, you never had to look at them.

“…just cloud IAM?”

IAM is one cloud.

IAM is one cloud. Real teams use Neon and Vercel and Sentry and Clerk and four other things in a tab nobody can find. We give you one revoke button that reaches all of them, one audit log to hand the auditor, one set of scoped keys. The next time someone leaves, you press one button and go to lunch.

0s
median cold-start
Click select to first deploy. Faster than your kettle.
0
credential to manage
Rotate it. Your code never knew.
0
environments, one key
Dev, staging, prod. Same key, different bundle.
0
providers, growing
Curated, not infinite. The ones we'd pick ourselves.
pricing

Free until your first deploy. Honest after.

free
$0
For your first project and the weekend hack. Yes, all three environments.
  • 1 seat (solo), 5 stacks across dev, staging, prod
  • 1 PR-preview snapshot per stack
  • 200 resolves per hour per key
  • 14-day audit retention
Start free
pro
$23/mo
For the indie shipping real things. Two coffees, one cold start gone.
  • 3 seats (you and two collaborators), 20 stacks
  • 10 snapshots per stack for PR previews
  • Multi-account per provider (personal + work)
  • 30-day audit retention, 2000 resolves per hour
Start 14-day Pro trial
team
$300/mo
When ‘who has the prod key?’ stops being funny.
  • 15 seats included, $20 per seat beyond that
  • 50 stacks, workspace key policies (per-role, per-user)
  • Cascade revoke kills provider tokens upstream in one action
  • 90-day audit retention + CSV / JSONL export
Choose Team
enterprise
Talk
For the org running on it. Procurement-friendly, on-prem optional.
  • Unlimited seats, unlimited stacks, unlimited workspaces
  • SSO and SCIM (SAML, OIDC), enterprise controls
  • 365-day audit retention with export
  • Dedicated solutions engineer, VPC or on-prem option
Talk to us

Stop being the credential librarian. You have a product to ship.

One master key. Paste it once. Your agent reads it, resolves every credential it needs, and goes to work. You go to lunch.

your master key · preview
ss_4f9c·a02e·b711·8d24·c0ff·ee15
↳ resolves every service across dev · staging · prod. Rotates on demand.