AI Post

Unlimited agents with unlimited databases.Excited to see projects.dev take off Your browser does not support the video tag. Stripe @stripe We're rolling out Stripe Projects, a new tool in the Stripe CLI that lets you provision real services from the terminal, keep resources in your provider accounts, sync agent-ready credentials safely, and upgrade to paid tiers when you need more, without rebuilding your stack or leaving your terminal. Go from a local repo to a working stack backed by provider accounts you own. Attach hosting, a database, auth, analytics, and AI-friendly building blocks, then sync real credentials back into your environment safely. Upgrade your service to a paid tier and have Projects handle payment without re-entering payment details across provider dashboards. Step 1: Install the Stripe CLI and create a ProjectInstall the Stripe CLI and the Stripe Projects CLI plugin. In your local project directory, initialize a project: brew install stripe/stripe-cli/stripe && stripe plugin install projectsstripe projects init [my-app]What you should expect: A project named my-app (or same as your directory name) is created and populated with .projects configurations, a blank .env, and relevant agent skills. You’ll be guided to add new services or link existing provider accounts. Your project is configured with a secure place to keep credentials, and can sync them into local development, CI, or a team secret manager depending on your workflow. What is a project? A project is the unit Stripe Projects manages. It’s a lightweight manifest plus a Stripe-backed record of the services you’ve attached, the provider accounts you own, and the credentials those services require. It’s designed to make your setup repeatable across machines and teammates, and deterministic enough for agents to operate safely. Step 2: Add services from providersWe’re co-designing the integration protocol with some of the most popular providers developers use when building a production-ready stack. The protocol standardizes provisioning, plan selection and upgrades, and credential handoff so the Stripe CLI, and your agents, can do this reliably across providers. Services available in the developer preview: @vercel @railway @supabase @neondatabase @PlanetScale @tursodatabase @trychroma @posthog @clerk @RunloopAI Example flow: stripe projects catalogstripe projects add vercel/projectstripe projects add neon/postgresstripe projects add clerk/authstripe projects add railway/bucketstripe projects add chroma/databaseStep 3: Upgrade to a paid tier when you’re ready (with payments handled securely)A common flow is to start on a free tier, then upgrade once your app is real. # See what you’re runningstripe projects status# Upgrade to a paid tierstripe projects upgrade <provider>/<service>Projects will handle the payment step without you re-entering payment details across provider dashboards. Add your payment method to Stripe once. Then, when you select a paid plan in the CLI, Stripe tokenizes your payment credentials into a Shared Payment Token and securely grants the provider a scoped payment credential for that upgrade. The provider will charge using that token, while your underlying payment credentials stay protected and are not manually copied around. In the developer preview, this payment handoff is only available in the US, EU, UK and Canada, for supported providers and plans. Step 4: Sync credentials to your environmentstripe projects env --pullThe biggest security footgun in developer workflows is key sprawl: keys living in Slack messages, old .env files, random notes, and half-rotated tokens that nobody wants to touch. With Stripe Projects, onboarding a new engineer onto an existing project becomes a predictable, auditable step instead of a scavenger hunt. If someone gets a new laptop, switches dev boxes, or you spin up a fresh environment in CI, you can re-sync the right credentials in minutes with the same flow every time, without exposing secrets. Here’s what that can look like after a sync, with values redacted: VERCEL_PROJECT_ID=...NEON_DATABASE_URL=...CLERK_SECRET_KEY=...POSTHOG_PROJECT_API_KEY=...CHROMA_API_KEY=...Get started from the CLI or through your coding agentIf you want the direct path, install the Stripe CLI and initialize a project: brew install stripe/stripe-cli/stripe && stripe plugin install projectsstripe projects init [my-app]Sign up for early accessStripe Projects is now in developer preview, join the waitlist and learn more. Any feedback, let us know. Posted Mar 26, 2026 at 4:00PM Posted Mar 26, 2026 at 4:51PM