> ## Documentation Index > Fetch the complete documentation index at: https://docs.livry.dev/llms.txt > Use this file to discover all available pages before exploring further. # Introduction to Livry: Whitelabel Theming as a Service > Livry stores your design tokens, layers per-brand overrides on top, and serves the resulting theme to your app at runtime over a CDN. Livry is whitelabel theming as a service. It stores your design tokens, lets each of your customers' brands override them, and serves the resulting theme to your application at runtime over a CDN. If you build a product that has to look like someone else's — a platform with branded customer portals, a white-label SaaS, a multi-tenant app where each account brings its own identity — Livry is the piece that holds the branding and gets it to your frontend fast. ## What Livry does * **Stores tokens as JSON.** Schema-less, so your token vocabulary is whatever your design system already uses. * **Layers brand overrides on a default theme.** Each Organization expresses only what makes it different. * **Serves themes over signed URLs.** Access is controlled by a signing key held by an Application, and delivery goes through a CDN. * **Separates environments.** Sandbox and live Tenants are fully independent. ## Who it's for Livry is developer-first. You integrate it into your own frontend; there is no drop-in widget and no visual page builder. If your team already thinks in design tokens — the way Chakra, Tailwind, or a bespoke token pipeline does — Livry will feel familiar. ## What Livry is not * Not a CMS. Livry holds branding, not content. * Not a component library. You bring your own components; Livry supplies the values they render with. * Not a visual theme editor for end users. Managing brands happens through the developer portal and the Management API. Start here to understand Teams, Tenants, Organizations, and Applications.