CASE STUDY · /website-builder-saas

Website Builder SaaS

A no-code platform with end-to-end domain automation — Studio editor, generic renderer, and per-tenant SSL provisioning.

ROLE

Solo Lead Engineer · Architecture + Implementation

TIMELINE

2024 – Present

TEAM

1 (solo, AI-augmented)

STATUS

Production · Multi-tenant

Overview

A fully no-code website builder where end users visually compose pages, publish, and host them on their own custom domains — comparable in scope to Webflow but delivered solo.

The product is built as two cooperating apps: a Studio editor with command-pattern undo/redo and live preview, and a separate Next.js renderer that serves each tenant's published site under their custom domain. Both apps share a single section registry, so editor and runtime never drift.

The problem

Off-the-shelf builders force a tradeoff between visual flexibility and production hosting. We needed both — drag-edit fidelity AND custom-domain hosting with SSL — without renting Webflow per tenant.

What I built

Studio editor: block-based composer, command-pattern undo/redo, live preview, theme abstraction
Generic Next.js renderer driven by JSON page config — same section components in editor and runtime
Domain lifecycle state machine: availability → purchase → Route53 records → SSL → deploy → active
Middleware-driven multi-tenancy: subdomain + custom-domain routing without per-route tenant checks
PayPal Subscriptions with idempotent webhook orchestration across plan transitions
Turborepo monorepo with 6 shared packages — UI library, sections, schemas, SSR-safe utils

Tech stack

Next.jsReactNode.jsTypeScriptMongoDB AtlasAWS Route53AWS SESTurborepoPayPal SubscriptionsDocker

Outcome

Production-live serving multiple tenants on custom domains. End-to-end uptime from edit → publish → live custom-domain in under 5 minutes. The shared component runtime means new section types ship without touching the renderer.

Want this in your stack? Let's talk.

Email Athar Back to all projects