Loading documentation...
Preparing Ring Platform content
Concepts, value, and typical clone scenarios — less code.
Concepts, value, and typical clone scenarios — less code.
Preparing Ring Platform content
Preparing Ring Platform content
Preparing Ring Platform content
For executives: Ring is a white-label platform — one codebase, many branded deployments. Production rings run PostgreSQL-primary on Kubernetes with optional Firebase for push only, unified payments via PaymentConductor, and locale-aware routing without auth redirect loops.
Ring Platform v1.6.0 is a white-label Next.js application with a single DatabaseService contract, config-driven payments, and optional Web3/token layers per clone. This page is the architecture hub; each topic below has a dedicated deep-dive page.
| Dimension | Ring approach |
|---|---|
| Application | Next.js 16 App Router, React 19 Server Components, Tailwind 4 |
| Data (production default) | DB_BACKEND_MODE=k8s-postgres-fcm — Postgres + PostGIS, JSONB-first schema |
| Auth | Auth.js v5 — layout-level auth(), slim proxy.ts for locale only |
| Payments | PaymentConductor — WayForPay, Stripe, ledger + webhooks |
| Realtime | TunnelHub — native WSS (/api/tunnel/ws) on k8s; SSE/poll on Vercel; driven by RING_DEPLOY_TARGET |
| Files | Vercel Blob or clone-specific object storage |
| Deploy target | k3s (ringdom.org rings) — not Vercel-hosted Postgres |
| Extension | White-label env, portal config, per-clone token contracts |
DB_BACKEND_MODE matrix — Postgres vs Firebase vs Supabase, FCM-only Firebase, Tunnel vs SQL backend
JSONB-first schema, PostGIS, collections contract, migrations
Auth.js v5 providers, JWT sessions, Postgres adapter, role gates
Slim proxy, layout auth, localePrefix: as-needed, OAuth exclusions
Store checkout flows through PaymentConductor (fiat) or RING credit / on-chain subscription (Web3-enabled clones). Settlement, vendor referral commission, and platform token rewards are documented under PaymentConductor, Affiliate enablement, and ERP commissions.
Public pages use next-intl with shared label modules. News and docs content are per-locale files under docs/{locale}/. EN is canonical unless LOCALE-GAPS marks a condensed UK/RU summary.
Operators fork the Ring repo, set portal branding, choose database mode, and optionally enable token economics — see White-label quick start and Token economics.
v1.6.0 baseline: Postgres-primary + PaymentConductor + slim proxy + locale system. Start with Backend modes, then Environment configuration. Hub layout patterns: Documentation components.
DB_HYBRID_MODE ≠ DB_BACKEND_MODE. Use DB_BACKEND_MODE for all new deployments; see backend-modes page for legacy hybrid references.
For executives: Ring is a white-label platform — one codebase, many branded deployments. Production rings run PostgreSQL-primary on Kubernetes with optional Firebase for push only, unified payments via PaymentConductor, and locale-aware routing without auth redirect loops.
Ring Platform v1.6.0 is a white-label Next.js application with a single DatabaseService contract, config-driven payments, and optional Web3/token layers per clone. This page is the architecture hub; each topic below has a dedicated deep-dive page.
| Dimension | Ring approach |
|---|---|
| Application | Next.js 16 App Router, React 19 Server Components, Tailwind 4 |
| Data (production default) | DB_BACKEND_MODE=k8s-postgres-fcm — Postgres + PostGIS, JSONB-first schema |
| Auth | Auth.js v5 — layout-level auth(), slim proxy.ts for locale only |
| Payments | PaymentConductor — WayForPay, Stripe, ledger + webhooks |
| Realtime | TunnelHub — native WSS (/api/tunnel/ws) on k8s; SSE/poll on Vercel; driven by RING_DEPLOY_TARGET |
| Files | Vercel Blob or clone-specific object storage |
| Deploy target | k3s (ringdom.org rings) — not Vercel-hosted Postgres |
| Extension | White-label env, portal config, per-clone token contracts |
DB_BACKEND_MODE matrix — Postgres vs Firebase vs Supabase, FCM-only Firebase, Tunnel vs SQL backend
JSONB-first schema, PostGIS, collections contract, migrations
Auth.js v5 providers, JWT sessions, Postgres adapter, role gates
Slim proxy, layout auth, localePrefix: as-needed, OAuth exclusions
Store checkout flows through PaymentConductor (fiat) or RING credit / on-chain subscription (Web3-enabled clones). Settlement, vendor referral commission, and platform token rewards are documented under PaymentConductor, Affiliate enablement, and ERP commissions.
Public pages use next-intl with shared label modules. News and docs content are per-locale files under docs/{locale}/. EN is canonical unless LOCALE-GAPS marks a condensed UK/RU summary.
Operators fork the Ring repo, set portal branding, choose database mode, and optionally enable token economics — see White-label quick start and Token economics.
v1.6.0 baseline: Postgres-primary + PaymentConductor + slim proxy + locale system. Start with Backend modes, then Environment configuration. Hub layout patterns: Documentation components.
DB_HYBRID_MODE ≠ DB_BACKEND_MODE. Use DB_BACKEND_MODE for all new deployments; see backend-modes page for legacy hybrid references.
For executives: Ring is a white-label platform — one codebase, many branded deployments. Production rings run PostgreSQL-primary on Kubernetes with optional Firebase for push only, unified payments via PaymentConductor, and locale-aware routing without auth redirect loops.
Ring Platform v1.6.0 is a white-label Next.js application with a single DatabaseService contract, config-driven payments, and optional Web3/token layers per clone. This page is the architecture hub; each topic below has a dedicated deep-dive page.
| Dimension | Ring approach |
|---|---|
| Application | Next.js 16 App Router, React 19 Server Components, Tailwind 4 |
| Data (production default) | DB_BACKEND_MODE=k8s-postgres-fcm — Postgres + PostGIS, JSONB-first schema |
| Auth | Auth.js v5 — layout-level auth(), slim proxy.ts for locale only |
| Payments | PaymentConductor — WayForPay, Stripe, ledger + webhooks |
| Realtime | TunnelHub — native WSS (/api/tunnel/ws) on k8s; SSE/poll on Vercel; driven by RING_DEPLOY_TARGET |
| Files | Vercel Blob or clone-specific object storage |
| Deploy target | k3s (ringdom.org rings) — not Vercel-hosted Postgres |
| Extension | White-label env, portal config, per-clone token contracts |
DB_BACKEND_MODE matrix — Postgres vs Firebase vs Supabase, FCM-only Firebase, Tunnel vs SQL backend
JSONB-first schema, PostGIS, collections contract, migrations
Auth.js v5 providers, JWT sessions, Postgres adapter, role gates
Slim proxy, layout auth, localePrefix: as-needed, OAuth exclusions
Store checkout flows through PaymentConductor (fiat) or RING credit / on-chain subscription (Web3-enabled clones). Settlement, vendor referral commission, and platform token rewards are documented under PaymentConductor, Affiliate enablement, and ERP commissions.
Public pages use next-intl with shared label modules. News and docs content are per-locale files under docs/{locale}/. EN is canonical unless LOCALE-GAPS marks a condensed UK/RU summary.
Operators fork the Ring repo, set portal branding, choose database mode, and optionally enable token economics — see White-label quick start and Token economics.
v1.6.0 baseline: Postgres-primary + PaymentConductor + slim proxy + locale system. Start with Backend modes, then Environment configuration. Hub layout patterns: Documentation components.
DB_HYBRID_MODE ≠ DB_BACKEND_MODE. Use DB_BACKEND_MODE for all new deployments; see backend-modes page for legacy hybrid references.
Code landmarks
| Concern | Where to read |
|---|---|
| Locale proxy | proxy.ts, lib/proxy-intl.ts |
| Auth enforcement | (authenticated)/[locale]/layout.tsx, auth.config.ts |
| DB mode switch | lib/database/backend-mode-config.ts |
| Payments | features/store/services/payment-conductor* |
| Schema SSOT | data/schema.sql |
Component layering
Config-driven processors, payment_transactions ledger, unified webhooks
Code landmarks
| Concern | Where to read |
|---|---|
| Locale proxy | proxy.ts, lib/proxy-intl.ts |
| Auth enforcement | (authenticated)/[locale]/layout.tsx, auth.config.ts |
| DB mode switch | lib/database/backend-mode-config.ts |
| Payments | features/store/services/payment-conductor* |
| Schema SSOT | data/schema.sql |
Component layering
Config-driven processors, payment_transactions ledger, unified webhooks
Code landmarks
| Concern | Where to read |
|---|---|
| Locale proxy | proxy.ts, lib/proxy-intl.ts |
| Auth enforcement | (authenticated)/[locale]/layout.tsx, auth.config.ts |
| DB mode switch | lib/database/backend-mode-config.ts |
| Payments | features/store/services/payment-conductor* |
| Schema SSOT | data/schema.sql |
Component layering
Config-driven processors, payment_transactions ledger, unified webhooks