ForgeHub: Build-in-Public Platform Case Study

ForgeHub is a social platform built for developers and builders to share work in progress rather than finished portfolios. It combines a dark, atmospheric design system with production-grade full-stack engineering: Next.js 16 and React 19 on the frontend, Express and PostgreSQL on the backend, real-time messaging via Socket.IO, and comprehensive security including split-token authentication and two-factor authentication on every sign-in method.

Service
Web Development
Industry
SaaS / Social Platform
Category
FULL-STACK DEVELOPMENT

Built with: Next.js, PostgreSQL, Socket.IO, TypeScript.

Overview

The Problem

  • Progress from builders is scattered across Twitter threads, GitHub READMEs, Discord servers, and LinkedIn posts, with no unified narrative of how a project actually developed
  • Traditional portfolios showcase only finished work, hiding the decisions, iterations, and dead ends that collaborators and hiring managers actually want to see
  • Finding collaborators relies on cold direct messages and chance encounters rather than visible, verifiable work and active projects
  • Mainstream social platforms prioritize polish and follower counts over shipping and progress, leaving early-stage builders invisible

The Solution

  • Built a project-first platform where every project has a defined stage, milestones, tech stack, visibility controls, and team roles, creating a single source of truth for work in progress
  • Designed a dedicated feed for work in progress with nine post types (updates, milestones, code snippets, polls, announcements) that let builders share progress naturally as it happens
  • Implemented real-time messaging with typing indicators, read receipts, reactions, and online presence, enabling synchronous collaboration without leaving the platform
  • Created communities organized around what members are building, with role-based moderation and discovery features that surface trending projects and builders

Solution Workflow

  1. Create
  2. Ship
  3. Discover
  4. Connect
  5. Collaborate

Full Technical Breakdown

Dark Design System with Token Architecture

Near-black canvas (#09090B) with layered surfaces, violet accent (#7C5CFF), and raised cards instead of glass morphism. Every colour, radius, and shadow defined as a single-source CSS token for consistency and theme portability.

Three.js Constellation Hero with Parallax

Animated network of connected nodes rendered at 18% opacity with GSAP ScrollTrigger parallax effects, aurora backdrop, film-grain texture, and vignette. Respects reduced-motion preferences.

Split-Token JWT Authentication

15-minute access token held in memory only, refresh token stored in httpOnly path-scoped cookies. Resistant to XSS attacks; sessions survive page reloads via silent refresh.

Multi-Step OAuth 2.0 / OpenID Connect Integration

Google sign-in implemented with full PKCE (S256), single-use state stored in Redis, and cryptographic nonce. ID tokens verified against Google's public keys using jose library, no SDK dependency.

Two-Factor Authentication (TOTP) on Every Sign-In Method

Secrets encrypted with AES-256-GCM, applied uniformly to password and Google OAuth flows. Prevents account takeover even if a single authentication method is compromised.

Next.js 16 with App Router and Turbopack

Server rendering for public pages, route groups separating marketing site, auth flows, and app dashboard. 26 routes, 138 React 19 components, Tailwind CSS 4 with design tokens.

Express 5 REST API with 135 Endpoints

Modular architecture across 11 modules: users, projects, posts, communities, messages, search, admin, and real-time. Full OpenAPI specification and Swagger UI documentation.

Prisma ORM with 49 Data Models

Type-safe queries, additive migrations for schema changes, and relational modeling of projects, milestones, teams, follows, and community memberships.

Socket.IO Real-Time Messaging with Redis Adapter

Messaging, typing indicators, read receipts, reactions, and online presence delivered across serverless instances. Redis adapter ensures no messages are lost between deployments.

PostgreSQL with Pooled and Direct Connections

Neon serverless Postgres in production; pooled connection for app requests, direct connection for migrations. Ensures connection exhaustion doesn't break schema updates.

Admin and Moderation Suite

User management dashboard, reports queue for handling community violations, platform-level analytics, and role-based access controls (platform admin, community owner, moderator).

Comprehensive Automated Testing

1,879 automated tests across 62 test files covering authentication, API endpoints, real-time messaging, and business logic. All passing, ensuring production reliability.

Results

Key Features

  • Project-First Discovery Model: Every project displays its current stage (idea through launched), milestone progress, tech stack, and team roles. A unified search covers builders, projects, communities, and posts with type filters and trending rankings.
  • Multi-Format Work-in-Progress Feed: Nine post types (text, image, video, code, markdown, poll, update, milestone, announcement) let builders share progress in whatever format fits. The feed offers latest, following, and trending views tailored to discovery and engagement.
  • Real-Time Messaging and Presence: Conversations include typing indicators, read receipts, reactions, and message editing. Online presence updates in real time and is stored in Redis with expiry, so users never appear online after leaving.
  • Role-Based Community Moderation: Communities are organized around what members build, with owner, admin, moderator, and member roles. Moderation scales with the community instead of concentrating on a single platform team.
  • Hardened Authentication and 2FA: Split-token JWT with access token in memory only, refresh token in httpOnly cookies. Two-factor authentication applies to every sign-in method (password and Google OAuth). Google sign-in uses full PKCE and nonce verification.
  • Comprehensive Admin and Moderation Suite: User management, a reports queue for handling violations, and platform-level analytics. All admin-only features with role-based access controls and audit trails.

Before

Before ForgeHub, builders progress was scattered across Twitter threads lost in timelines, sporadically updated GitHub READMEs, ephemeral Discord conversations, and LinkedIn posts constrained by platform conventions. Traditional portfolios showed finished work, omitting the decisions, dead ends, and iterations collaborators and hiring managers wanted to see. Finding collaborators relied on cold DMs or chance encounters, while mainstream platforms favored polish and follower counts, leaving early-stage builders invisible. No single place captured a project’s full history, stage by stage.

After

ForgeHub gives work in progress a unified home. Builders start projects with a single field, then add a stage, milestones, and a team as they build publicly. Updates, milestones, and announcements appear in a chronological feed followers see in real time. Collaborators discover projects through search or trending rankings and join teams directly. Profiles reveal how builders work and ship, beyond finished results. End-to-end security includes split-token authentication and two-factor authentication across every sign-in method, alongside real-time messaging backed by 1,879 automated tests. A distinctive dark interface and production-grade reliability earn technical users trust.

What This Proves

ForgeHub demonstrates production standards across every layer: authentication that closes real attack paths with split tokens, Argon2, PKCE, and 2FA; reliable real-time messaging across serverless instances via a Redis adapter; and a distinctive, intentional design system without unnecessary decoration. It includes 135 REST endpoints, 138 reusable React components, and a bento-style dashboard powered by real product data. Transparency is deliberate: sample data is labelled, statistics are never invented, and motion respects reduced-motion preferences. Built by technical people for technical people, ForgeHub reflects its users values without compromising reliability or trust.

Tech Stack

Backend

  • Node.js — Runtime with native ES modules and TypeScript throughout
  • Express — REST API framework with 135 endpoints across 11 modules
  • Prisma — ORM with type-safe queries, migrations, and 49 data models
  • Socket.IO — Real-time messaging, typing indicators, presence, and notifications

Frontend

  • Next.js — Full-stack framework with App Router, server rendering, and Turbopack bundler
  • React — Component architecture with 138 components across 26 routes
  • TailwindCSS — Utility-first styling with design tokens for colours, radii, and shadows
  • TanStack Query — Server state management with caching and automatic refetching
  • Zustand — Lightweight client state for UI toggles and form state

Security & Auth

  • Argon2 — Memory-hard password hashing resistant to GPU attacks
  • jose — JWT signing and verification, Google ID token validation
  • Helmet — Security headers (CSP, X-Frame-Options, etc.)

Email & Services

  • Resend — Transactional email for verification and password reset

Animation & Design

  • Framer Motion — Entrance reveals, focus-pull animations, and spring hover effects
  • GSAP ScrollTrigger — Scroll-linked parallax on hero constellation
  • Three.js — 3D constellation network scene with aurora and film-grain effects

Data & Infrastructure

  • PostgreSQL — Relational database on Neon serverless with pooled and direct connections
  • Redis — Rate limiting, brute-force tracking, OAuth state, 2FA challenges, presence, and Socket.IO delivery
  • Vercel — Hosting for frontend and Vercel Functions for the API with WebSocket support

Scalability & Flexibility

  • Design System Tokens: Every colour, radius, and shadow is a CSS token defined in one file. The dark theme is primary; a light-theme override point already exists. Components use tokens, not hex values, so palette changes never touch component code.
  • Project Model Expansion: Five project stages, milestone-based progress, six team roles, and three visibility levels. New fields ship as additive Prisma migrations without schema redesigns or data loss.
  • Authentication Provider Extensibility: Linked sign-in accounts are stored by provider and provider account ID. Adding GitHub or another provider requires one enum value and one protocol module, with no schema changes.
  • Email Provider Portability: A single switch in one file selects the email service. Resend is implemented; adding Postmark or SendGrid is one new case with no changes to services, routes, or call sites.
  • Pluggable AI Provider Architecture: A modular AI service with a local tag-suggestion provider and a disabled mode. Hosted models are ready to connect to project and post creation without modifying core logic.
  • Horizontal Real-Time Scaling: Socket.IO uses a Redis adapter to deliver events to every serverless instance. Presence lives in Redis with expiry times, not in server memory, so real-time features scale with instance count.
  • Serverless and Container Flexibility: The backend runs as a Vercel Function with WebSocket support or as a container from the included multi-stage Dockerfile. Local development uses Docker Compose, so environments match production.
  • Database Portability: Standard PostgreSQL through Prisma. Separate pooled and direct connection URLs allow migration between Neon, managed services, or self-hosting by configuration only.
  • Unified Search with Engine Portability: One search endpoint covers builders, projects, communities, and posts. The API surface remains unchanged if the backend moves to Elasticsearch or another search engine.
  • Two-Level Moderation: Platform admins handle a central reports queue. Community owners, admins, and moderators manage their own spaces independently, so moderation scales with community growth.
  • Notification Channel Expansion: Real-time notifications are delivered today. A notification preferences page already exists, ready to extend to email digests or push notifications without backend changes.
  • Configuration Safety at Startup: Production refuses to start with placeholder secrets, secrets shorter than 32 characters, non-HTTPS OAuth redirects, or disabled email. The frontend build fails if the API address is missing or points to localhost. Misconfiguration is caught at startup, not by users.

Live Preview

Live site: https://forgehub-gamma.vercel.app

About Nexoryn Nexoryn Services Nexoryn Portfolio Client Reviews Contact Nexoryn Privacy Policy Terms of Service Cookie Policy