The Ring · hosted router

One door for your AI suite.

Hosted Ring gives you the self-hostable Ring and Phylax runtime, deployed and managed for you with cloud checkout, metering, setup, and configuration UI.

Buy hosted Ring Self-host the runtime

The hosted path runs through the Zenod cloud control plane. It provisions your tenant, wires tokens and watchdogs, then sends you to Ring setup.

Hosted first, self-hostable underneath.

Ring is still open runtime infrastructure. The difference is who operates it: the hosted product deploys and manages the same kind of Ring/Phylax stack for you, while self-hosting means you run the MCP servers and runtime yourself.

Hosted Ring

Use the cloud product when you want the managed path from checkout to setup to ongoing operation.

  • Cloud buy route creates the hosted Ring order.
  • The control plane provisions the tenant runtime.
  • Cloud UI handles metering, setup, config, and recovery state.
  • Cloud WhatsApp setup uses managed provider or business-number connection, not QR pairing.

Self-host

Use the runtime directly when you want to operate your own Ring, Phylax, MCP servers, secrets, and updates.

  • You run the Ring router/control surface yourself.
  • You run Phylax or another channel gateway yourself.
  • You bring your own hosting, metering, setup flow, and config UI.
  • QR pairing belongs here for self-host and development WhatsApp flows.

What happens after checkout.

  1. Buy hosted Ring. The cloud route starts the Ring checkout with Ring-specific provisioning metadata.
  2. We deploy the tenant runtime. The cloud control plane provisions Ring, Phylax, tokens, metering, and watchdog receipts.
  3. You configure your channels and products. Ring shows channel state, route policy, connected-server health, and links to each product's own settings page.
  4. You use one conversation door. Messages arrive through Phylax or web chat, Ring routes each turn, and connected products do their own work.

Clear product boundaries.

Ring is the switchboard, not the owner of every product setting. It routes turns, records provenance, and keeps the control surface readable.

Ring

Owns the router, channel/product control surface, connected-server registry, skills, route policy, relay policy, mailbox provenance, logs, and settings links.

Phylax

Carries channel traffic. Inbound messages go to Ring; outbound responses come from Ring. It exposes health, delivery receipts, provider/session state, allowed senders, and media handles.

Zenod

Owns memory and media ingest. When text, audio, screenshots, PDFs, Drive files, or media handles should become memory, Ring sends them to Zenod for archive, extraction, digest, filing, and receipts.

Connected products own their own cloud settings pages. Ring shows their status, route policy, health checks, test calls, and a link to configure each product at the source.