Replit Reference Architecture

Overview

Design a Replit App around five boundaries: editable project versus published release, public edge versus server, authenticated user versus tenant data, ephemeral runtime versus durable storage, and development configuration versus production Secrets. Keep provider-specific details behind small adapters and confirm time-sensitive platform controls in current official documentation.

Prerequisites

• A short workload profile: request-driven, continuously available, static, or scheduled.
• The app's public/private access policy, supported regions, cost owner, and availability target.
• A data classification and retention decision for relational records, files, logs, and backups.
• A chosen auth path: Replit Auth for Replit-account users or Clerk Auth for a branded tenant.
• Approval boundaries for publishing, production data changes, DNS, and access-control changes.

Architecture