antrix.dev
Free Guide

Stripe Projects: Provision Your Stack from the CLI

From zero to a fully provisioned project with credentials in your .env.

Quick startWhat is itInstall CLIInstall pluginInit projectCatalogAdd a service

Reading this alone?

Do it with peers — bi-weekly calls, $29/mo founding.

Join →
Short and sweet

Two commands. Under two minutes.

Install everything

brew install stripe/stripe-cli/stripe && stripe plugin install projects

Then open Claude Code (or Codex) and run:

Claude Code

/stripe-projects

Example prompt

“Create an MVP hosted on Vercel, backed by Supabase for auth and database, PostHog for analytics, Resend for transactional email, and Clerk for user management. Write credentials to .env and scaffold the Next.js app.”

The agent provisions each service, writes all credentials to your .env, and scaffolds the project. You skip the 14-tab signup marathon and go straight to building.

Need the full walkthrough? The step-by-step guide starts below.

1

What is Stripe Projects

Stripe Projects is a Stripe CLI plugin. It provisions third-party services — hosting, databases, auth, analytics, AI tools — directly from your terminal.

Instead of signing up for each service separately and manually copying API keys, you run one command. Your .env is written automatically. The credentials live in an encrypted local vault, not in plain text.

It solves a real problem: code generation got fast. Provisioning didn’t.

Key properties:

  • →Resources provision in your own accounts on each provider, not in Stripe's
  • →.env is written automatically after each add command
  • →.projects/ directory tracks what's provisioned — commit state.json, gitignore vault/
  • →Works with agents, CI pipelines, and across teammates
2

Install the Stripe CLI

You need Stripe CLI version 1.40.0 or higher. Install for your platform:

macOS

macOS

brew install stripe/stripe-cli/stripe

Linux (Debian/Ubuntu)

Linux

curl -s https://packages.stripe.dev/api/security/keypair/stripe-cli-gpg/public | gpg --dearmor | sudo tee /usr/share/keyrings/stripe.gpg > /dev/null
echo "deb [signed-by=/usr/share/keyrings/stripe.gpg] https://packages.stripe.dev/stripe-cli-debian-local stable main" | sudo tee -a /etc/apt/sources.list.d/stripe.list
sudo apt update && sudo apt install stripe

Windows

Windows

scoop bucket add stripe https://github.com/stripe/scoop-stripe-cli.git
scoop install stripe

Verify (must be 1.40.0+)

Verify

stripe --version

Action steps

  1. 1Run the install command for your platform
  2. 2Run stripe --version and confirm 1.40.0+
  3. 3If upgrading on macOS: brew upgrade stripe/stripe-cli/stripe
3

Install the Projects Plugin

The plugin adds the projects subcommand to the Stripe CLI. It installs in seconds.

Install

stripe plugin install projects

Verify the install:

Verify

stripe projects --help

Reading this and want to actually do it with others?

The community is bi-weekly live calls, async accountability, and a group of builders shipping in parallel. Founding seats are $29/mo.

4

Initialize Your Project

Run this from your project directory. If it’s your first time, a browser opens to authenticate with your Stripe account.

Init

stripe projects init --json --yes

What this creates:

  • →.projects/state.json — tracks provisioned services (commit this)
  • →.projects/vault/ — encrypted credentials (gitignore this)
  • →.projects/cache/ — local cache (gitignore this)

Add these to your .gitignore:

.gitignore

.projects/cache
.projects/vault
.env

Action steps

  1. 1cd into your project directory
  2. 2Run stripe projects init --json --yes
  3. 3Complete browser auth if prompted
  4. 4Confirm .projects/state.json exists
  5. 5Update .gitignore with the three entries above
5

Browse the Catalog

See everything available:

Catalog

stripe projects catalog --json

Search for a specific provider:

Search

stripe projects search vercel --json
stripe projects search supabase --json

40+ providers as of mid-2026, organized by category:

HostingVercel, Cloudflare, Fly.io, Netlify, Railway, Render
DatabaseSupabase, Neon, PlanetScale, Turso, Chroma
AuthClerk, Auth0/Okta, WorkOS, Privy
AI/MLOpenRouter, Hugging Face, ElevenLabs, Browserbase, Inngest
AnalyticsPostHog, Mixpanel, Amplitude
ObservabilitySentry
CommsAgentMail, Twilio
CacheUpstash
CI/CDGitLab
SandboxDaytona, Runloop
SearchAlgolia, Firecrawl
6

Add a Service

General syntax:

Syntax

stripe projects add <provider>/<service> --json --yes --config '{"name":"<name>"}'

Vercel project example (note: --accept-tos shares your name, email, country, and phone with Vercel as part of account creation):

Vercel

stripe projects add vercel/project --json --yes --accept-tos --config '{"name":"my-app"}'

After provisioning Vercel, your .env contains:

VERCEL_ORG_ID=team_...
VERCEL_PROJECT_ID=prj_...
VERCEL_TOKEN=vca_...
VERCEL_PROJECT_URL=https://vercel.com/...

Supabase example:

Supabase

stripe projects add supabase/database --json --yes --config '{"name":"my-db","region":"us-east-1"}'

After provisioning Supabase, your .env contains:

SUPABASE_URL=https://...
SUPABASE_ANON_KEY=eyJ...
SUPABASE_SERVICE_ROLE_KEY=eyJ...

Build the full product

Stack provisioned. Now ship.

You have the services. The next step is building a product on top of them.

Ship Your Product

Full-stack app with auth, payments, and deploy →

Claude Code workflows, Next.js + Supabase + Stripe, Vercel deploy. From blank repo to live product.

Run the Machine

Full autonomous agentic framework →

Claude Code agents, autonomous overnight issue processing, orchestration dashboard. Ship features while you sleep.

The Community — Coming Soon

For AI-first operators who actually build the thing.

Builders, consultants, founders, freelancers — anyone whose income comes from shipping real work, not from selling courses about shipping.

AI isn't going to make you money. Products do. Clients do. Real businesses do. But AI is the unfair advantage — when you wire it into how you build, sell, and serve, you move 10x faster than people still doing it by hand.

Who it's for

Beginners

Learning AI from people actually using it, not just teaching it.

Builders

Ready to automate workflows — yours or your clients'.

Operators

Senior, deep in production, looking for peers and leverage.

You have real skills. You want AI as an unfair advantage on real work — building something of your own, leveling up at your job, or both — not another set of videos to watch.

What's inside

Direct access — me + the network

Bi-weekly Google Meet calls where we actually work. DMs and posts with me and other operators when you're mid-build and stuck.

  • Bi-weekly live calls — builds, Q&A, teardowns
  • Architecture + payment reviews on your code
  • Peer network of operators who actually ship
  • Paid client referrals when I'm overbooked

The production agentic stack

Everything I run on real client work and my own products — installed in your environment, not just shown in a video.

  • Antrix OS — the control room for your agent fleet
  • Installers: Ship Your Product + Run the Machine
  • ax-* skill packs (audit, deliver, simplify, content, more)
  • Multi-agent code review across parallel worktrees
  • Scheduled jobs, overnight pipelines, dual-AI planning
  • Setup library: Stripe, Supabase, Vercel, Resend

Antrix OS — the agent dashboard

Antrix OS — agent fleet dashboard

The control room I actually run my work from — every project, agent, skill, schedule, machine, and secret in one place. Members get the codebase.

Why this one is different

Most hosts make content.
I make products.

The platform doesn't matter — Skool, Circle, Discord, Whop, whatever. The problem is the host.

Most paid-community founders aren't shipping anything outside of the community itself. Their whole business is selling you the community.

I'm in production every day. The people I want next to me are too.

We level up together.

Most communities

  • Revenue IS the membership fee
  • Main output: content about the community
  • You learn from someone who only sells communities
  • Growth metric: new members

This community

  • Revenue is client work + products. Community is a side of it.
  • Main output: shipped code, deployed products, served clients
  • You learn from someone in production every single day
  • Growth metric: what members are actually shipping

Waitlist

Open · first cohort

Get in before the price moves.

Founding pricing exists for the first cohort. When it fills, the next one pays more — and joins behind it. Names get pulled in order.

  • Founding price locked: $29/mo
  • Bi-weekly live calls + brainstorms
  • Direct access: me + operator peers

Work with me directly

Senior engineering, paired with agentic AI.

I take a handful of clients each quarter. Direct work on your codebase, your stack, your business. No agency. No junior handoffs. You hire me, you get me.

I build with you

Pair sessions where we ship the product, the agent, or the integration that's been blocking you.

I wire AI into your business

Agentic workflows, multi-agent pipelines, and scheduled jobs that turn AI from a chat window into 10x leverage on actual revenue work.

I review what you shipped

Architecture, AI usage, payments. I'll tell you what's worth keeping, what to rip out, and what to ship next.

I set you up, you take it from there

Sometimes you don't need me to run it. You need someone in the room while you do. I'll show you the system.

Specialty — payments

Hundreds of millions processed across subscriptions, marketplaces, and migrations. If your product touches money, that's where I help most. Webhook reliability, marketplace splits, billing architectures — the kind of work where shipping wrong costs you money, not just time.

Tell me what you're building.

I reply within 24 hours.

LinkedInEmail