Stripe Projects CLIPublic preview

Stripe Projects provisions and manages third-party services (such as hosting, databases, auth, AI, and observability) from the terminal. Run one command to create your accounts, sync credentials to your .env, and handle billing through Stripe.

• Provision services from 30+ providers. No separate dashboards.
• Sync credentials to .env automatically. No copy-pasting API keys.
• Manage plans, billing, environments, and keys from the CLI or your coding agent.

Start with a coding agent

Install the Stripe Projects skill in Claude Code, Cursor, Codex, or any MCP-compatible coding agent:

npx skills add https://docs.stripe.com --skill stripe-projects -g -y

Then describe the stack you want to your agent:

"Use Stripe Projects to set up a Next.js app with Supabase, Vercel, and PostHog."

The agent installs the CLI plugin, runs stripe projects init, adds your services, and syncs credentials automatically.

Quickstart

Install the plugin, create a project, add services, and pull credentials to your local environment:

stripe plugin install projects
stripe projects init
stripe projects add supabase/project
stripe projects add vercel/project
stripe projects env --pull

How it works

A Stripe project represents a single app or codebase, and groups together a provider account’s services and resources.

• Provider account: The account with your provider, such as Vercel, Supabase, Clerk, or PostHog.
• Service: The provider’s product offerings, such as a database, authorization, or analytics.
• Resource: An instance of the service for your account, and the associated credentials and environment variables (for example, test-db-1, auth, or test-analytics-1).

You can use a project to:

• Associate an existing provider account or create a new one
• Provision resources, such as databases, authorization instances, and analytics projects
• Store credentials in the vault and sync them to your environment (.env) as environment variables
• Manage named environments, such as development, staging, and production, each with its own output file and set of resources
• Manage upgrades and rotate credentials

After you associate a provider account with your Stripe account, it remains authorized until you explicitly remove the association. You can reuse a provider account for new projects with the same Stripe account. If you want to use a different Stripe account, you must associate the provider account again.

You can initialize a project in a new directory or an existing codebase. If you use an existing codebase and add services, new credentials and environment variables merge with your existing environment (.env) and project configuration.

How credentials work

Stripe Projects fetches credentials from each provider on your behalf, encrypts them in .projects/vault/vault.json, and stores them in the Stripe Secret Store:

• Local files: .projects/vault/vault.json stores an encrypted copy of your credentials. Your .env is the default output for local development. For named environments, the CLI writes to the configured output file, such as .env.dev or .env.production. The CLI creates output files with 600 permissions, so only you can read them on your machine. Don’t commit credential files to version control—stripe projects init adds them to .gitignore automatically.
• On removal: Running stripe projects remove <service> deprovisions the resource and removes it from your project state. The CLI doesn’t delete any credentials previously written to .env or .projects/vault/. Remove those manually, or run stripe projects env --pull to overwrite them with the current credential set.

To use your credentials in a production hosting environment, see Set up production environment variables.

Create a project

Run init in the directory you want to use for your project:

stripe projects init [name]

This initializes a Stripe project for that directory. If you omit the name, Stripe Projects uses the folder name.

Stripe Projects writes the project state under .projects/, which tracks the associated provider accounts, provisioned resources, and local project configuration. You can see the tools your project uses in .projects/state.json. The .projects/state.local.json file in your private repo contains the resource IDs that your team needs to share the same project state.

File reference

Use a coding agent

After you initialize a project, Stripe Projects writes coding agent skills into the local project directory. These skills provide context and actions for your agent to work with your project through the Stripe Projects workflow.

You can ask your agent to complete tasks, such as:

• “Link my existing Neon account and provision a database.”
• “Add Turso auth and PostHog on the free tier.”
• “Set up the services this repo needs and explain what changed.”

Your agent uses the same Stripe Projects CLI commands. You can provision, upgrade, configure, and sync credentials using the same deterministic, auditable path as the CLI directly.

To avoid browser pop-ups during provisioning and credential exchange:

1. Sign in to your Stripe account.
2. Associate your existing provider account (or create a new one) with stripe projects link.
3. Add a payment method with stripe projects billing add.
4. Start the agent session.

Check project status

After you’ve added services or connected providers, run status to review your project:

stripe projects status

This shows your project name, Stripe account, associated provider accounts, provisioned resources, current tiers, and health status.

For projects with named environments, status also shows environment membership and marks the active environment for this checkout.

List projects

Use stripe projects list to view all projects on your Stripe account.

stripe projects list

The command returns each project’s name, ID, and creation date. Use the project ID with stripe projects pull.

Pull a project

Use stripe projects pull to set up an existing project in a new local directory. Run it from an empty directory:

stripe projects pull <projectID>

The command creates .projects/state.json and .projects/state.local.json, then writes your .env file by running env --pull. It connects you to the project’s existing service instances — it doesn’t provision new ones.

To find a project ID, run stripe projects list.

Integrate projects into your workflow

You can use Stripe Projects for new apps, existing codebases, and active setups.

Start a new project

If you have a new app, you can create a project, associate provider accounts or create new ones, and provision resources, such as a database, authorization, and analytics.

Add services to an existing codebase

You can initialize Stripe Projects in an existing application directory. If you use an existing directory and add services, new credentials and environment variables are merged into your existing environment (.env) and project configuration. This is useful when an app already has hosting but requires services, such as a database, authentication, analytics, feature flags, or other managed infrastructure.

Manage an existing setup

When you associate the provider accounts you already use with your Stripe account, the project is represented in a single location. This also allows you to associate existing resources and add relevant environment variables.

Browse the service catalog

Use catalog to list all available providers, their service categories, plan tiers, add-ons, and pricing:

stripe projects catalog
stripe projects catalog <provider>
stripe projects catalog <category>

Use search to explore all available provider services related to a keyword:

stripe projects search <keyword>

Manage a service

Add a service

Add a provider’s service to your project:

stripe projects add <provider>/<service>

When you add a service, this action associates an existing provider account with your Stripe account or creates one, before adding the service.

Adding a service provisions a resource in your provider account. Use the add command to provision a database, auth instance, analytics project, feature flags, or other managed infrastructure for your app.

Associate a provider with the link command

Associate a provider account or create an account without provisioning a resource. This is helpful in agent-driven workflows, when you want to establish a connection with the provider before provisioning resources.

stripe projects link <provider>

Remove a service

Remove a service from your provider account and local project:

stripe projects remove <provider>/<service>
#or
stripe projects remove <resource_name>

Rotate a credential

Rotate credentials for a specific service:

stripe projects rotate <provider>/<service>
#or
stripe projects rotate <resource_name>

Upgrade a service tier

You can upgrade the service tier when a service needs more capacity, features, or limits than the current tier provides.

stripe projects upgrade <provider> | <provider>/<service> | <resource_name>

Before upgrading, review the current tier for each service in the status or your provider dashboard.

You only need to add your payment method to Stripe once. When you select a paid plan in the CLI, Stripe tokenizes your payment credentials into a Shared Payment Token and grants the provider a payment credential for that upgrade. The provider charges using that token. Your underlying payment credentials aren’t shared.

Open a provider dashboard

Open a provider’s dashboard in your default browser:

stripe projects open <provider>

Manage environment variables

Stripe Projects stores credentials in the vault, and syncs environment variables to your local environment (.env) automatically when you add or change services.

List variables

Display all project environment variables. Values aren’t revealed in the output:

stripe projects env

Environment variables also sync automatically after resource provisioning.

Sync variables

Update the active environment’s output file and replenish your credentials vault. For the default environment, this writes to .env unless you’ve configured a different output path. For named environments, it writes to the output file you configured when you created or updated the environment.

stripe projects env --pull

When to run env --pull

env --pull runs automatically after you provision a service, rotate credentials, or upgrade a resource. You don’t need to run it manually in those cases.

Run env --pull manually when:

• You’re setting up the project on a new machine or after cloning the repo.
• A teammate provisioned or rotated a resource and you need to pick up the updated credentials.
• Your .env was deleted or corrupted and you need to restore it.
• You want to verify that your local credentials match the current project state.
• You switched to another environment with stripe projects env use and need that environment’s credentials locally.
• You changed environment membership with stripe projects env add or stripe projects env remove.

stripe projects env --pull

Set up production environment variables

stripe projects env --pull writes credentials to the active environment’s local output file. It doesn’t write environment variables to your production host.

To use the same credentials in production, add them to your host’s environment variable settings. Stripe Projects doesn’t automate this step.

Manage multiple environments

Use project environments to keep separate credentials and resources for different stages of your app, such as local development, staging, and production.

Each environment has:

• A name, such as default, development, staging, or production
• An output file, such as .env, .env.dev, or .env.production
• A set of project resources whose credentials are written to that output file

Stripe Projects uses an active environment for local commands. Commands that add resources or sync credentials target the active environment.

List your environments:

stripe projects env list

Show the active environment:

stripe projects env show

Create a new environment and make it active:

stripe projects env create development --output .env.dev

Switch the active environment:

stripe projects env use default
stripe projects env use development

After you switch environments, stripe projects add provisions resources into the active environment, and stripe projects env --pull writes that environment’s credentials to its configured output file.

# Add a database to the active development environment
stripe projects env use development
stripe projects add neon/postgres --name dev-db
stripe projects env --pull

# Switch back to the default environment and pull its credentials
stripe projects env use default
stripe projects env --pull

Update the active environment’s name or output file:

stripe projects env update --name staging
stripe projects env update --output .env.staging

Delete an environment:

stripe projects env delete staging

You can’t delete the last environment or the virtual default environment.

Manage environment resources

Environment membership controls which project resources contribute credentials to the active environment’s output file.

Add an existing project resource to the active environment:

stripe projects env add <resource_name>

Remove a resource from the active environment:

stripe projects env remove <resource_name>

These commands only change environment membership. They don’t provision, remove, or rotate provider resources. To remove a provider resource from the project, use stripe projects remove.

Run stripe projects status or stripe projects services list to find resource names.

Manage billing

Payment methods are associated with your Stripe account.

View the payment method

Display your payment method on file:

stripe projects billing show

Add or update a payment method

Add a payment method or replace an existing one:

stripe projects billing add

After you set up a payment method, you can set a spend limit.

View your spend

Run stripe projects spend to see your spend for the current and previous months, broken down by provider.

stripe projects spend

The output shows your spend for:

• Current month: spend to date, by provider
• Previous months: total spend, by provider

Set a spend limit

Use stripe projects billing update to set spend limits on your payment method. You can set a global limit that applies across all providers, or a per-provider limit for more granular control.

Run the command interactively to choose the limit type and enter your values:

stripe projects billing update

You can also include the --limit flag directly to skip the prompts. To set a global limit across all providers:

stripe projects billing update --limit <amount>

To set a limit for a specific provider:

stripe projects billing update --limit <amount> --provider <provider>

Per-provider limits take precedence over a global limit when both are set. Run the command once for each provider you want to cap individually.

Generate LLM context

Display and write a local file that combines your project context with all provider-supplied LLM context files:

stripe projects llm-context

Share a project

Use stripe projects share to generate a URL that encodes your project’s service stack. The URL captures which services you’ve added, but not your credentials or configuration values.

Run this from a project directory that has at least one service:

stripe projects share

Copy the URL and share it with anyone. The URL is self-contained and doesn’t expire.

Set up a new project from a shared stack

Run stripe projects init with the --from flag in an empty directory:

stripe projects init --from <URL>

This initializes a new project and provisions fresh instances of each service in the shared stack.

Add services to an existing project

Run stripe projects import from an already-initialized project directory:

stripe projects import <URL>

This provisions the services from the shared stack and adds them to your existing project.

Available providers

These providers co-designed the integration protocol with Stripe. The protocol standardizes provisioning, plan selection, upgrades, and credential handoff.

Run stripe projects catalog at any time to view the most current list of providers and available service tiers. Or view the directory at projects.dev/providers.

Use non-interactive environments

Every command supports flags for non-interactive environments such as CI/CD pipelines, scripts, and agents.

Global flags

Command reference