The Cathedral Framework

Architecture

Six structural pillars. Zero plugin dependencies. Built to outlast every platform trend.

UnifyOne's architecture is the Cathedral Framework: a multi-tenant commerce platform built in sequence — multi-tenant foundation, commerce infrastructure, payment orchestration, automation, analytics, and AI — where each of the six pillars is load-bearing and completed before the next is raised.

The Principle

Sequential Construction.
Permanent Foundation.

Medieval cathedral builders did not decorate before the foundation was sealed. They did not install stained glass before the vault was load-tested. They built in sequence — crypt, nave, transept, clerestory, spire — because each layer depended on the structural integrity of the one below it.

UnifyOne is built on the same principle. Multi-tenant isolation before commerce features. Commerce features before payment rails. Payment rails before automation. Automation before analytics. Analytics before AI. Each pillar is a load-bearing wall, not a decorative facade.

The result is a platform that does not collapse under production load, does not require manual intervention at scale, and does not accumulate technical debt that compounds into operational drag.

01
Foundation First
02
Structure Before Scale
03
Automation Before Traffic
04
Proven Before Promoted
Structural Elements

The Six Pillars

I
Schema-level isolation

Multi-Tenant Foundation

Every store is an isolated vault. Tenant data, billing, and access controls are structurally separated at the schema level — not by convention, not by middleware, not by row-level filtering alone. Each tenant is a load-bearing wall in the system's foundation.

Drizzle ORMPostgreSQL (Neon)JWT sessionsRole-based access control
II
Products, orders, inventory

Commerce Infrastructure

Products, orders, inventory, and fulfillment built as load-bearing walls. No plugin dependencies. No single points of failure. The catalog, order pipeline, and inventory system are first-class citizens of the schema — not afterthoughts bolted onto a CMS.

tRPC proceduresOptimistic UISupabase RealtimeWebhook events
III
Three rails, one roof

Payment Orchestration

Stripe, PayPal, and Shopify Checkout unified under one roof. Webhooks are verified, idempotent, and fire into your automation layer. Every payment event is logged, retried on failure, and linked to the order record — no orphaned transactions.

Stripe Checkout + PortalPayPal Smart ButtonsShopify redirectIdempotent webhooks
IV
Event-driven, not polled

Automation Nave

n8n workflows, Zapier hooks, and Mailchimp drip sequences triggered by real commerce events — not scheduled polling. An order placed fires into your automation layer within 200ms. A subscription renewed triggers your fulfillment workflow before the customer closes the tab.

n8n webhook triggersZapier hooksMailchimp dripEvent queue
V
Real-time illumination

Analytics Clerestory

Revenue, orders, and customer data illuminated in real time. Supabase Realtime keeps every panel current without a page refresh. The analytics layer reads from the same schema as the commerce layer — no ETL pipeline, no data warehouse lag, no stale numbers.

RechartsSupabase RealtimetRPC queriesBigQuery-ready
VI
Context-aware intelligence

AI Spire

An intelligent co-pilot built into every page. Context-aware insights drawn from your actual shift, earnings, and route data. The AI reads your operational data server-side and returns specific recommendations — not generic tips, not hallucinated metrics.

UnifyAI (invokeLLM)Context injectionConversation historyFloating widget
The Materials

Full Stack

Frontend
React 19
Vite 6
Tailwind CSS 4
shadcn/ui
Recharts
API Layer
tRPC 11
Superjson
Zod validation
Express 4
Database
Drizzle ORM
PostgreSQL (Neon)
Supabase Realtime
Schema migrations
Auth
OAuth
JWT sessions
Role-based access
Protected procedures
Payments
Stripe Checkout
PayPal SDK
Shopify redirect
Webhook verification
Automation
n8n webhooks
Zapier hooks
Resend email
Event queue
AI
Kai (LLM)
Context injection
Streaming responses
Conversation history
Infrastructure
Node.js 22
pnpm workspaces
GitHub Actions CI
Vitest 100 tests
Frequently Asked

Architecture Questions

What is the Cathedral Framework?

The Cathedral Framework is UnifyOne's architectural philosophy: build the platform sequentially, with each layer load-bearing before the next is raised. Multi-tenant isolation comes before commerce features, commerce before payment rails, payment before automation, automation before analytics, and analytics before AI. Every pillar is structural, not a decorative add-on.

What are the six structural pillars of UnifyOne?

The six pillars are the Multi-Tenant Foundation (schema-level store isolation), Commerce Infrastructure (products, orders, inventory), Payment Orchestration (Stripe, PayPal, and Shopify under one roof), the Automation Nave (event-driven n8n, Zapier, and Mailchimp workflows), the Analytics Clerestory (real-time dashboards via Supabase Realtime), and the AI Spire (a context-aware co-pilot built into every page).

How does UnifyOne isolate data between tenants?

Every store is an isolated vault. Tenant data, billing, and access controls are separated at the schema level and enforced with JWT sessions and role-based access control through Drizzle ORM on PostgreSQL — not by middleware or row-level filtering alone.

What technology stack is UnifyOne built on?

The frontend uses React 19, Vite, Tailwind CSS 4, and shadcn/ui. The API layer is tRPC 11 with Zod validation on Express. Data lives in PostgreSQL (Neon) via Drizzle ORM with Supabase Realtime for live updates. Payments run through Stripe, PayPal, and Shopify; automation through n8n and Zapier; and the platform ships on Node.js 22 with GitHub Actions CI.

Why build payment rails before automation?

Because automation triggers on real commerce events. If payment events are not verified, idempotent, and reliably logged first, every downstream workflow inherits that fragility. UnifyOne seals each load-bearing layer before adding the one above it, so the system does not collapse under production load or accumulate compounding technical debt.

Begin Construction

The Foundation Is Ready.
Your Nave Awaits.

Start with the Starter tier — free forever. Upgrade when your automation or commerce volume demands it.