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

    Project configuration

    Use Founder / Developer tabs in the docs sidebar to filter this page. Configuration for a paid clone order lives on the Order Lab desk — not only in local .env.

    After a calculator project order is paid, buyers and integrators configure the clone from the Order Lab desk (example admin desk: /admin/crm/orders/…?tab=secrets). Brand overlay fields use ?tab=project. Runtime env uses ?tab=secrets (buyer) and ?tab=env (integrator ops).

    TabWhoWhat
    projectBuyer + integratorAllowlisted projectConfig (name, slogan, logo) → brand mirrors on deploy
    secretsBuyer (owner)owner_private + public_shared keys from env.local.template
    envIntegrator / adminOps keys (integrator_ops) — DB, Auth.js secret, PSP, etc.
    wikiBuyer + integratorProject NODUS / Admin Wiki space
    playbookBuyer + integratorRingization steps for this order

    Operator map

    Public vars

    Browser-safe NEXT_PUBLIC_* values you can set on Secrets — including WalletConnect.

    Secrets

    Private keys (Firebase, SMTP, RingBase token) — encrypted at rest; applied on next deploy.

    WalletConnect Project ID

    Get a free Reown Cloud ID and paste it into Secrets for mobile QR wallets.

    Supported services

    Catalog of third-party accounts you may need (Firebase, Reown, Filebase, Google OAuth, PSP).

    Module map (verified)

    ConcernPath
    Buyer secrets UIfeatures/crm/orders/owner-secrets-panel.tsx
    Ownership taxonomyfeatures/crm/lab/env-key-ownership.ts (owner_private | public_shared | integrator_ops)
    Template allowlistenv.local.template → env-template-parser.ts
    Buyer env APIGET/PATCH /api/my-orders/[id]/env
    Project overlayproject_orders.data.projectConfig · ?tab=project
    Order Lab tabsfeatures/crm/lab/order-lab-tabs.ts

    Write roles

    Related documentation

    Related documentation

    WalletConnect Project ID (Reown Cloud)

    Next-step: obtain and paste NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID.

    Order Lab secrets

    Deep-dive: ownership model and Secrets tab save flow.

    Owner Project Lab

    Prerequisite: My Projects / Order Lab desk surfaces.

    Environment Configuration

    See-also: full env.local.template reference (integrator depth).

    Project configuration

    Use Founder / Developer tabs in the docs sidebar to filter this page. Configuration for a paid clone order lives on the Order Lab desk — not only in local .env.

    After a calculator project order is paid, buyers and integrators configure the clone from the Order Lab desk (example admin desk: /admin/crm/orders/…?tab=secrets). Brand overlay fields use ?tab=project. Runtime env uses ?tab=secrets (buyer) and ?tab=env (integrator ops).

    TabWhoWhat
    projectBuyer + integratorAllowlisted projectConfig (name, slogan, logo) → brand mirrors on deploy
    secretsBuyer (owner)owner_private + public_shared keys from env.local.template
    envIntegrator / adminOps keys (integrator_ops) — DB, Auth.js secret, PSP, etc.
    wikiBuyer + integratorProject NODUS / Admin Wiki space
    playbookBuyer + integratorRingization steps for this order

    Operator map

    Public vars

    Browser-safe NEXT_PUBLIC_* values you can set on Secrets — including WalletConnect.

    Secrets

    Private keys (Firebase, SMTP, RingBase token) — encrypted at rest; applied on next deploy.

    WalletConnect Project ID

    Get a free Reown Cloud ID and paste it into Secrets for mobile QR wallets.

    Supported services

    Catalog of third-party accounts you may need (Firebase, Reown, Filebase, Google OAuth, PSP).

    Module map (verified)

    ConcernPath
    Buyer secrets UIfeatures/crm/orders/owner-secrets-panel.tsx
    Ownership taxonomyfeatures/crm/lab/env-key-ownership.ts (owner_private | public_shared | integrator_ops)
    Template allowlistenv.local.template → env-template-parser.ts
    Buyer env APIGET/PATCH /api/my-orders/[id]/env
    Project overlayproject_orders.data.projectConfig · ?tab=project
    Order Lab tabsfeatures/crm/lab/order-lab-tabs.ts

    Write roles

    Related documentation

    Related documentation

    WalletConnect Project ID (Reown Cloud)

    Next-step: obtain and paste NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID.

    Order Lab secrets

    Deep-dive: ownership model and Secrets tab save flow.

    Owner Project Lab

    Prerequisite: My Projects / Order Lab desk surfaces.

    Environment Configuration

    See-also: full env.local.template reference (integrator depth).

    Project configuration

    Use Founder / Developer tabs in the docs sidebar to filter this page. Configuration for a paid clone order lives on the Order Lab desk — not only in local .env.

    After a calculator project order is paid, buyers and integrators configure the clone from the Order Lab desk (example admin desk: /admin/crm/orders/…?tab=secrets). Brand overlay fields use ?tab=project. Runtime env uses ?tab=secrets (buyer) and ?tab=env (integrator ops).

    TabWhoWhat
    projectBuyer + integratorAllowlisted projectConfig (name, slogan, logo) → brand mirrors on deploy
    secretsBuyer (owner)owner_private + public_shared keys from env.local.template
    envIntegrator / adminOps keys (integrator_ops) — DB, Auth.js secret, PSP, etc.
    wikiBuyer + integratorProject NODUS / Admin Wiki space
    playbookBuyer + integratorRingization steps for this order

    Operator map

    Public vars

    Browser-safe NEXT_PUBLIC_* values you can set on Secrets — including WalletConnect.

    Secrets

    Private keys (Firebase, SMTP, RingBase token) — encrypted at rest; applied on next deploy.

    WalletConnect Project ID

    Get a free Reown Cloud ID and paste it into Secrets for mobile QR wallets.

    Supported services

    Catalog of third-party accounts you may need (Firebase, Reown, Filebase, Google OAuth, PSP).

    Module map (verified)

    ConcernPath
    Buyer secrets UIfeatures/crm/orders/owner-secrets-panel.tsx
    Ownership taxonomyfeatures/crm/lab/env-key-ownership.ts (owner_private | public_shared | integrator_ops)
    Template allowlistenv.local.template → env-template-parser.ts
    Buyer env APIGET/PATCH /api/my-orders/[id]/env
    Project overlayproject_orders.data.projectConfig · ?tab=project
    Order Lab tabsfeatures/crm/lab/order-lab-tabs.ts

    Write roles

    Related documentation

    Related documentation

    WalletConnect Project ID (Reown Cloud)

    Next-step: obtain and paste NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID.

    Order Lab secrets

    Deep-dive: ownership model and Secrets tab save flow.

    Owner Project Lab

    Prerequisite: My Projects / Order Lab desk surfaces.

    Environment Configuration

    See-also: full env.local.template reference (integrator depth).

    NODUS wiki

    Keep brand and deploy decisions in the order wiki — not only in chat.

    Playbook

    Order Lab playbook tab + full ringization playbook.

    Typical buyer path

    1. Open My Projects → your order → Secrets.
    2. Fill Firebase / RingBase / public URL fields using the doc links on the panel.
    3. Create a WalletConnect (Reown) Project ID and set NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID.
    4. Capture decisions on the Wiki tab; follow the Playbook checklist with your integrator.
    5. Integrator deploys — secrets apply on next deploy (appliedOnNextDeploy).
    Role
    May PATCH
    buyerowner_private + public_shared
    integratorintegrator_ops + public_shared
    adminall except brand-mirror keys (those come from projectConfig apply)

    Brand mirrors (NEXT_PUBLIC_BRAND_*, RING_ORDER_PROJECT_CONFIG) are not writable via env routes — they flow from Order Project Config on deploy.

    Ethereum wallets (Wagmi v3)

    Same-workflow: Wagmi connectors gated on WalletConnect project ID.

    NODUS wiki

    Keep brand and deploy decisions in the order wiki — not only in chat.

    Playbook

    Order Lab playbook tab + full ringization playbook.

    Typical buyer path

    1. Open My Projects → your order → Secrets.
    2. Fill Firebase / RingBase / public URL fields using the doc links on the panel.
    3. Create a WalletConnect (Reown) Project ID and set NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID.
    4. Capture decisions on the Wiki tab; follow the Playbook checklist with your integrator.
    5. Integrator deploys — secrets apply on next deploy (appliedOnNextDeploy).
    Role
    May PATCH
    buyerowner_private + public_shared
    integratorintegrator_ops + public_shared
    adminall except brand-mirror keys (those come from projectConfig apply)

    Brand mirrors (NEXT_PUBLIC_BRAND_*, RING_ORDER_PROJECT_CONFIG) are not writable via env routes — they flow from Order Project Config on deploy.

    Ethereum wallets (Wagmi v3)

    Same-workflow: Wagmi connectors gated on WalletConnect project ID.

    NODUS wiki

    Keep brand and deploy decisions in the order wiki — not only in chat.

    Playbook

    Order Lab playbook tab + full ringization playbook.

    Typical buyer path

    1. Open My Projects → your order → Secrets.
    2. Fill Firebase / RingBase / public URL fields using the doc links on the panel.
    3. Create a WalletConnect (Reown) Project ID and set NEXT_PUBLIC_WALLETCONNECT_PROJECT_ID.
    4. Capture decisions on the Wiki tab; follow the Playbook checklist with your integrator.
    5. Integrator deploys — secrets apply on next deploy (appliedOnNextDeploy).
    Role
    May PATCH
    buyerowner_private + public_shared
    integratorintegrator_ops + public_shared
    adminall except brand-mirror keys (those come from projectConfig apply)

    Brand mirrors (NEXT_PUBLIC_BRAND_*, RING_ORDER_PROJECT_CONFIG) are not writable via env routes — they flow from Order Project Config on deploy.

    Ethereum wallets (Wagmi v3)

    Same-workflow: Wagmi connectors gated on WalletConnect project ID.

    1. Docs
    2. /Project configuration
    Updated Aug 7, 20263 min listen
    1. Docs
    2. /Project configuration
    Updated Aug 7, 20263 min listen
    1. Docs
    2. /Project configuration
    Updated Aug 7, 20263 min listen