Blog
-
GoVueKit vs supastarter vs SaaS Pegasus vs ShipFast: an architecture comparison
Four SaaS boilerplates, four architectures: a Next.js starter on a BaaS, a Nuxt full-stack kit, a Django monolith, and a Go binary with a Vue app inside. What each one assumes about your team, your hosting and your month six — with the prices and links to check them.
-
Multi-tenant SaaS in Go with chi and sqlc: the whole tenancy layer
One column, one middleware, one convention, one test. How GoVueKit isolates organizations in a Go API: membership resolution in a chi route group, 404 for outsiders and 403 for insiders, sqlc queries that cannot forget the tenant, and the Playwright test that proves it against the production binary.
-
Stripe webhooks in Go: the complete idempotent handler, line by line
A production Stripe webhook in Go is two parts, not one: a handler that verifies the signature and stores the event in under a millisecond, and a worker that re-fetches the object by ID and applies the change in the same transaction that marks the event done. The code, the table, and the seven failure modes it closes.
-
Self-hosted SaaS boilerplate: what "self-hosted" has to mean, and a checklist
Most starter kits can technically run on your server and still depend on five external services to sign in, send an email or run a job. A precise definition of self-hosted, the questions that expose the difference, and how GoVueKit answers each one.
-
Embedding a Vue 3 app in a Go binary with go:embed — and keeping SEO without SSR
The complete mechanism behind a single-binary SaaS: vite build into go:embed, an SPA fallback that never serves the shell for a real 404, and build-time prerendering with Playwright that gives crawlers full HTML, canonical and hreflang — with the deployment origin substituted at startup.
-
Vue 3 SaaS starter kits in 2026: Nuxt kits, Vue on another backend, and one Go binary
The Vue side of the boilerplate market is thin and confusing: Nuxt full-stack kits, UI templates that are not kits, and Vue frontends bolted on Laravel, .NET or Go. What each family gives you, what it costs, and how to pick.
-
Go SaaS boilerplates in 2026: the honest list
Every Go starter kit that actually ships a SaaS foundation — auth, teams, billing, email, admin — compared by stack, licence and what it leaves you to write. Including the one we sell, held to the same bar.
-
Vibe coding on a boilerplate: stop your agent from rebuilding what it already has
Coding agents fail on boilerplates in one specific way: they reimplement what exists. The fix is not a smarter prompt — it is an enforced map. How GoVueKit does it with AGENTS.md and a conformance test.
-
Choosing a SaaS boilerplate in 2026: a comparison by architecture
The SaaS starter market splits into five families. What each one is genuinely good at, what it commits you to, and how to pick without regretting it in month six.
-
Go + Vue or a Next.js starter: what changes when the backend is a binary
A fair comparison between GoVueKit and the Next.js SaaS starters that dominate the market: deployment, cost at idle, type safety, ecosystem, and who should pick which.
-
The rented stack: what a BaaS-based starter really commits you to
Hosting platform, database service, auth vendor, queue, email: the bill nobody quotes when you pick a starter built on managed services — and when renting is still the right call.
-
21 questions to ask a SaaS boilerplate before you pay for it
A buyer's checklist that works on any starter kit: tenancy, webhooks, sessions, tests, licence and delivery. With how GoVueKit answers each one, so you can compare.
-
Your first hour with GoVueKit: clone, configure, ship
From an empty directory to a running multi-tenant SaaS with auth, teams and billing on your machine — then to a server. What each command does and why.
-
Adding your first business resource, from migration to e2e test
The full chain an org-scoped resource needs in a multi-tenant SaaS — migration, queries, handler, routes, store, view, tests — written by hand, one obvious file per layer.
-
Row-level multi-tenancy in Go: the rule, the middleware and the test that proves it
How to make cross-tenant leaks structurally impossible in a Go SaaS: one column, one middleware, 404 instead of 403, and the end-to-end test that keeps it true.
-
Idempotent billing webhooks: exactly-once fulfilment with Stripe
Why duplicate webhook deliveries double-charge or lose fulfilments, and the transaction pattern that makes replays a no-op — behind a provider seam, so you can plug your own.
-
Deploying a Go + Vue SaaS on one VPS with Traefik and Let's Encrypt
The whole production setup for a single-binary SaaS: DNS, Traefik with automatic HTTPS, the compose file, backups that actually restore, and zero-drama updates.
-
SQLite or PostgreSQL: one codebase, two engines, one env var
How to write a SaaS that runs unmodified on both engines, when SQLite is genuinely enough in production, and what it costs to keep the portability.
-
Keeping a SaaS in the EU: what self-hosting answers, and what it does not
Data residency, sub-processors, GDPR export and erasure, and enterprise security questionnaires — what a self-hosted Go binary settles, and what still needs paperwork.