Architecture
Internal app boundaries, release outputs, data model, and extension points for VibeShip.
VibeShip has three layers: SaaS foundation, agentic guidance, and customer distribution tooling.
The private source-of-truth monorepo keeps the internal VibeShip app and customer template source in apps/marketing.
Route groups separate public marketing, Clerk auth pages, authenticated app routes, and API handlers.
Data access is isolated behind repository interfaces so SpacetimeDB can later be swapped or joined by another adapter without rewriting routes.
Provider-aware billing normalizes Stripe and generic Polar events into shared customer, purchase, subscription, and entitlement records.
The workspace launch checklist proves the route, data, entitlement, email, and agent-preflight path end to end.
The operator dashboard is gated by ADMIN_EMAILS and reads users, workspaces, purchases, subscriptions, and integration health through repository boundaries.