This repository is a full-stack monorepo template for building SaaS applications using React 19, tRPC, and Cloudflare Workers. It features an edge-native architecture with three Workers (web router, app SPA, and API server) connected via service bindings. The template includes integrated authentication (Better Auth with email OTP, passkey, Google OAuth), multi-tenancy, Stripe billing, transactional emails (via Resend), file uploads to Cloudflare R2, and a Neon PostgreSQL database accessed through Drizzle ORM with Hyperdrive connection pooling. Key components include a reusable shadcn/ui component library, a typed WebSocket protocol package, and isolated database testing utilities.
This is a production-ready Node.js/Express web application boilerplate designed to jumpstart hackathon projects. The codebase implements a complete user authentication system supporting local email/password, OAuth 2.0/OAuth 1.0a (10+ providers including Google, Facebook, GitHub, Discord, Microsoft), WebAuthn passkeys, and two-factor authentication (TOTP + email). It includes session management with MongoDB, CSRF protection, rate limiting, and custom security measures like timing-safe token comparisons and IP-bound token consumption. Beyond auth, it ships working demos for ~20 third-party API integrations (Stripe, Twilio, GitHub, NYT, Wikipedia, etc.) and AI features powered by LangChain and Groq, including a ReAct agent with SSE streaming, a RAG pipeline with vector search, and LLM-based classification/vision. The repository also provides a sophisticated Playwright-based e2e testing framework using nock-recorded HTTP fixtures, enabling deterministic offline tests without live API keys. All features are organized as deletable modules with a removal checklist to facilitate trimming for production use.
ReNative (rnv) is a cross-platform development CLI tool and framework that enables building applications for mobile (iOS, Android), web, TV (Tizen, webOS, Fire TV, Android TV, tvOS), desktop (macOS, Windows, Linux, Electron), wearables, and consoles from a single codebase. The system uses a monorepo architecture with modular packages: a core library (`@rnv/core`) providing configuration merging, plugin management, template injection, and task orchestration; platform-specific engines (`@rnv/engine-rn`, `@rnv/engine-rn-electron`, `@rnv/engine-rn-next`, etc.) that define build logic and native project templates; SDK packages (`@rnv/sdk-android`, `@rnv/sdk-apple`, `@rnv/sdk-tizen`, etc.) for platform-specific tooling like device management and code generation; and a CLI entry point (`rnv`) that dispatches commands to registered tasks. The primary data flow involves reading hierarchical configuration files (`renative.json`, `appConfigs/`), merging them with plugin definitions and engine defaults, injecting placeholders into platform templates (e.g., AndroidManifest.xml, Xcode project files, Webpack configs), and then invoking native build tools (Gradle, Xcode, Webpack, etc.) to produce deployable artifacts. External dependencies include React Native, Electron, Next.js, Webpack, and platform SDKs (Android SDK, Xcode, Tizen SDK, webOS SDK). The framework also includes a telemetry module, Docker integration, and a build hooks system for custom pre/post-publish scripts.
Materio is a free admin dashboard starter template built on Next.js 14 App Router, MUI v5, and Tailwind CSS, published by ThemeSelection. It ships as two parallel, functionally identical codebases: javascript-version/ and typescript-version/. Everything in the repo is static UI - hardcoded demo data, mock ApexCharts, placeholder auth forms - there is no API layer, database, or authentication logic. Its job is to be a polished starting point for admin applications, and it executes that role well: an extensive per-component MUI theme override system, a custom collapsible vertical menu subsystem, and a cookie-persisted settings context for dark/light mode. Architecturally it follows Next.js App Router conventions: root layout (app/layout.jsx), a dashboard layout that wraps the VerticalLayout shell (navigation, navbar, footer), and a blank layout for login/register/error pages. The most interesting engineering lives in src/@menu (a self-contained vertical navigation layer with context-driven collapse/expand and breakpoint behavior), src/@core/theme (dozens of isolated MUI component overrides), and a few genuinely reusable React hooks (useObjectCookie, useImageVariant). All dashboard data is fabricated; adopters must wire real data and backend logic themselves. The template is actively maintained (last commit March 2026, one open issue, automated issue triage workflows). Drift risks are version pinning to Next.js 14 / MUI v5.15 and the maintenance cost of keeping JS and TS variants in sync.
This repository serves as the landing page for the Nuxt web framework, providing a minimal but polished interface to kickstart Nuxt projects. The core functionality is a gallery of starter templates—each pointing to a GitHub repository branch—with one-click redirections to CodeSandbox, StackBlitz, or a local `npm create nuxt@latest` command. The application is built with Nuxt 4 and leverages server routes for API lookups (slug-based) and redirects, client-side data fetching via `useFetch`, and a performant static generation pipeline. It also includes a custom `style-inlining` module that purges unused CSS and inlines critical styles during prerendering, and a `purge-comments` Vite plugin that strips HTML comments from Vue templates at build time. The UI is styled with Tailwind CSS and Nuxt UI components, and the entire site is designed to be lightweight (budgeted at 270 KB total). It is a genuinely useful tool for the Nuxt community, acting as both a promotional site and a practical starter launcher.
This repository is an Eleventy (11ty) starter template for building a digital garden (mind garden) website. It generates a static site from Markdown notes with two key features: wiki-style double-bracket links ([[link]]) that auto-resolve to internal notes, and automatic backlinks display with hovercard previews. The architecture is a standard Eleventy static site configuration: source files (Markdown notes, layouts, includes, data) are processed by Eleventy with custom markdown-it plugins and the eleventy-plugin-backlinks plugin to produce a static HTML site. The external dependencies are limited to Eleventy, markdown-it (with footnote and attribute plugins), eleventy-plugin-backlinks, and a few dev dependencies for formatting. The code is well-structured, uses ES modules, and demonstrates a clean integration of custom markdown syntax for wiki links via markdown-it's linkify extension. However, as a starter template, most code is configuration and templating specific to Eleventy, with no truly isolated, reusable component that can be extracted without the Eleventy framework. The maintenance appears active with recent commits, issue templates, and dependency management via Renovate.
This is a production-ready, multi-tenant SaaS starter kit built with Next.js (Pages Router), NextAuth.js, Prisma ORM (PostgreSQL), and Tailwind CSS. The system provides comprehensive enterprise features: email/password authentication, magic link, OAuth (Google, GitHub), SAML/SSO via BoxyHQ Jackson, directory sync (SCIM), webhooks via Svix, audit logging via Retraced, Stripe billing, API keys, and team-based role management (RBAC). The architecture follows a monolith with API routes under /pages/api, middleware for session validation, and a component-based frontend. Data flows center around team creation and management: users register (or SSO), create or join teams via invitations, then configure team-level SSO, directory sync, webhooks, billing, and API keys. The codebase demonstrates solid engineering practices with Zod validation, reusable UI components, and a clear separation of concerns, but shows signs of feature creep and some legacy patterns (e.g., Pages Router). It is well-suited for developers building a SaaS platform who need a jump-start on authentication, team management, and enterprise integrations.
This is a full-stack web application starter kit combining Angular (frontend) and Spring Boot (backend) with JWT-based authentication. The system provides user registration, login, role-based access control (USER/ADMIN), and protected API endpoints. The frontend communicates with the backend via RESTful APIs, with authentication handled through JWT tokens stored in cookies. The architecture follows a standard client-server pattern with clear separation of concerns: Angular handles UI presentation and user interactions, while Spring Boot manages business logic, data persistence, and security. Key features include route guards for client-side protection, custom JWT filters for server-side authentication, and centralized service layers for API communication.
This repository provides a minimal, opinionated starter template for building React applications with Vite. It includes a pre-configured setup with TypeScript, Tailwind CSS v4, Biome for linting and formatting, Lefthook for git hooks, Turbo for task orchestration, and Renovate for automated dependency updates. The actual application code is trivial: a single-page app shell with lazy-loaded routes for an index page and a 404 page, wrapped in React Router's BrowserRouter. The template prioritizes modern tooling and developer experience but does not implement any business logic, custom components, or complex architecture. It is intended to be cloned and used as a starting point for new React projects, rather than as a standalone application.
This repository is a starter template for creating documentation websites using the Hugo Blox framework. It provides a pre-configured Hugo site with example content, navigation, and configuration files for a documentation theme. The actual functionality (rendering, shortcodes, search) is delegated to imported Hugo modules from the HugoBlox/kit ecosystem. The repo contains no application logic or data pipelines; it is purely a content and configuration scaffold intended to be cloned and customized. The architecture is a static site generator with Tailwind CSS, Pagefind search, and GitHub Actions CI/CD. Key entry points are the hugo.yaml, params.yaml, and menus.yaml configuration files, and the content/Markdown files. External dependencies include Hugo, the HugoBlox modules, Node.js (for Tailwind and Pagefind), and a hosting provider.
This repository is a curated list of open-source SaaS boilerplates and starter templates. It is a static, community-driven directory (an 'awesome list') that links to external projects across various tech stacks (React/Next.js, Node.js, Django, Flutter, etc.). The repository contains no executable code, API endpoints, or data pipelines—it functions solely as a discoverability resource for developers seeking pre-built SaaS foundations. The architecture is a single README file with a table of contents and categorized sections. There are no software artifacts to analyze; the value lies in the curation and presentation of external projects, not in any implemented system.
AgentKit is a full-stack framework for building constrained, reliable LLM agents, developed by BCG X and now deprecated. The codebase consists of a FastAPI backend (Python 3.10) that orchestrates LangChain-based agents through a meta-agent and a simple router, executing tools like SQL queries, PDF question-answering, visualizations, image generation, and summarization. The Next.js 14 frontend provides a conversational chat interface with streaming responses, tool action rendering, and configurable UI components. The application is Dockerized with PostgreSQL, Redis, Minio, and Caddy, and supports optional features such as user authentication (NextAuth), feedback collection (LangSmith), and Celery-based background tasks. The architecture is monolithic in code but service-oriented in deployment, with configuration-driven agent behavior via YAML files. While the codebase demonstrates solid engineering patterns (e.g., streaming callbacks, base tool classes, state management), it is explicitly deprecated, relies on outdated LangChain imports and API versions, and requires significant maintenance to be viable for new projects. The repository serves as a reference for building constrained agents but is not recommended for production use without substantial updates.