OpenUI Cloud

The managed backend for Agent Interface: conversation history, production-grade generative UI, and prebuilt presentation and report artifacts.

OpenUI Cloud is the managed backend for Agent Interface. It is built on the open-source OpenUI rendering engine and adds the production layers on top, so you point your app at it and ship instead of operating that infrastructure yourself.

A Cloud-rendered, on-brand interface beside a report and presentation artifact it generated

What you get

  • Conversation history. Threads and messages are stored and reloaded for you. No database to run, no endpoints to write.
  • Production-grade generative UI. A pre-tested, responsive, accessible component set. Invalid model output is detected and corrected before the user sees it, and a middleware layer normalizes model quirks so generation stays consistent across providers and model versions.
  • Prebuilt artifacts. Reports and presentations the agent generates and renders out of the box, with no renderer to build.
  • Theming and white-labeling. Fonts, colors, spacing, and component styles are configurable, so every agent-rendered UI is on-brand by default. Multiple brand configurations are supported.
  • Production hardening. Model fallbacks and a degraded mode when a provider is slow or down, version pinning and rollback to a known-good setup, and observability with an audit trail: render success, latency, token usage, and a record of what was rendered for whom.

Connect

AgentInterface connects to Cloud through two props, both wired by the scaffold (or by hand, following the openui-cloud example in the repo):

  • llm points at a thin /api/chat route in your app that proxies to Cloud's Responses endpoint. Your THESYS_API_KEY stays on that route and never reaches the browser. On the client it uses openAIResponsesAdapter() with openAIConversationMessageFormat.
  • storage is useOpenuiCloudStorage() from @openuidev/thesys. It reads conversations and artifacts from Cloud directly, authenticated by a short-lived frontend token your app mints from a /api/frontend-token route (so the server key never reaches the browser).

The component set (chatLibrary), artifact renderers, and categories also come from @openuidev/thesys.

Add your server-side key:

THESYS_API_KEY=sk-th-your-key

Generate a key in the Thesys console. See Quickstart to scaffold a Cloud app.

OpenUI vs OpenUI Cloud

OpenUI (open source)OpenUI Cloud
Generative UI rendering
Streaming and progressive rendering
Production-grade componentsBasicOptimized, cross-browser tested
Prebuilt report and presentation artifacts
Theming and white-labeling
Error detection and correction
Cross-model consistency
Fallbacks, versioning, observability

Roadmap

Coming next:

  • Document exports. Download reports and presentations as PDF, DOCX, and PPT.
  • Live dashboards. Dashboards backed by your business-specific data.
  • Manual editing. Edit generated reports and presentations by hand.
  • Insights. See what users ask, where they hit dead ends, and which usage patterns to build for next.
  • Continual learning and memory. Cloud learns how individual users prefer information presented and adapts over time.

On this page