Vibe Code Home

The layer that lets makers get paid.

Course Kit runs on it with real users and real money in production. Now opening to the first ten seed creators.

Visit the site Course Kit on the platform
Vibe Code Home homepage

Why it exists: From code to commercial assets

Plenty of people can build a side project. Very few can take money for it safely. Vibe Code Home is the layer that closes that gap — and Course Kit runs on it, with real users and real money, so I know it holds.

1 Build the core product The maker writes the thing itself, a Flutter app or a web tool.
2 Connect the platform layer Plug into unified sign-in, Stripe checkout, and entitlements across all three rails.
3 Sell and keep serving Sell across web and both app stores without running a billing system.

Where Course Kit sits as Proof-of-Concept

Course Kit is the first product running on the platform. It proves the infrastructure holds under real-world constraints: real users, real money, 3 app stores, and 1 unified account model. A second creator now runs their own SaaS on top of this layer.

Single Sign-On (SSO) Cross-Platform License Sync Zero Key Pasting Multi-Project Firebase

The engineering decision

Course Kit and the platform are two separate Firebase projects by design. Apple and Google receipts are verified inside Course Kit's backend; Stripe checkout lives on the platform side.

The client resolves conflicting purchase states by taking the highest tier, not the last write.

Course Kit project

Apple and Google receipts are verified here, inside the app's own Firebase backend.

Platform project

Stripe checkout runs on the Vibe Code Home side, in a separate Firebase project.

Two projects on purpose. Neither one can quietly overwrite the other's receipts.

Apple / Google Course Kit backend Account tier Course Kit Stripe platform highest tier not last write
Three sources, resolved upward.

Entitlement Resolution Trade-Off Matrix

Architecture Strategy How It Works Operational Risk Why Chosen / Trade-off
Highest Tier Wins (Chosen) Client evaluates all 3 rails and grants access matching the highest valid subscription/purchase. Worst case: user retains access slightly longer if a refund webhook is delayed. Zero False Downgrades · Zero customer support friction for a solo operator.
Last Write Wins (Rejected) Latest incoming webhook or receipt timestamp overwrites the user's database status. Delayed webhooks or out-of-order retries silently strip paid access from paying users. High Support Risk · Unacceptable customer frustration.

What this shows

What gets rewarded here

Not the instinct that asks what would be fun to build. The one that asks what creators are already struggling with, what they would pay to stop struggling with, and what the business needs to run reliably.

Status

Course Kit is live on the platform. We are currently recruiting the first ten seed creators.

vibecodehome.io → · Read the Course Kit case study →