I open-sourced my Go and Next B2B SaaS Starter (deploy anywhere, MIT)

The gap in what exists

Most SaaS starters lock users into specific platforms or frameworks, creating a need for a truly self-hostable, infrastructure-agnostic option with predictable costs.

Wedge to win

Target indie hackers and small B2B teams who prioritize full control over their infrastructure, predictable scaling costs, and a modern Go/Next.js stack, offering a more flexible alternative to platform-locked starters.

Reputation value (worth doing free for proof) — 70/100

Contributing to or creating a popular open-source SaaS starter would significantly boost credibility for future dev-tool products or consulting engagements with developer audiences.

Likely monetization

Premium version, paid support, or consulting services

Incumbents to beat

SaasRocknext-saas-stripe-starter

You are an expert full-stack developer specializing in Go, Next.js (App Router, React 19), Tailwind v4, Docker, and PostgreSQL. Your task is to build a production-grade B2B SaaS starter kit, similar to the `production-saas-starter` by moh_quz, but with a focus on ease of deployment to a generic Linux VPS using `docker-compose`. The core problem this solves is vendor lock-in and unpredictable costs of cloud-specific SaaS starters.

Here’s what to build:

1.  **Go Backend:** Develop a Go backend API service (using the `gin-gonic/gin` framework for REST endpoints) for core SaaS features: authentication (email/password, JWTs), user management, and a placeholder for basic 'item' CRUD operations (e.g., managing client projects). Use `gorm.io/driver/postgres` with `gorm.io/gorm` for ORM, connecting to a Neon Postgres database. Implement a modular monolith structure where auth, users, and items are distinct Go packages with explicit interfaces, but compile into a single binary. Ensure it's Dockerized with a minimal `Dockerfile`.
2.  **Next.js Frontend:** Create a Next.js 16 App Router frontend with React 19 and Tailwind v4. This frontend should consume the Go backend APIs for user registration, login, and displaying/managing the 'item' CRUD operations. Use `react-query` for data fetching and caching. Ensure it's Dockerized for static asset serving or SSR via `next start`.
3.  **Docker Compose:** Provide a `docker-compose.yml` file that orchestrates both the Go backend and Next.js frontend containers, along with a `postgres` service (for local development/testing) and `nginx` as a reverse proxy/load balancer.
4.  **Configuration:** Implement a robust configuration system (e.g., using environment variables) for database connections, JWT secrets, and API endpoints, making it easy to deploy to different environments.
5.  **Initial Schema:** Define a basic PostgreSQL schema for users and items.

**MVP Slice to Ship First:**

*   A fully functional Go backend with user registration, login, and JWT-based authentication.
*   A Next.js frontend with public landing page, registration form, login form, and a protected dashboard page that displays the logged-in user's email.
*   A working `docker-compose.yml` that brings up both services locally and connects them.

**Build and Verify Gate:**

*   All services start successfully via `docker-compose up`.
*   Users can register, log in, and access the protected dashboard.
*   Code is clean, well-commented, and adheres to Go and Next.js best practices.
*   The Docker images are optimized for size and build speed.