Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)

    Documentation

    Concepts, value, and typical clone scenarios — less code.

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    First Success Validation
    Next Steps
    Features
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    SubscriptionConductor
    PaymentConductor
    Ring Oracle
    Payments Overview
    Public Pools & DAO Jars
    WayForPay Payment Integration
    Wallet & Credit System
    WalletConductor
    Affiliate & Referral Enablement
    Referral Codes (Refcodes)
    NFT Exhibition Marketplace
    Solana NFT Gates
    Token Staking System
    Owner Project Lab
    Entities
    Opportunities
    Real-Time Messaging
    Ring Tasks
    WebRTC Calls & STUNner TURN
    Peer Games
    News Module
    Member Blogs
    Public Profile Pages
    Profile Account Widgets
    Ring File Cabinet
    Username Reservation System
    Scientific Editor
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Email AI-CRM
    Ring Mailer & RingdomX Mail
    Tunnel Protocol
    VideoConductor
    MediaConductor
    Generative Gallery
    Authentication
    Security & Compliance
    Admin console
    Admin Wiki
    Manage via Telegram
    Locale System
    Mobile Experience
    Performance Optimization Patterns
    Examples
    Quick Start
    Basic Setup
    White Label
    Custom Branding
    Web3 Integration
    Real World
    Advanced Features
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Vertical Presets (SSOT)
    Ringization playbook
    Branding
    Themes
    Features
    Localization
    Token Economics Setup
    Payment Gateway Integration
    Reference Ring deployments
    Project configuration
    Public environment variables
    Order Lab secrets
    WalletConnect Project ID (Reown Cloud)
    Supported services
    NODUS wiki (project knowledge)
    Configuration playbook
    Web3
    Token launch jurisdictions
    Wallet
    Wallet Security Tips
    Integrations
    Ethereum wallets (Wagmi v3)
    RingFileBase (object storage API)
    Ring CDN (RingFileBase edge)
    Deployment
    Self-hosted deployment
    Vercel Deployment
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Architecture
    Data Model
    Security
    Real Time
    Discovery Mutation Sync
    PaymentConductor architecture
    WalletConductor architecture
    Backend Services
    Firebase Integration
    Development
    Ring MCP Server

    Quick entry (CTOs · auditors · agents)

    Welcome — mission & audiences
    Quick Reference
    Getting started
    Architecture & Auth.js
    Backend modes & databases (DB_BACKEND_MODE)
    Self-hosted
    Ring MCP Tools
    Ring MCP Server
    Token economics
    Token launch jurisdictions
    Deploy (Docker · k8s)
    Security & compliance reads
    ringdom.org — LegioX homebase
    Source — MIT license (GitHub)
    Ring Platform Logo

    Loading documentation...

    Preparing Ring Platform content

    Ring Platform Logo

    Loading documentation...

    Preparing Ring Platform content

    Ring Platform Logo

    Loading documentation...

    Preparing Ring Platform content

    Customization Guide

    Time estimate: 1–4 hours for branding + feature toggles. Prerequisites: Quick Start completed locally.

    Ring clones share one codebase (ring-platform.org). Customization is config-first (ring-config.json presets, env, locales). Vertical niches ship as in-repo presets — do not fork niche TypeScript into the clone. See Vertical presets.

    Customization map

    Where white-label settings live

    1. ring-config.json (install-time SSOT)

    Created by ./install.sh or copied from ring-config.template.json. Merged with the template at runtime in lib/ring-config-core.ts (also exposed server-side via lib/ring-config.ts).

    Clone identity

    json
    
    {
      "clone": {
        "name": "my-ring-clone",
        "displayName": "My Platform",
        "description": "Regional opportunities network",
        "organization": "Your Org",
        "contactEmail": "contact@example.com"
      },
      "domains": {
        "production": "https://example.com",
        "development": "http://localhost:3000"
      },
      "platform": {
        "baseUrl": "https://example.com"
      }
    }

    Used for SEO (lib/seo-metadata.ts), JSON-LD, and getSiteBaseUrl().

    Vertical presets (preferred over code forks)

    json
    
    {
      "entities": { "preset": "platform" },
      "productFields": { "preset": "platform" },
      "productBadges": { "preset": "platform" }
    }

    Agricultural / GreenFood-style clones use "agricultural" for all three. Full registry: Vertical presets.

    Branding block

    branding.logo, branding.colors, branding.darkColors, branding.fonts in the template — place assets under public/images/ (see template paths).

    Optional env overrides (lib/site-branding.ts):

    Feature flags

    Toggle modules without deleting code:

    Server checks: isFeatureEnabled() in lib/ring-config-core.ts and whitelabel/features.ts. Disable routes in navigation when turning features off.

    Matcher defaults

    Install-time AI matcher thresholds live under matcher in ring-config.json (getMatcherInstallDefaults()). Runtime DB overlay may apply for production rings — see AI customization.

    Sidebar and navigation metadata

    sidebar and navigation.links in ring-config.json feed public instance config (getPublicInstanceConfig()). Primary chrome is implemented in:

    • components/navigation/navigation.tsx
    • components/navigation/desktop-sidebar.tsx
    • components/navigation/bottom-navigation.tsx

    For a custom desktop nav variant, follow Whitelabel navigation.

    2. Home page (replaces deprecated portal)

    LayerFileRole
    Routeapp/(public)/[locale]/page.tsxStatic metadata + renders HomeWrapper
    Layout shellcomponents/wrappers/home-wrapper.tsxResponsive grid, right rail, session-aware chrome
    Hero bodycomponents/common/pages/home.tsxDaVinci hero, CTAs, feature rotator
    Copylocales/{locale}/pages.json → homePrimary hero title, subtitle, features[], right-rail strings

    Do not configure a separate “portal” app or lib/portal-config.ts — that path is deprecated. Marketing home is always HomeWrapper on /.

    Customize hero copy (fastest path)

    Edit locales/en/pages.json (mirror uk, ru):

    HomeContent reads via useTranslations('pages.home').

    Customize home layout

    • Right rail (OSS marketplace / Ringdom CTAs): HomeRightRail inside home-wrapper.tsx, strings in pages.home.rightRail
    • Deeper UX — fork home-wrapper.tsx or home.tsx; add paths to .reggie-propagate-exclude.json

    ring-config.json hero block remains for clones that read it elsewhere; the flagship home hero is i18n-driven as above.

    3. Internationalization

    • SSOT: lib/locale-config.ts
    • Messages: locales/{locale}/**/*.json, loaded by lib/i18n.ts
    • Routing: @/i18n/routing — never hand-strip locale prefixes in client code

    Full guide: Localization.

    Protected locale files (overlay deltas) are listed in .reggie-propagate-exclude.json — typically locales/*/config.json, vendor.json only.

    4. Theme and visual polish

    Ring uses Tailwind 4 with CSS variables for light/dark (next-themes).

    1. Set branding.colors / darkColors in ring-config.json (template documents keys aligned to shadcn tokens)
    2. Replace public/favicon.ico, public/images/logo-*.svg, apple-touch-icon.png
    3. Theme default: ring-config.json → "theme": { "default": "system" }

    Avoid editing generated design tokens in unrelated clones — prefer ring-config + env brand overrides.

    5. Payments and store (clone-level)

    • PaymentConductor processors: env vars — Payment integration
    • Store currency / tax: features.store in ring-config.json
    • WayForPay / Stripe: never commit secrets; use k8s secrets in production

    6. Web3 and tokens (optional)

    Contract addresses and treasury: env + Token economics. Set tokens.native in ring-config.json for display metadata.

    7. Reggie propagation — thin overlay only

    Source of truth: always propagate from ring-platform.org. Exclude protects brand/locale overlay — not vertical code.

    File: .reggie-propagate-exclude.json at repo root. Do not exclude niche fields, entity catalogs, or home-wrapper forks — select presets instead. Details: Vertical presets.

    8. Verification checklist

    1. 1

      Branding — logo, favicon, NEXT_PUBLIC_BRAND_NAME, OG image on share previews

    2. 2

      Home — / hero matches pages.home in each supported locale

    3. 3

      Presets — entities / productFields / productBadges match the vertical

    4. 4

      Features — disabled modules 404 or hide from nav; no dead sidebar links

    5. 5

      Auth — login/logout, role-gated admin at /admin

    6. 6

      Build — npm run build clean; smoke tests if payments enabled

    Next steps

    Vertical presets

    Ship niches in platform; select via ring-config

    Database selection

    DB_BACKEND_MODE and migration strategy

    Payment integration

    WayForPay, Stripe, webhooks

    AI customization

    Matcher tuning and agent costs

    Fork discipline: Config + locales first, component forks second, exclusions before propagation. Your clone should upgrade without merge wars.

    Customization Guide

    Time estimate: 1–4 hours for branding + feature toggles. Prerequisites: Quick Start completed locally.

    Ring clones share one codebase (ring-platform.org). Customization is config-first (ring-config.json presets, env, locales). Vertical niches ship as in-repo presets — do not fork niche TypeScript into the clone. See Vertical presets.

    Customization map

    Where white-label settings live

    1. ring-config.json (install-time SSOT)

    Created by ./install.sh or copied from ring-config.template.json. Merged with the template at runtime in lib/ring-config-core.ts (also exposed server-side via lib/ring-config.ts).

    Clone identity

    json
    
    {
      "clone": {
        "name": "my-ring-clone",
        "displayName": "My Platform",
        "description": "Regional opportunities network",
        "organization": "Your Org",
        "contactEmail": "contact@example.com"
      },
      "domains": {
        "production": "https://example.com",
        "development": "http://localhost:3000"
      },
      "platform": {
        "baseUrl": "https://example.com"
      }
    }

    Used for SEO (lib/seo-metadata.ts), JSON-LD, and getSiteBaseUrl().

    Vertical presets (preferred over code forks)

    json
    
    {
      "entities": { "preset": "platform" },
      "productFields": { "preset": "platform" },
      "productBadges": { "preset": "platform" }
    }

    Agricultural / GreenFood-style clones use "agricultural" for all three. Full registry: Vertical presets.

    Branding block

    branding.logo, branding.colors, branding.darkColors, branding.fonts in the template — place assets under public/images/ (see template paths).

    Optional env overrides (lib/site-branding.ts):

    Feature flags

    Toggle modules without deleting code:

    Server checks: isFeatureEnabled() in lib/ring-config-core.ts and whitelabel/features.ts. Disable routes in navigation when turning features off.

    Matcher defaults

    Install-time AI matcher thresholds live under matcher in ring-config.json (getMatcherInstallDefaults()). Runtime DB overlay may apply for production rings — see AI customization.

    Sidebar and navigation metadata

    sidebar and navigation.links in ring-config.json feed public instance config (getPublicInstanceConfig()). Primary chrome is implemented in:

    • components/navigation/navigation.tsx
    • components/navigation/desktop-sidebar.tsx
    • components/navigation/bottom-navigation.tsx

    For a custom desktop nav variant, follow Whitelabel navigation.

    2. Home page (replaces deprecated portal)

    LayerFileRole
    Routeapp/(public)/[locale]/page.tsxStatic metadata + renders HomeWrapper
    Layout shellcomponents/wrappers/home-wrapper.tsxResponsive grid, right rail, session-aware chrome
    Hero bodycomponents/common/pages/home.tsxDaVinci hero, CTAs, feature rotator
    Copylocales/{locale}/pages.json → homePrimary hero title, subtitle, features[], right-rail strings

    Do not configure a separate “portal” app or lib/portal-config.ts — that path is deprecated. Marketing home is always HomeWrapper on /.

    Customize hero copy (fastest path)

    Edit locales/en/pages.json (mirror uk, ru):

    HomeContent reads via useTranslations('pages.home').

    Customize home layout

    • Right rail (OSS marketplace / Ringdom CTAs): HomeRightRail inside home-wrapper.tsx, strings in pages.home.rightRail
    • Deeper UX — fork home-wrapper.tsx or home.tsx; add paths to .reggie-propagate-exclude.json

    ring-config.json hero block remains for clones that read it elsewhere; the flagship home hero is i18n-driven as above.

    3. Internationalization

    • SSOT: lib/locale-config.ts
    • Messages: locales/{locale}/**/*.json, loaded by lib/i18n.ts
    • Routing: @/i18n/routing — never hand-strip locale prefixes in client code

    Full guide: Localization.

    Protected locale files (overlay deltas) are listed in .reggie-propagate-exclude.json — typically locales/*/config.json, vendor.json only.

    4. Theme and visual polish

    Ring uses Tailwind 4 with CSS variables for light/dark (next-themes).

    1. Set branding.colors / darkColors in ring-config.json (template documents keys aligned to shadcn tokens)
    2. Replace public/favicon.ico, public/images/logo-*.svg, apple-touch-icon.png
    3. Theme default: ring-config.json → "theme": { "default": "system" }

    Avoid editing generated design tokens in unrelated clones — prefer ring-config + env brand overrides.

    5. Payments and store (clone-level)

    • PaymentConductor processors: env vars — Payment integration
    • Store currency / tax: features.store in ring-config.json
    • WayForPay / Stripe: never commit secrets; use k8s secrets in production

    6. Web3 and tokens (optional)

    Contract addresses and treasury: env + Token economics. Set tokens.native in ring-config.json for display metadata.

    7. Reggie propagation — thin overlay only

    Source of truth: always propagate from ring-platform.org. Exclude protects brand/locale overlay — not vertical code.

    File: .reggie-propagate-exclude.json at repo root. Do not exclude niche fields, entity catalogs, or home-wrapper forks — select presets instead. Details: Vertical presets.

    8. Verification checklist

    1. 1

      Branding — logo, favicon, NEXT_PUBLIC_BRAND_NAME, OG image on share previews

    2. 2

      Home — / hero matches pages.home in each supported locale

    3. 3

      Presets — entities / productFields / productBadges match the vertical

    4. 4

      Features — disabled modules 404 or hide from nav; no dead sidebar links

    5. 5

      Auth — login/logout, role-gated admin at /admin

    6. 6

      Build — npm run build clean; smoke tests if payments enabled

    Next steps

    Vertical presets

    Ship niches in platform; select via ring-config

    Database selection

    DB_BACKEND_MODE and migration strategy

    Payment integration

    WayForPay, Stripe, webhooks

    AI customization

    Matcher tuning and agent costs

    Fork discipline: Config + locales first, component forks second, exclusions before propagation. Your clone should upgrade without merge wars.

    Customization Guide

    Time estimate: 1–4 hours for branding + feature toggles. Prerequisites: Quick Start completed locally.

    Ring clones share one codebase (ring-platform.org). Customization is config-first (ring-config.json presets, env, locales). Vertical niches ship as in-repo presets — do not fork niche TypeScript into the clone. See Vertical presets.

    Customization map

    Where white-label settings live

    1. ring-config.json (install-time SSOT)

    Created by ./install.sh or copied from ring-config.template.json. Merged with the template at runtime in lib/ring-config-core.ts (also exposed server-side via lib/ring-config.ts).

    Clone identity

    json
    
    {
      "clone": {
        "name": "my-ring-clone",
        "displayName": "My Platform",
        "description": "Regional opportunities network",
        "organization": "Your Org",
        "contactEmail": "contact@example.com"
      },
      "domains": {
        "production": "https://example.com",
        "development": "http://localhost:3000"
      },
      "platform": {
        "baseUrl": "https://example.com"
      }
    }

    Used for SEO (lib/seo-metadata.ts), JSON-LD, and getSiteBaseUrl().

    Vertical presets (preferred over code forks)

    json
    
    {
      "entities": { "preset": "platform" },
      "productFields": { "preset": "platform" },
      "productBadges": { "preset": "platform" }
    }

    Agricultural / GreenFood-style clones use "agricultural" for all three. Full registry: Vertical presets.

    Branding block

    branding.logo, branding.colors, branding.darkColors, branding.fonts in the template — place assets under public/images/ (see template paths).

    Optional env overrides (lib/site-branding.ts):

    Feature flags

    Toggle modules without deleting code:

    Server checks: isFeatureEnabled() in lib/ring-config-core.ts and whitelabel/features.ts. Disable routes in navigation when turning features off.

    Matcher defaults

    Install-time AI matcher thresholds live under matcher in ring-config.json (getMatcherInstallDefaults()). Runtime DB overlay may apply for production rings — see AI customization.

    Sidebar and navigation metadata

    sidebar and navigation.links in ring-config.json feed public instance config (getPublicInstanceConfig()). Primary chrome is implemented in:

    • components/navigation/navigation.tsx
    • components/navigation/desktop-sidebar.tsx
    • components/navigation/bottom-navigation.tsx

    For a custom desktop nav variant, follow Whitelabel navigation.

    2. Home page (replaces deprecated portal)

    LayerFileRole
    Routeapp/(public)/[locale]/page.tsxStatic metadata + renders HomeWrapper
    Layout shellcomponents/wrappers/home-wrapper.tsxResponsive grid, right rail, session-aware chrome
    Hero bodycomponents/common/pages/home.tsxDaVinci hero, CTAs, feature rotator
    Copylocales/{locale}/pages.json → homePrimary hero title, subtitle, features[], right-rail strings

    Do not configure a separate “portal” app or lib/portal-config.ts — that path is deprecated. Marketing home is always HomeWrapper on /.

    Customize hero copy (fastest path)

    Edit locales/en/pages.json (mirror uk, ru):

    HomeContent reads via useTranslations('pages.home').

    Customize home layout

    • Right rail (OSS marketplace / Ringdom CTAs): HomeRightRail inside home-wrapper.tsx, strings in pages.home.rightRail
    • Deeper UX — fork home-wrapper.tsx or home.tsx; add paths to .reggie-propagate-exclude.json

    ring-config.json hero block remains for clones that read it elsewhere; the flagship home hero is i18n-driven as above.

    3. Internationalization

    • SSOT: lib/locale-config.ts
    • Messages: locales/{locale}/**/*.json, loaded by lib/i18n.ts
    • Routing: @/i18n/routing — never hand-strip locale prefixes in client code

    Full guide: Localization.

    Protected locale files (overlay deltas) are listed in .reggie-propagate-exclude.json — typically locales/*/config.json, vendor.json only.

    4. Theme and visual polish

    Ring uses Tailwind 4 with CSS variables for light/dark (next-themes).

    1. Set branding.colors / darkColors in ring-config.json (template documents keys aligned to shadcn tokens)
    2. Replace public/favicon.ico, public/images/logo-*.svg, apple-touch-icon.png
    3. Theme default: ring-config.json → "theme": { "default": "system" }

    Avoid editing generated design tokens in unrelated clones — prefer ring-config + env brand overrides.

    5. Payments and store (clone-level)

    • PaymentConductor processors: env vars — Payment integration
    • Store currency / tax: features.store in ring-config.json
    • WayForPay / Stripe: never commit secrets; use k8s secrets in production

    6. Web3 and tokens (optional)

    Contract addresses and treasury: env + Token economics. Set tokens.native in ring-config.json for display metadata.

    7. Reggie propagation — thin overlay only

    Source of truth: always propagate from ring-platform.org. Exclude protects brand/locale overlay — not vertical code.

    File: .reggie-propagate-exclude.json at repo root. Do not exclude niche fields, entity catalogs, or home-wrapper forks — select presets instead. Details: Vertical presets.

    8. Verification checklist

    1. 1

      Branding — logo, favicon, NEXT_PUBLIC_BRAND_NAME, OG image on share previews

    2. 2

      Home — / hero matches pages.home in each supported locale

    3. 3

      Presets — entities / productFields / productBadges match the vertical

    4. 4

      Features — disabled modules 404 or hide from nav; no dead sidebar links

    5. 5

      Auth — login/logout, role-gated admin at /admin

    6. 6

      Build — npm run build clean; smoke tests if payments enabled

    Next steps

    Vertical presets

    Ship niches in platform; select via ring-config

    Database selection

    DB_BACKEND_MODE and migration strategy

    Payment integration

    WayForPay, Stripe, webhooks

    AI customization

    Matcher tuning and agent costs

    Fork discipline: Config + locales first, component forks second, exclusions before propagation. Your clone should upgrade without merge wars.

    Quick Start (new clone)

    One Ring deployment per organization

    Token economics

    RING contracts and membership

    Architecture

    System layout and backend modes

    env
    
    NEXT_PUBLIC_BRAND_NAME=My Platform
    NEXT_PUBLIC_BRAND_TAGLINE=Your tagline
    NEXT_PUBLIC_BRAND_LOGO=/images/logo-light.svg
    NEXT_PUBLIC_BRAND_OG_IMAGE=/og-image.png
    json
    
    {
      "features": {
        "entities": { "enabled": true },
        "opportunities": { "enabled": true, "types": ["offer", "request"] },
        "store": { "enabled": true, "multiVendor": true },
        "web3": { "enabled": false },
        "ai": { "enabled": true, "matcher": true },
        "messaging": { "enabled": true }
      }
    }
    json
    
    {
      "home": {
        "hero": {
          "title": "Your headline",
          "subtitle": "One sentence value prop",
          "features": ["Bullet 1", "Bullet 2"]
        }
      }
    }
    env
    
    NEXT_PUBLIC_SUPPORTED_LOCALES=en,uk,ru
    NEXT_PUBLIC_DEFAULT_LOCALE=en
    json
    
    {
      "features": {
        "web3": {
          "enabled": true,
          "nativeToken": true,
          "defaultChain": "solana"
        }
      }
    }
    json
    
    {
      "customized_files": [
        "ring-config.json",
        "public/logo.svg",
        "public/logo-light.svg",
        "public/logo-dark.svg",
        "public/favicon.ico",
        "locales/en/config.json",
        "locales/uk/config.json",
        "locales/ru/config.json",
        "locales/en/vendor.json",
        "locales/uk/vendor.json",
        "locales/ru/vendor.json"
      ],
      "customized_directories": ["public/branding/"]
    }

    Quick Start (new clone)

    One Ring deployment per organization

    Token economics

    RING contracts and membership

    Architecture

    System layout and backend modes

    env
    
    NEXT_PUBLIC_BRAND_NAME=My Platform
    NEXT_PUBLIC_BRAND_TAGLINE=Your tagline
    NEXT_PUBLIC_BRAND_LOGO=/images/logo-light.svg
    NEXT_PUBLIC_BRAND_OG_IMAGE=/og-image.png
    json
    
    {
      "features": {
        "entities": { "enabled": true },
        "opportunities": { "enabled": true, "types": ["offer", "request"] },
        "store": { "enabled": true, "multiVendor": true },
        "web3": { "enabled": false },
        "ai": { "enabled": true, "matcher": true },
        "messaging": { "enabled": true }
      }
    }
    json
    
    {
      "home": {
        "hero": {
          "title": "Your headline",
          "subtitle": "One sentence value prop",
          "features": ["Bullet 1", "Bullet 2"]
        }
      }
    }
    env
    
    NEXT_PUBLIC_SUPPORTED_LOCALES=en,uk,ru
    NEXT_PUBLIC_DEFAULT_LOCALE=en
    json
    
    {
      "features": {
        "web3": {
          "enabled": true,
          "nativeToken": true,
          "defaultChain": "solana"
        }
      }
    }
    json
    
    {
      "customized_files": [
        "ring-config.json",
        "public/logo.svg",
        "public/logo-light.svg",
        "public/logo-dark.svg",
        "public/favicon.ico",
        "locales/en/config.json",
        "locales/uk/config.json",
        "locales/ru/config.json",
        "locales/en/vendor.json",
        "locales/uk/vendor.json",
        "locales/ru/vendor.json"
      ],
      "customized_directories": ["public/branding/"]
    }

    Quick Start (new clone)

    One Ring deployment per organization

    Token economics

    RING contracts and membership

    Architecture

    System layout and backend modes

    env
    
    NEXT_PUBLIC_BRAND_NAME=My Platform
    NEXT_PUBLIC_BRAND_TAGLINE=Your tagline
    NEXT_PUBLIC_BRAND_LOGO=/images/logo-light.svg
    NEXT_PUBLIC_BRAND_OG_IMAGE=/og-image.png
    json
    
    {
      "features": {
        "entities": { "enabled": true },
        "opportunities": { "enabled": true, "types": ["offer", "request"] },
        "store": { "enabled": true, "multiVendor": true },
        "web3": { "enabled": false },
        "ai": { "enabled": true, "matcher": true },
        "messaging": { "enabled": true }
      }
    }
    json
    
    {
      "home": {
        "hero": {
          "title": "Your headline",
          "subtitle": "One sentence value prop",
          "features": ["Bullet 1", "Bullet 2"]
        }
      }
    }
    env
    
    NEXT_PUBLIC_SUPPORTED_LOCALES=en,uk,ru
    NEXT_PUBLIC_DEFAULT_LOCALE=en
    json
    
    {
      "features": {
        "web3": {
          "enabled": true,
          "nativeToken": true,
          "defaultChain": "solana"
        }
      }
    }
    json
    
    {
      "customized_files": [
        "ring-config.json",
        "public/logo.svg",
        "public/logo-light.svg",
        "public/logo-dark.svg",
        "public/favicon.ico",
        "locales/en/config.json",
        "locales/uk/config.json",
        "locales/ru/config.json",
        "locales/en/vendor.json",
        "locales/uk/vendor.json",
        "locales/ru/vendor.json"
      ],
      "customized_directories": ["public/branding/"]
    }
    1. Docs
    2. /Customization
    3. /Customization Guide

    Updated Jul 14, 20264 min listen

    1. Docs
    2. /Customization
    3. /Customization Guide

    Updated Jul 14, 20264 min listen

    1. Docs
    2. /Customization
    3. /Customization Guide

    Updated Jul 14, 20264 min listen