Documentation

    Documentation

    Documentation

    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    Ring Platform Logo

    Завантаження документації...

    Підготовка контенту платформи Ring

    1. /Vendor Guide

    Updated Jun 15, 20266 min listen

    1. /Vendor Guide

    Updated Jun 15, 20266 min listen

    1. /Vendor Guide

    Updated Jun 15, 20266 min listen

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

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    Database migrations
    First Success Validation
    Troubleshooting
    Next Steps
    Architecture
    Backend modes and databases
    Data Model
    Authentication Architecture
    Email AI-CRM architecture
    PaymentConductor architecture
    Refcodes architecture
    News Kingdom architecture
    Proxy and internationalization
    Real Time
    Discovery Mutation Sync
    Security
    Features
    Doc System
    Authentication
    Email AI-CRM
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Tunnel Protocol
    Web3 Wallet
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    Referral Codes (Refcodes)
    Affiliate & Referral Enablement
    Payment Integration
    PaymentConductor
    VideoConductor
    WayForPay Payment Integration
    News Module - Digital Newspaper Experience
    Member Blogs
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Wallet
    Wallet Security Tips
    API
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet API
    Store API
    Admin API
    CLI
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Database Backend Selection
    Token Economics Setup
    Payment Gateway Integration
    AI Agent Customization
    Reference Ring deployments
    Branding
    Features
    Localization
    Themes
    Components
    Web3
    Token launch jurisdictions
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Development
    Local Setup
    Code Structure
    Documentation components
    Community tooling
    Ring MCP Server
    Generative Images (ImageConductor)
    Autonomous Newsroom (Grok)
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    MCP
    ring-image-create
    ring-video-create
    Roadmap
    Examples
    Quick Start
    Authentication
    Email AI-CRM developer guide
    API Integration Examples
    Web3 Integration
    White Label
    Real World
    API Examples (cURL)
    Integrations
    Ethereum wallets (Wagmi v3)

    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)

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

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    Database migrations
    First Success Validation
    Troubleshooting
    Next Steps
    Architecture
    Backend modes and databases
    Data Model
    Authentication Architecture
    Email AI-CRM architecture
    PaymentConductor architecture
    Refcodes architecture
    News Kingdom architecture
    Proxy and internationalization
    Real Time
    Discovery Mutation Sync
    Security
    Features
    Doc System
    Authentication
    Email AI-CRM
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Tunnel Protocol
    Web3 Wallet
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    Referral Codes (Refcodes)
    Affiliate & Referral Enablement
    Payment Integration
    PaymentConductor
    VideoConductor
    WayForPay Payment Integration
    News Module - Digital Newspaper Experience
    Member Blogs
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Wallet
    Wallet Security Tips
    API
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet API
    Store API
    Admin API
    CLI
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Database Backend Selection
    Token Economics Setup
    Payment Gateway Integration
    AI Agent Customization
    Reference Ring deployments
    Branding
    Features
    Localization
    Themes
    Components
    Web3
    Token launch jurisdictions
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Development
    Local Setup
    Code Structure
    Documentation components
    Community tooling
    Ring MCP Server
    Generative Images (ImageConductor)
    Autonomous Newsroom (Grok)
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    MCP
    ring-image-create
    ring-video-create
    Roadmap
    Examples
    Quick Start
    Authentication
    Email AI-CRM developer guide
    API Integration Examples
    Web3 Integration
    White Label
    Real World
    API Examples (cURL)
    Integrations
    Ethereum wallets (Wagmi v3)

    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)

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

    Welcome to Ring
    Quick Reference
    Getting Started
    Prerequisites
    Installation
    Database migrations
    First Success Validation
    Troubleshooting
    Next Steps
    Architecture
    Backend modes and databases
    Data Model
    Authentication Architecture
    Email AI-CRM architecture
    PaymentConductor architecture
    Refcodes architecture
    News Kingdom architecture
    Proxy and internationalization
    Real Time
    Discovery Mutation Sync
    Security
    Features
    Doc System
    Authentication
    Email AI-CRM
    Entities
    Opportunities
    Notifications
    Push Notifications with FCM (Ring-Powered)
    Tunnel Protocol
    Web3 Wallet
    Multi-Vendor Store
    Inventory & Stock
    Vendor Management
    Commissions & Settlements
    Referral Codes (Refcodes)
    Affiliate & Referral Enablement
    Payment Integration
    PaymentConductor
    VideoConductor
    WayForPay Payment Integration
    News Module - Digital Newspaper Experience
    Member Blogs
    Scientific Editor
    Locale System
    Security & Compliance
    NFT Marketplace
    Token Staking System
    Performance Optimization Patterns
    Mobile Experience
    Wallet
    Wallet Security Tips
    API
    Authentication
    Email AI-CRM API
    Entities
    Opportunities
    Messaging API
    Notifications API
    Wallet API
    Store API
    Admin API
    CLI
    Customization
    Quick Start — Your First Ring Clone
    Customization Guide
    Database Backend Selection
    Token Economics Setup
    Payment Gateway Integration
    AI Agent Customization
    Reference Ring deployments
    Branding
    Features
    Localization
    Themes
    Components
    Web3
    Token launch jurisdictions
    Deployment
    Self-hosted deployment
    Vercel
    Docker
    Environment Configuration
    Monitoring & Analytics
    Performance Optimization
    Backup & Recovery
    Development
    Local Setup
    Code Structure
    Documentation components
    Community tooling
    Ring MCP Server
    Generative Images (ImageConductor)
    Autonomous Newsroom (Grok)
    OSS vs enterprise
    Whitelabel Navigation
    Best Practices
    Workflow
    Code Style
    Performance
    Testing
    Deployment
    Debugging
    Contributing
    MCP
    ring-image-create
    ring-video-create
    Roadmap
    Examples
    Quick Start
    Authentication
    Email AI-CRM developer guide
    API Integration Examples
    Web3 Integration
    White Label
    Real World
    API Examples (cURL)
    Integrations
    Ethereum wallets (Wagmi v3)

    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)
    Docs
    Docs
    Docs

    Vendor Guide

    Sell on Ring Platform as a vendor — whether you ship Ring clones, AI tooling, expert integrations, or managed hosting. This guide is written for you (the seller), not the platform operator.

    Open-source marketplace

    Ring Platform is open source. The community portal at ring-platform.org hosts a multi-vendor store where verified entities list digital products and services for builders, agencies, and platform operators worldwide.

    Who can become a vendor?

    You need:

    1. A Ring account with at least Subscriber access (Member role unlocks additional opportunity types elsewhere on the platform).
    2. A completed vendor store at /vendor/start — slug, name, description, categories, and logo.
    3. Honest listings that match one or more store categories below.

    Your public storefront lives at:

    text
    
    /store/vendors/{your-store-slug}

    Vendor journey at a glance

    Nine common vendor types on ring-platform.org

    These are the archetypes we see most often on the open-source Ring ecosystem. You may fit one or combine several.

    #Vendor typeWhat you sellTypical categories
    1Ring implementation studioWhite-label Ring clones, module wiring, Auth.js/DB setup, k8s deploy packagesring-platform, expert-services
    2Dev kit publisherStarter repos, integration packs, CLI scaffolds, migration kitsdev-kits, ring-platform
    3AI tools & agent builderPrompt packs, MCP servers, matcher configs, local LLM pipelinesai-tools, saas-assets
    4Expert services firmAudits, custom features, payment/tunnel/i18n remediation, SLA supportexpert-services
    5Digital template studioUI kits, landing themes, email/notification templates, docs layouts
    Pick your positioning

    Buyers compare outcome (faster launch, fewer regressions, compliant payments) — not stack trivia. Lead with deliverables, support window, and what is included in the repo or service SOW.

    Store categories on ring-platform.org

    When onboarding, you select one or more categories. They align with filter chips in the main store:

    • ring-platform — deployment, modules, branding, localization, payments, tunnel/Web3 customization
    • dev-kits — scaffolds, integration bundles, tooling
    • ai-tools — agents, matchers, automation
    • expert-services — professional services and retainers
    • digital-templates — themes, layouts, content packs
    • learn — courses and structured training
    • community — memberships, cohorts, office hours
    • saas-assets — hosted add-ons, subscriptions, infrastructure products

    Onboarding checklist

    1. 1

      Create your store

      Go to /vendor/start and complete:

      • Store slug — URL-safe identifier (e.g. acme-ring-studio)
      • Store name — public brand
      • Description — who you help and what you ship (max 500 characters)
      • Categories — at least one from the list above
      • Logo — square image, 512×512 recommended
    2. 2

      Add your first product

      Open /vendor/products → Add Product:

      • 1–5 photos (first image is the hero)
      • Name, category, price (UAH; optional DAAR display)
      • Stock count for physical or seat-limited digital goods
      • Short description; use clear scope bullets for services

      Optional: Submit to Main Store for admin review and listing in the central /store catalog.

    3. 3

      Configure fulfillment

      • Digital goods — document delivery (repo access, license key, calendar link) in the product description and order messaging.
      • Services — state response SLA, timezone, and what discovery call includes.
      • Hosted offers — link status page or onboarding doc; never promise root access you do not provide.
    4. 4

      Monitor dashboard

    Trust tiers and commission

    Ring uses a trust tier model. New vendors start at NEW (higher platform commission); commission decreases as you maintain quality sales, reviews, and tenure.

    TierIndicative commissionHow you progress
    NEW20%Complete onboarding; first listings live
    BASIC18%Early sales; positive feedback
    VERIFIED16%Sustained rating and revenue thresholds
    TRUSTED14%Longer track record; featured eligibility
    PREMIUM12%Top reputation; lowest platform take

    Exact thresholds and overrides may be set in merchant configuration (admin-managed). Details: Vendor Management and Multi-Vendor Store.

    Main Store review

    Products submitted to the Main Store are reviewed for quality, accuracy, and category fit. Rejected listings include a reason — fix and resubmit.

    Listing quality (what buyers expect)

    • Use real screenshots or diagrams of deliverables
    • Specify Ring / Next.js / Auth.js versions you support
    • List prerequisites (k8s cluster, Postgres, WayForPay, etc.)
    • Offer a clear refund or revision policy for services

    Payments and settlements

    • Checkout supports fiat (WayForPay) and platform wallet flows where enabled.
    • Settlements are automated with tier-based commission deduction; see earnings for pending and completed payouts.
    • For payment architecture: Payment Conductor and WayForPay integration.

    AI product enrichment

    Upload a hero image plus basic fields; platform AI can suggest descriptions, tags, and cross-sells. You remain responsible for technical accuracy — review every generated field before publishing.

    After launch

    1. Link your storefront from your site and GitHub org profile.
    2. Respond to buyer messages via Ring messaging where enabled.
    3. Keep stock and pricing updated after each release.
    4. Request Main Store inclusion once you have polished assets and docs.

    Related documentation

    Multi-Vendor Store

    Architecture, payments, and marketplace flows.

    Vendor Management (ERP)

    Tiers, trust scoring, and merchant configuration.

    Wallet & credits

    Token balances and checkout integration.

    Customization & white-label

    Support

    • Onboarding UI: /vendor/start
    • Community: ring-platform.org — opportunities, entities, and docs
    • Source: github.com/connectplatform/ring

    Last updated: June 2026. Commission tiers and routes reflect ring-platform.org community portal; self-hosted clones may configure marketplace rules independently.

    Vendor Guide

    Sell on Ring Platform as a vendor — whether you ship Ring clones, AI tooling, expert integrations, or managed hosting. This guide is written for you (the seller), not the platform operator.

    Open-source marketplace

    Ring Platform is open source. The community portal at ring-platform.org hosts a multi-vendor store where verified entities list digital products and services for builders, agencies, and platform operators worldwide.

    Who can become a vendor?

    You need:

    1. A Ring account with at least Subscriber access (Member role unlocks additional opportunity types elsewhere on the platform).
    2. A completed vendor store at /vendor/start — slug, name, description, categories, and logo.
    3. Honest listings that match one or more store categories below.

    Your public storefront lives at:

    text
    
    /store/vendors/{your-store-slug}

    Vendor journey at a glance

    Nine common vendor types on ring-platform.org

    These are the archetypes we see most often on the open-source Ring ecosystem. You may fit one or combine several.

    #Vendor typeWhat you sellTypical categories
    1Ring implementation studioWhite-label Ring clones, module wiring, Auth.js/DB setup, k8s deploy packagesring-platform, expert-services
    2Dev kit publisherStarter repos, integration packs, CLI scaffolds, migration kitsdev-kits, ring-platform
    3AI tools & agent builderPrompt packs, MCP servers, matcher configs, local LLM pipelinesai-tools, saas-assets
    4Expert services firmAudits, custom features, payment/tunnel/i18n remediation, SLA supportexpert-services
    5Digital template studioUI kits, landing themes, email/notification templates, docs layouts
    Pick your positioning

    Buyers compare outcome (faster launch, fewer regressions, compliant payments) — not stack trivia. Lead with deliverables, support window, and what is included in the repo or service SOW.

    Store categories on ring-platform.org

    When onboarding, you select one or more categories. They align with filter chips in the main store:

    • ring-platform — deployment, modules, branding, localization, payments, tunnel/Web3 customization
    • dev-kits — scaffolds, integration bundles, tooling
    • ai-tools — agents, matchers, automation
    • expert-services — professional services and retainers
    • digital-templates — themes, layouts, content packs
    • learn — courses and structured training
    • community — memberships, cohorts, office hours
    • saas-assets — hosted add-ons, subscriptions, infrastructure products

    Onboarding checklist

    1. 1

      Create your store

      Go to /vendor/start and complete:

      • Store slug — URL-safe identifier (e.g. acme-ring-studio)
      • Store name — public brand
      • Description — who you help and what you ship (max 500 characters)
      • Categories — at least one from the list above
      • Logo — square image, 512×512 recommended
    2. 2

      Add your first product

      Open /vendor/products → Add Product:

      • 1–5 photos (first image is the hero)
      • Name, category, price (UAH; optional DAAR display)
      • Stock count for physical or seat-limited digital goods
      • Short description; use clear scope bullets for services

      Optional: Submit to Main Store for admin review and listing in the central /store catalog.

    3. 3

      Configure fulfillment

      • Digital goods — document delivery (repo access, license key, calendar link) in the product description and order messaging.
      • Services — state response SLA, timezone, and what discovery call includes.
      • Hosted offers — link status page or onboarding doc; never promise root access you do not provide.
    4. 4

      Monitor dashboard

    Trust tiers and commission

    Ring uses a trust tier model. New vendors start at NEW (higher platform commission); commission decreases as you maintain quality sales, reviews, and tenure.

    TierIndicative commissionHow you progress
    NEW20%Complete onboarding; first listings live
    BASIC18%Early sales; positive feedback
    VERIFIED16%Sustained rating and revenue thresholds
    TRUSTED14%Longer track record; featured eligibility
    PREMIUM12%Top reputation; lowest platform take

    Exact thresholds and overrides may be set in merchant configuration (admin-managed). Details: Vendor Management and Multi-Vendor Store.

    Main Store review

    Products submitted to the Main Store are reviewed for quality, accuracy, and category fit. Rejected listings include a reason — fix and resubmit.

    Listing quality (what buyers expect)

    • Use real screenshots or diagrams of deliverables
    • Specify Ring / Next.js / Auth.js versions you support
    • List prerequisites (k8s cluster, Postgres, WayForPay, etc.)
    • Offer a clear refund or revision policy for services

    Payments and settlements

    • Checkout supports fiat (WayForPay) and platform wallet flows where enabled.
    • Settlements are automated with tier-based commission deduction; see earnings for pending and completed payouts.
    • For payment architecture: Payment Conductor and WayForPay integration.

    AI product enrichment

    Upload a hero image plus basic fields; platform AI can suggest descriptions, tags, and cross-sells. You remain responsible for technical accuracy — review every generated field before publishing.

    After launch

    1. Link your storefront from your site and GitHub org profile.
    2. Respond to buyer messages via Ring messaging where enabled.
    3. Keep stock and pricing updated after each release.
    4. Request Main Store inclusion once you have polished assets and docs.

    Related documentation

    Multi-Vendor Store

    Architecture, payments, and marketplace flows.

    Vendor Management (ERP)

    Tiers, trust scoring, and merchant configuration.

    Wallet & credits

    Token balances and checkout integration.

    Customization & white-label

    Support

    • Onboarding UI: /vendor/start
    • Community: ring-platform.org — opportunities, entities, and docs
    • Source: github.com/connectplatform/ring

    Last updated: June 2026. Commission tiers and routes reflect ring-platform.org community portal; self-hosted clones may configure marketplace rules independently.

    Vendor Guide

    Sell on Ring Platform as a vendor — whether you ship Ring clones, AI tooling, expert integrations, or managed hosting. This guide is written for you (the seller), not the platform operator.

    Open-source marketplace

    Ring Platform is open source. The community portal at ring-platform.org hosts a multi-vendor store where verified entities list digital products and services for builders, agencies, and platform operators worldwide.

    Who can become a vendor?

    You need:

    1. A Ring account with at least Subscriber access (Member role unlocks additional opportunity types elsewhere on the platform).
    2. A completed vendor store at /vendor/start — slug, name, description, categories, and logo.
    3. Honest listings that match one or more store categories below.

    Your public storefront lives at:

    text
    
    /store/vendors/{your-store-slug}

    Vendor journey at a glance

    Nine common vendor types on ring-platform.org

    These are the archetypes we see most often on the open-source Ring ecosystem. You may fit one or combine several.

    #Vendor typeWhat you sellTypical categories
    1Ring implementation studioWhite-label Ring clones, module wiring, Auth.js/DB setup, k8s deploy packagesring-platform, expert-services
    2Dev kit publisherStarter repos, integration packs, CLI scaffolds, migration kitsdev-kits, ring-platform
    3AI tools & agent builderPrompt packs, MCP servers, matcher configs, local LLM pipelinesai-tools, saas-assets
    4Expert services firmAudits, custom features, payment/tunnel/i18n remediation, SLA supportexpert-services
    5Digital template studioUI kits, landing themes, email/notification templates, docs layouts
    Pick your positioning

    Buyers compare outcome (faster launch, fewer regressions, compliant payments) — not stack trivia. Lead with deliverables, support window, and what is included in the repo or service SOW.

    Store categories on ring-platform.org

    When onboarding, you select one or more categories. They align with filter chips in the main store:

    • ring-platform — deployment, modules, branding, localization, payments, tunnel/Web3 customization
    • dev-kits — scaffolds, integration bundles, tooling
    • ai-tools — agents, matchers, automation
    • expert-services — professional services and retainers
    • digital-templates — themes, layouts, content packs
    • learn — courses and structured training
    • community — memberships, cohorts, office hours
    • saas-assets — hosted add-ons, subscriptions, infrastructure products

    Onboarding checklist

    1. 1

      Create your store

      Go to /vendor/start and complete:

      • Store slug — URL-safe identifier (e.g. acme-ring-studio)
      • Store name — public brand
      • Description — who you help and what you ship (max 500 characters)
      • Categories — at least one from the list above
      • Logo — square image, 512×512 recommended
    2. 2

      Add your first product

      Open /vendor/products → Add Product:

      • 1–5 photos (first image is the hero)
      • Name, category, price (UAH; optional DAAR display)
      • Stock count for physical or seat-limited digital goods
      • Short description; use clear scope bullets for services

      Optional: Submit to Main Store for admin review and listing in the central /store catalog.

    3. 3

      Configure fulfillment

      • Digital goods — document delivery (repo access, license key, calendar link) in the product description and order messaging.
      • Services — state response SLA, timezone, and what discovery call includes.
      • Hosted offers — link status page or onboarding doc; never promise root access you do not provide.
    4. 4

      Monitor dashboard

    Trust tiers and commission

    Ring uses a trust tier model. New vendors start at NEW (higher platform commission); commission decreases as you maintain quality sales, reviews, and tenure.

    TierIndicative commissionHow you progress
    NEW20%Complete onboarding; first listings live
    BASIC18%Early sales; positive feedback
    VERIFIED16%Sustained rating and revenue thresholds
    TRUSTED14%Longer track record; featured eligibility
    PREMIUM12%Top reputation; lowest platform take

    Exact thresholds and overrides may be set in merchant configuration (admin-managed). Details: Vendor Management and Multi-Vendor Store.

    Main Store review

    Products submitted to the Main Store are reviewed for quality, accuracy, and category fit. Rejected listings include a reason — fix and resubmit.

    Listing quality (what buyers expect)

    • Use real screenshots or diagrams of deliverables
    • Specify Ring / Next.js / Auth.js versions you support
    • List prerequisites (k8s cluster, Postgres, WayForPay, etc.)
    • Offer a clear refund or revision policy for services

    Payments and settlements

    • Checkout supports fiat (WayForPay) and platform wallet flows where enabled.
    • Settlements are automated with tier-based commission deduction; see earnings for pending and completed payouts.
    • For payment architecture: Payment Conductor and WayForPay integration.

    AI product enrichment

    Upload a hero image plus basic fields; platform AI can suggest descriptions, tags, and cross-sells. You remain responsible for technical accuracy — review every generated field before publishing.

    After launch

    1. Link your storefront from your site and GitHub org profile.
    2. Respond to buyer messages via Ring messaging where enabled.
    3. Keep stock and pricing updated after each release.
    4. Request Main Store inclusion once you have polished assets and docs.

    Related documentation

    Multi-Vendor Store

    Architecture, payments, and marketplace flows.

    Vendor Management (ERP)

    Tiers, trust scoring, and merchant configuration.

    Wallet & credits

    Token balances and checkout integration.

    Customization & white-label

    Support

    • Onboarding UI: /vendor/start
    • Community: ring-platform.org — opportunities, entities, and docs
    • Source: github.com/connectplatform/ring

    Last updated: June 2026. Commission tiers and routes reflect ring-platform.org community portal; self-hosted clones may configure marketplace rules independently.

    digital-templates
    6Cloud & Kubernetes hostManaged Ring hosting, CNPG backups, ingress/TLS, observability stackssaas-assets, expert-services
    7Marketing & growth agencyLaunch playbooks, SEO for Ring clones, community growth, Product Hunt kitsexpert-services, digital-templates
    8Education & training providerCourses, workshops, certification prep for Ring stack (Next.js 16, Auth.js v5, k8s)learn, community
    9Open-source SaaS asset publisherPlugins, premium components, licensed extensions compatible with Ring clonessaas-assets, dev-kits

    Use /vendor/dashboard for sales snapshot, /vendor/orders for fulfillment, /vendor/earnings for settlements, and /vendor/stock for inventory.

    Branding and clone-specific marketplace rules.

    digital-templates
    6Cloud & Kubernetes hostManaged Ring hosting, CNPG backups, ingress/TLS, observability stackssaas-assets, expert-services
    7Marketing & growth agencyLaunch playbooks, SEO for Ring clones, community growth, Product Hunt kitsexpert-services, digital-templates
    8Education & training providerCourses, workshops, certification prep for Ring stack (Next.js 16, Auth.js v5, k8s)learn, community
    9Open-source SaaS asset publisherPlugins, premium components, licensed extensions compatible with Ring clonessaas-assets, dev-kits

    Use /vendor/dashboard for sales snapshot, /vendor/orders for fulfillment, /vendor/earnings for settlements, and /vendor/stock for inventory.

    Branding and clone-specific marketplace rules.

    digital-templates
    6Cloud & Kubernetes hostManaged Ring hosting, CNPG backups, ingress/TLS, observability stackssaas-assets, expert-services
    7Marketing & growth agencyLaunch playbooks, SEO for Ring clones, community growth, Product Hunt kitsexpert-services, digital-templates
    8Education & training providerCourses, workshops, certification prep for Ring stack (Next.js 16, Auth.js v5, k8s)learn, community
    9Open-source SaaS asset publisherPlugins, premium components, licensed extensions compatible with Ring clonessaas-assets, dev-kits

    Use /vendor/dashboard for sales snapshot, /vendor/orders for fulfillment, /vendor/earnings for settlements, and /vendor/stock for inventory.

    Branding and clone-specific marketplace rules.