Skip to main content
Platform Case StudyGlitch Studios + Glitch Tech

Glitch Platform

Shared Next.js platform behind Glitch Studios and Glitch Tech, with public product surfaces, routing, backend/admin architecture, media, auth, and proof-led portfolio evidence.

Two Products, One Platform

The lobby keeps the shared platform story intact while letting each product keep its own identity.

Creative Product

Glitch Studios

Music and video studio surfaces for services, booking, beats, media, and client-facing workflows.

Technology Product

Glitch Tech

Review, ranking, benchmark, comparison, and methodology surfaces sharing the same platform foundation.

Deep-dive coming next

Shared Backend Proof

Architecture evidence makes the platform work visible while private admin screens and unapproved media stay out of the public page.

2
Products
6
Route Groups
Next.js 16
Framework
Vercel
Deployment
01Evidence mapped

Shared App Shell

Glitch Studios and Glitch Tech stay distinct at the product layer while sharing one source-backed Next.js app foundation.

Evidence: Phase 02.1 source audit project summary and route inventory.

02Evidence mapped

Domain Routing

Host-aware routing separates Studios, Tech, review, and apparel behavior without turning the lobby into one blended product page.

Evidence: Phase 02.1 source audit middleware and host routing table.

03Evidence mapped

Backend/Admin Surface

Admin, auth, customer, commerce, content, booking, and tech-admin areas are represented as architecture proof, not private screenshots.

Evidence: Phase 02.1 source audit admin, auth, public, and API route tables.

04Evidence mapped

Data, Payments, Media

Database, checkout, email, media, audio, and content systems are shown as source-backed capability groups with conservative wording.

Evidence: Phase 02.1 content spec stack evidence, proof map, and media inventory rules.

Proof Pending Approval

Only public-safe architecture notes and sanitized screenshots appear here after source and media review.

Media gate

Sanitized screenshots can be added later only after the source and media review confirms that no private data, credentials, internal hostnames, customer records, or unfinished proof states are visible.

Preview unavailable. Open the approved live surface directly while iframe access is rechecked.