VibeFast
Introduction

Technology Stack

Why the combination of Next.js, Expo, and a choice of Convex or Supabase makes VibeFast a high-leverage starter kit.

Why this combination?

VibeFast is opinionated about one thing: moving from idea to production with the least amount of undifferentiated work. Every choice in the stack reflects that goal and is still flexible enough that teams with their own preferences can treat VibeFast as a clean sandbox or a reference implementation.

Next.js for web, SaaS, and full-product surfaces

Next.js is the most battle-tested platform for serious web apps right now. It gives you marketing pages, docs, dashboards, APIs, background routes, and SaaS portals in the same runtime. The VibeFast Next.js app can be the marketing site, admin console, or the full product experience you launch to customers. You get server rendering, streaming, and route-level control without introducing a second repo.

Expo + React Native for cross-platform mobile and shared UI

Expo accelerates React Native projects because it handles native tooling, dev builds, and OTA updates for you. It keeps iOS, Android, and AI-friendly workflows tight: most AI copilots reason better with Expo/React Native than other native stacks. Building on Expo means you ship polished mobile clients with minimal platform drift.

Backend — Convex or Supabase

VibeFast supports two backends. You choose during vf init:

  • Convex — TypeScript functions with reactive queries that auto-update your UI
  • Supabase — PostgreSQL database with SQL queries and Row-Level Security

Both provide auth, storage, AI features, and self-hosting. See Choose Your Backend for a full comparison.

Monorepo to keep everything aligned

Having Expo, Next.js, and your backend in one workspace means you only need to think about one set of dependencies, one shared UI/system theme, and one backend. Shared packages (UI components, types, helpers) prevent copy/pasting logic between mobile and web. Your backend lives in one folder (packages/backend/), so every client calls the same APIs.

The VF CLI keeps this stack usable

All that power only works if it stays manageable. The vf CLI lets you initialize a Clean or Custom project (vf init), pick your backend (Convex or Supabase), choose platforms (Native, Web, or Both), and toggle features with vf add/vf remove. No manual wiring across 20 files when you want to try a chatbot, image generator, payments flow, or tracker app.

Even if your day-to-day stack is different, VibeFast gives you a fast sandbox for a new mobile + web project. Use it for experimentation, boilerplate-free prototyping, or as the backbone of a full SaaS product.

Found an issue or bug in the docs?

Help me improve! If you spot any errors, typos, or have suggestions, please let me know.

Reach out on X/Twitter @zafarbuildzz

On this page