Launch now. Not tomorrow.

It is built for founders, indie hackers, and small product teams that want a production-ready Go base without spending weeks wiring the same SaaS essentials again.

It is less suited for teams looking for a no-code builder or a heavy framework that hides the app structure behind magic.

Two things: the Go SaaS boilerplate (auth, billing, docs, blog, email, file uploads, analytics hooks, legal pages, Docker setup, migrations, layered architecture) and the premium block library (222+ production-ready templ blocks across 33 categories).

The detailed feature breakdown lives in the public docs under Introduction.

Pure copy-paste. Every block ships as a templ file inside the blocks folder in your customer repo. Paste the ones you want into your project, edit to taste. No package import, no version lock-in.

The web showcase at /blocks is just a live preview so you can see blocks rendered before you grab them. Login is optional, the actual code is already in the repo from day one.

Blocks only depend on the open-source templui components library, so they work in any templ project, not just the boilerplate.

Yes. The customer repo ships an auto-generated AGENTS.md index that Claude Code, Cursor, Aider, and Continue load automatically. Your agent knows every block, its category, and its purpose, so it can pick the right one without scanning the full library.

I do not try to prebuild your entire product domain. There is no visual builder, no generated admin, and no framework-specific runtime you are forced to keep forever.

You still build your own product logic, workflows, data model decisions, and customer experience on top.

It is opinionated in structure, not restrictive in ownership. The app uses clear handler, service, and repository layers so you can replace providers and modules without fighting hidden abstractions.

The public Architecture docs explain the project layout and extension model in detail.

Yes. SQLite is the default for fast local setup, and PostgreSQL is supported when you need a more traditional production database setup.

The database layer is designed to keep that switch practical instead of forcing a rewrite.

Both are first-class options, and both handle sales tax for you. Polar is the default. It's open source, developer first, and the simplest path to launch.

Stripe is supported with Managed Payments enabled out of the box, which makes Stripe the merchant of record and handles VAT, GST, and US sales tax across 80+ countries, the same compliance benefit as Polar. Pick Stripe if your team already lives in the Stripe ecosystem.

The public Subscriptions and Billing docs explain the tradeoff in detail.

You should treat goilerplate as a starting point you own, not as a framework that auto-updates underneath you. Review releases, compare changes, and pull over the updates you actually want.

The update workflow is documented publicly in Updating goilerplate.

They are real product features, not landing-page placeholders. Authentication includes magic links, passwords, onboarding, recovery flows, and account management. Security includes CSRF protection, CSP with nonces, rate limiting, and hardened defaults.

For exact details, use the public Authentication and Security docs as the source of truth.

Yes. The codebase is explicit, layered, and documented, which makes it much easier for AI tools to extend safely than ad hoc starter code.

The value is not that AI writes everything for you. The value is that AI starts from stable rails and recognizable patterns.

Your product-specific workflows, domain logic, data model decisions, onboarding copy, billing rules, and all the parts that make your app yours.

goilerplate removes plumbing work. It does not try to guess your business.

All licenses include private repository access. Team covers up to 5 developers, Enterprise up to 25. Team and Enterprise also include faster support than the Single tier.

Single includes community support. Team adds priority email support. Enterprise adds premium same-day support.

Web UI: share one team inbox like [email protected]. Magic-link logins go there, the whole team uses it.

Repo: fork the customer repo into your own GitHub org and have your devs work from your fork. Pull updates from upstream when a new release ships. Step-by-step git commands are in the repo README.

License caps are honor-system. Team up to 5 devs, Enterprise up to 25. No seat tracking, no per-user accounts to manage.

Yes. Drop your email in the signup just below and I'll send you a personal 15% off code, valid for 72 hours.

That's the only discount I run. No PPP pricing or recurring sales, just one fair price plus a welcome code for people who want a nudge to ship.

Yes. You can use goilerplate in unlimited projects, including client work. Your license tier only determines how many developers can use it.

Not allowed: public or open-source repositories, sharing the source code with non-license holders, or selling or redistributing goilerplate as templates, themes, or competing boilerplates. See the license page for details.

No refunds for digital products once access has been granted. If you hit a genuine issue, contact support and I'll help. Accidental duplicate payments are refunded immediately.