# Stripe Projects CLI Add third-party services to your app, sync credentials to your project, and manage upgrades. For more details, see the [Stripe CLI reference](https://docs.stripe.com/cli.md). > Stripe Projects is available in public preview. Join the waitlist at [projects.dev](https://projects.dev/) to request early access. 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, authorisation 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, authorisation instances and analytics projects - Store credentials in the vault and sync them to your environment (`.env`) as environment variables - Manage upgrades and rotate credentials After you associate a provider account with your Stripe account, it remains authorised until you explicitly remove the association. You can reuse a provider account for new projects in the same Stripe account. If you want to use a different Stripe account, you must associate the provider account again. You can initialise a project in a new directory or an existing codebase. If you use an existing codebase and add services, new credentials and environment variables are merged into your existing environment (`.env`) and project configuration. ## Before you begin - A Stripe account - The [Stripe CLI](https://docs.stripe.com/stripe-cli/install.md) installed and up to date - The Projects plugin installed: ```bash stripe plugin install projects ``` ### Use a coding agent You can ask a coding agent to install the Stripe CLI, and Projects plugin: ```bash Install the Stripe CLI, install the `projects` plugin, verify `stripe projects --help` works. ``` ## Quickstart This example attaches hosting, a database, authentication and analytics to a project, then syncs credentials into your local environment. ```bash # Create a project stripe projects init my-app # Associate a provider account or add a service stripe projects link vercel # or stripe projects add vercel/project # Add more services stripe projects add clerk/auth stripe projects add posthog/analytics ``` Stripe Projects stores credentials in the vault, and syncs the environment variables to your local environment (`.env`) automatically: ```bash VERCEL_PROJECT_ID=... SUPABASE_DATABASE_URL=... CLERK_SECRET_KEY=... POSTHOG_PROJECT_API_KEY=... ``` ## Create a project Run `init` in the directory you want to use for your project: ```bash stripe projects init [name] ``` This initialises 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. ## Use a coding agent When you initialise 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 then 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. This means you can provision, upgrade, configure, and sync credentials using the same deterministic, auditable path as using the CLI directly. To avoid browser pop-ups during provisioning and credential exchange, we recommend the following flow: - Sign in to your Stripe account. - Associate your existing provider account (or create a new one) with `stripe projects link`. - Add a payment method with `stripe projects billing add`. - Start the agent session. ## Check project status After you’ve added services or connected providers, run `status` to review your project: ```bash stripe projects status ``` This shows your project name, Stripe account, associated provider accounts, provisioned resources, current tiers and health status. ## 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, authorisation and analytics. ### Add services to an existing codebase You can initialise 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. ### Work in multiple environments A single Stripe project can represent multiple environments, including development and production. Associate or provision the resources that you need for each environment, and then sync the variables into the appropriate project configuration and local `.env` files. ## Browse the service catalogue Use `catalogue` to list all available providers, their service categories, plan tiers, add-ons and pricing: ```bash stripe projects catalog stripe projects catalog stripe projects catalog ``` ## Manage a service ### Add a service Add a provider’s service to your project: ```bash stripe projects add / ``` 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. ```bash stripe projects link ``` ### Remove a service Remove a service from your provider account and local project: ```bash stripe projects remove / #or stripe projects remove ``` ### Rotate a credential Rotate credentials for a specific service: ```bash stripe projects rotate / #or stripe projects rotate ``` ### Upgrade a service tier You can upgrade the service tier when a service needs more capacity, features or limits than the current tier provides. ```bash stripe projects upgrade | / | ``` 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 tokenises your payment credentials into a [Shared Payment Token](https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens.md) and grants the provider a payment credential for that upgrade. The provider charges using that token. Your underlying payment credentials aren’t shared. > In the developer preview, this payment handoff is only available in the US, EU, UK, and Canada. ### Open a provider dashboard Open a provider’s dashboard in your default browser: ```bash stripe projects open ``` ## 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: ```bash stripe projects env ``` Environment variables also sync automatically after resource provisioning. ### Sync variables Update your local `.env` files and replenish your credentials vault. It also updates automatically after resource provisioning. ```bash stripe projects env --pull ``` ## Manage billing Payment methods are associated with your Stripe account. ### View the payment method Display your payment method on file: ```bash stripe projects billing show ``` ### Add or update a payment method Add a payment method or replace an existing one: ```bash stripe projects billing add ``` ## Generate LLM context Display and write a local file that combines your project context with all provider-supplied LLM context files: ```bash stripe projects llm-context ``` ## Use non-interactive environments Every command supports flags for non-interactive environments such as CI/CD pipelines, scripts and agents. ### Global flags | Flag | Description | | ------------------ | --------------------------------------------------------------------------------------------------- | | `--json` | Return output as structured JSON instead of formatted text. | | `--no-interactive` | Disable interactive prompts and confirmation dialogs. Commands fail when required input is missing. | | `--auto-confirm` | Accept confirmation prompts automatically, for example when you remove a service. | | `--quiet` | Suppress non-essential output and only return final results or errors. | ## Available providers These providers co-designed the integration protocol with Stripe. The protocol standardises provisioning, plan selection, upgrades and credential handoff. | Provider | Primary categories | | ------------ | --------------------------------- | | Vercel | Hosting | | Cloudflare | Hosting, domains | | Railway | Hosting, database, storage | | Fly.io | Hosting, database | | Supabase | Database, authentication, storage | | Neon | Database, authentication | | PlanetScale | Database | | Turso | Database | | Chroma | Vector database | | Clerk | Authentication | | PostHog | Analytics, feature flags | | Amplitude | Analytics, feature flags | | Mixpanel | Analytics | | Firecrawl | Search | | OpenRouter | AI models | | Hugging Face | AI | | Inngest | AI | | Runloop | Sandboxes, hosting | 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](https://projects.dev/providers). > #### Request a provider > > Contact [provider-request@stripe.com](mailto:provider-request@stripe.com) if you’re interested in becoming a provider on the Stripe Projects network or want to request a specific provider. ## Command reference | Command | Description | | ------------------------------------------------ | --------------------------------------------------- | | `init ` | Create a project and sign in or register. | | `status` | View project name, services, tiers and health. | | `catalogue` | List available providers, categories, and services. | | `add /` | Add a service to your project. | | `link ` | Connect a provider to your project. | | `remove / | ` | Remove a service from your project. | | `rotate / | ` | Rotate credentials for a service. | | `upgrade / | ` | Change the tier of a service. | | `open ` | Open a provider’s dashboard in the browser. | | `env [--pull]` | List or sync project environment variables. | | `billing show` | View the current payment method. | | `billing add` | Add or replace a payment method. | | `llm-context` | Generate a combined LLM context file. |