Gvelte is a scaffolder. One command — gvelte create myapp — and you get a full-stack project: a SvelteKit 5 frontend running Svelte runes, and a compiled Go backend behind it. The two talk through a typed API client that Gvelte generates for you. No glue code. No boilerplate. Just a project that compiles and runs from the start.
The frontend runs on Vite with HMR. The backend runs under Air — Go’s hot-reload tool — so changes on either side reflect instantly without restarting anything manually. In production it compiles down to a single Go binary that embeds the entire SvelteKit build.
Here’s what it looks like in practice.
New project in seconds
gvelte create myapp drops you into a TUI wizard — built with Huh — where you pick your database (SQLite, Supabase/Postgres, MariaDB, or none), whether you want auth, and whether to include Shadcn + Tailwind. Answer the prompts and the scaffolder generates the project, runs go mod tidy, and writes your .env automatically.
Then ./gvelte install and ./gvelte run. That’s it. Air picks up the Go backend on :8080, Vite spins up the frontend on :5173, and the Vite proxy forwards /api and /auth requests to Go automatically.
Auth with Limen
Auth is handled by Limen — a composable Go auth library with a typed TypeScript client. When you opt in during setup, Gvelte mounts all auth endpoints at /auth/ and generates a LIMEN_SECRET straight into your .env.
On the backend, Limen exposes POST /auth/signup, POST /auth/signin, POST /auth/signout, and GET /auth/me out of the box. On the frontend, limen-auth/svelte gives you a reactive session store — auth.useSession() — so your UI reacts to sign-in state without any extra wiring.
Sign up, sign in, sign out — all working before you’ve written a single line of auth code.
Todos — your first API template
Every Gvelte project scaffolds a todos module: GET, POST, PUT, DELETE handlers on the Go side, all wired to the frontend through the generated typed client. It’s not a tutorial project — it’s a working reference you can gut and rebuild into your actual feature.
SQLite, zero config
Gvelte defaults to SQLite. Your database is already running when the project boots — no connection string, no separate service, no setup. The default tables are created on startup via CREATE TABLE IF NOT EXISTS, so the first ./gvelte run is all it takes.
New tables from Go structs
Adding a table means writing a Go struct and its DDL constant in a sub-package under backend/schema/, then registering it in schema.go. The next time the server starts — with Air picking it up automatically — the table exists. No migration runner, no ORM, no separate tooling. Your schema lives in your code and applies itself.
This is just the surface. More coming.
The beta drops Q1 2027 — and yes, it’ll be open source :)