SvelteFire Kit

SvelteFire Kit takes a different approach from most SvelteKit starters. Instead of the typical Postgres + ORM + custom auth stack, it goes all-in on Firebase. Authentication, database, file storage, hosting, and serverless functions all come from one provider. If you’re already comfortable with Firebase, this eliminates decision fatigue and lets you ship fast.

The Firebase Auth integration covers the major providers: Google, GitHub, email/password, and phone number verification. Session management uses Firebase’s ID tokens with SvelteKit server hooks for route protection. The Firestore integration is where Svelte 5’s reactivity shines — real-time subscriptions update the UI automatically through runes, with no manual state management needed.

What stands out

The real-time experience. Firestore’s snapshot listeners combined with Svelte 5 runes create a genuinely reactive UI. Update a document in the Firebase console and watch it appear on screen instantly. For collaborative features, dashboards with live data, or chat interfaces, this real-time foundation saves substantial development time.

The developer experience for prototyping is excellent. Firebase’s free Spark plan gives you generous limits for auth, database, and hosting. You can go from npx degit to a deployed app with authentication in under 15 minutes. The Firebase emulator suite is pre-configured for local development, so you’re not hitting production services while coding.

Cloud Functions are scaffolded with TypeScript and include examples for common patterns: sending welcome emails on user signup, processing webhook events, and running scheduled cleanup tasks.

Where it could improve

The SSR story is incomplete. Authenticated pages fall back to client-side rendering because Firebase Auth’s session management doesn’t play naturally with SvelteKit’s server-side hooks. The starter includes a workaround using cookie-based sessions, but it feels bolted on rather than native. Pages flash briefly while auth state initializes client-side.

Firestore’s NoSQL model is a double-edged sword. Simple queries are fast and intuitive, but the moment you need joins, aggregations, or complex filtering, you’ll restructure your data or move logic to Cloud Functions. Developers coming from SQL databases frequently underestimate this adjustment.

The Firebase SDK’s bundle size is hard to ignore. Even with tree-shaking, the auth and Firestore modules add roughly 80KB gzipped to your client bundle. For a landing page or content site, this overhead would be excessive, though for an app with authenticated users already loading Firebase, it’s an acceptable trade-off.

Vendor lock-in is the elephant in the room. Firestore, Cloud Functions, and Firebase Auth are proprietary. If you outgrow Firebase’s pricing or need features it doesn’t offer, the migration cost is significant.