BrandApp Playground

About

What BrandApp Playground is, who publishes it, and how it is built.

What this is

BrandApp Playground is the public reference implementation for @reopt-ai/brandapp-sdk, the TypeScript SDK for building applications on a Reopt BrandApp. It exists so that a developer evaluating or integrating the SDK can watch every module run against a real backend, next to the exact source that produced the result — no video, no abridged snippet, no gap between the documentation and what actually ships.

Every page in the sidebar pairs a live workspace with a code panel. EAV, AI, CMS, Files, authentication, single logout, plans and checkout, terms consent, webhooks, React hooks, the offline dev server, and the testing utilities each have their own page. Pages that would mutate a real BrandApp — schema migrations, for instance — are documented rather than executed, and say so.

Who publishes it

주식회사 리옵트 (Reopt), the company behind the Reopt brand platform. Reopt builds tools for brands to run customer experience, CRM, campaigns, and content operations in one place; BrandApp is the developer-facing surface of that platform, and this playground is its worked example. Reach the team through the contact page.

How it is built

Next.js App Router with React Server Components, TypeScript, and Tailwind CSS, using the Reopt opt-ui, opt-datagrid, opt-editor, and opt-filemanager component packages. Better Auth handles sessions, and the Reopt adapter stores them remotely, so the app carries no database of its own. Credentials never reach the browser: every SDK call runs server-side, behind a route handler.

Cost and access

The site is free and needs no account. The SDK is MIT-licensed and published on the public npm registry, so nothing here is gated behind a sales conversation. Connecting your own BrandApp credentials on the connection page unlocks the live demos against your own data; without them, every page still documents its API in full.

For AI agents

Every route has a Markdown twin: append .md to any path, or send Accept: text/markdown. The index lives at /llms.txt, the whole corpus in one file at /llms-full.txt, and this deployment's HTTP surface — including its security schemes and OAuth scopes — at /openapi.json.

Source