EdgeKit

EdgeKit bets on the edge stack: Turso for globally replicated SQLite, Drizzle for type-safe queries, and Cloudflare Workers for compute. The result is a SvelteKit app that responds in under 50ms no matter where your users are.

The philosophy is radical minimalism. No auth, no payments, no styling framework — just a SvelteKit app with a fast database and a clean project structure. You add what you need.

What stands out

The latency numbers. Turso replicates your SQLite database to edge locations worldwide. Combined with Cloudflare Workers running your SvelteKit server functions at the edge, every request stays close to the user. We tested from Tokyo, London, and São Paulo — response times were consistently 30-45ms.

Drizzle with SQLite is a joy. The schema is simple, migrations are fast, and the type safety catches errors before they reach production. For apps with straightforward data models, this combo beats Postgres + Prisma on developer experience.

Where it could improve

No authentication. For a starter that targets edge deployment, adding an edge-compatible auth solution (like Lucia with Turso sessions) would make this significantly more useful. As-is, you’re spending your first day adding auth.

SQLite’s limitations surface quickly. No native full-text search means you’re either pulling in a library or building search differently. Write throughput on a single primary is lower than Postgres. For read-heavy apps this is fine; for write-heavy apps, look elsewhere.