Two commands to Sentry: now on Stripe Projects

Two commands. That’s how little it takes to go from nothing to a fully configured Sentry project with error monitoring, performance tracing, and session replay:

stripe projects init my-app
stripe projects add sentry/project

No signup form. No email verification dance. No dashboard tab-switching to copy-paste a DSN into your .env. Your account is created, your project is provisioned, and five environment variables land in your working directory, ready for your SDK to pick up.

And if you’re using a coding agent? It does the same thing, except you didn’t type the commands. You just said “add error monitoring.”

What this actually is

Sentry is now a provider in Stripe Projects. Stripe Projects is a CLI workflow that lets developers (and their AI agents) discover, provision, and manage infrastructure services directly from the terminal. Think of it as a package manager, but for the services your app depends on at runtime.

Here’s the full catalog:

$ stripe projects catalog sentry

SERVICES
    project   ● Free tier
    seer      ● Paid

PLANS
    developer ● Free
    team      ● $29/month
    business  ● $89/month

Two deployable services (a Sentry project and Seer AI), three plan tiers. All manageable from the CLI. Billing goes through your existing Stripe payment method, with no separate Sentry billing setup.

The “just tell your agent” part

When you run stripe projects init, it scaffolds agent skill files into your project:

.agents/skills/stripe-projects-cli/SKILL.md
.claude/skills/stripe-projects-cli/SKILL.md
.cursor/rules/stripe-projects-cli.md

These teach Claude Code, Cursor, or any coding agent how to use the Stripe Projects CLI. The agent reads the skill, discovers available services via stripe projects catalog sentry --json, and provisions what you need.

A real interaction looks like this:

You: "Add error monitoring to this project"

Agent: [runs stripe projects catalog sentry --json]
Agent: [runs stripe projects add sentry/project --no-interactive --accept-tos]
Agent: "Done. Sentry is provisioned. Your DSN and auth token are in .env.
        I can integrate the Sentry SDK into your app next."

The agent doesn’t need special Sentry knowledge. It just needs the Stripe Projects CLI and the skill file that init already created. Provisioning becomes a step it handles between writing your code and running your tests.

Once the account is provisioned, you can ask the agent to instrument your app with sentry init. Since the auth token and DSN are already in the environment, the Sentry CLI knows exactly which project to target, with no configuration prompts, no guesswork.

Upgrades, downgrades, and the billing dance

Plans are first-class resources:

stripe projects add sentry/team                          # start on Team ($29/mo)
stripe projects upgrade sentry-plan sentry/business      # upgrade to Business
stripe projects downgrade sentry-plan sentry/team        # change your mind

All non-interactive, all scriptable. Billing happens through Stripe’s Shared Payment Token, so your existing Stripe payment method pays for Sentry with zero billing configuration on the Sentry side.

You can also add Seer (our AI debugging assistant) as a separate service:

stripe projects add sentry/seer      # $40/active contributor/month
stripe projects remove sentry-seer   # if you change your mind

The magic login

This one’s my favorite. When you need your Sentry dashboard:

stripe projects open sentry

This mints a single-use magic login URL. Click it (or let the CLI open it), and you’re logged into your Sentry dashboard. You skip the password prompt, the single sign-on (SSO) redirect, and the “which account was this again?” moment. Straight to your issues page.

It’s the kind of feature that sounds trivial but has a surprisingly dense security model once you start thinking about two-factor authentication (2FA) users, expired passwords, and SSO bypass prevention.

Multi-team collaboration

Here’s where it gets interesting. Stripe’s protocol distinguishes between the account owner (the Stripe account’s email) and the actor (the person running the CLI command). We use this to build a proper collaboration model:

• First team member runs stripe projects add sentry/project → creates the Sentry org
• Second team member runs the same command → joins the same Sentry org
• Everyone shares one org, one billing setup, one set of projects

We tie the Sentry organization to the Stripe organization, so everyone on the same Stripe account ends up in the same Sentry org. No per-developer silos, no “who created this and why can’t I see it” conversations.

Credential rotation

stripe projects rotate sentry-project

New DSN, new auth token, old ones revoked. The fresh credentials land in your .env automatically. The dashboard stays closed.

How to try it

1. Install the Stripe CLI and the Projects plugin:

   stripe plugin install projects

2. Initialize and add Sentry:

   stripe projects init my-app
   stripe projects add sentry/project

3. That’s it. Your SENTRY_DSN and SENTRY_AUTH_TOKEN are in .env, ready for any Sentry SDK to pick up.

For the full lifecycle (catalog browsing, plan management, Seer, deep links, credential rotation), check the Stripe Projects documentation.

If you’re building with AI coding agents and want error monitoring that provisions itself, give it a try. And if your agent breaks something in the process, well, you’ll have Sentry to tell you about it.