What it feels like building with Stripe Projects

Summary

The post recounts a 60-minute attempt to build a GitHub traffic dashboard with Stripe Projects, motivated by GitHub’s 14-day limit on traffic history. Using Cursor’s agentic chat workflow alongside Projects, the builder assembled a Next.js application with Auth0 authentication, Supabase persistence, Prisma schema management, Vercel hosting, scheduled jobs, environment wiring, and periodic GitHub traffic synchronization. The experiment largely avoided direct coding and instead tested whether AI-mediated orchestration could produce a production-shaped stack quickly. As services and credentials appeared across providers, the main difficulty shifted from implementation to understanding ownership, deployment topology, environment management, and operational flow. The repositories synced, charts populated, and historical data appeared, while the experience also exposed a need for clearer generated architecture or infrastructure-as-code descriptions of the assembled system.

Takeaways

1. 1

   Stripe Projects assembled Auth0, Supabase, Vercel, Prisma, scheduled jobs, and connected environment configuration with little manual setup.

2. 2

   As orchestration compressed implementation work, understanding resource ownership, provider relationships, deployment topology, credentials, and operational flow became more difficult.

3. 3

   The completed application synchronized repositories, populated charts, and preserved historical GitHub traffic data, while manual work remained for callbacks, tokens, deployments, synchronization, and environment debugging.