# Livry

> Livry is whitelabel theming as a service — store design tokens, layer per-brand overrides, and serve resolved themes to your application at runtime.

## Docs

- [Introduction to Livry: Whitelabel Theming as a Service](https://docs.livry.dev/introduction.md): 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 Quickstart: From Sign-Up to a Rendered Theme](https://docs.livry.dev/quickstart.md): Create your Livry account, define a default theme, add your first branded Organization, and fetch a resolved theme over a signed URL.
- [Core Concepts: Teams, Tenants, Organizations, and Applications](https://docs.livry.dev/core-concepts.md): Understand Livry's building blocks: Teams for billing, Tenants as environments, Organizations as brands, and Applications as signing key holders.
- [Design Tokens in Livry: Schema-Less JSON Theme Values](https://docs.livry.dev/theming/tokens.md): Livry stores theme values as schema-less JSON tokens, so you can model your own design system vocabulary rather than adopting a fixed taxonomy.
- [Organizations and Theme Overrides in Livry](https://docs.livry.dev/theming/organizations.md): Each Organization is a brand holding overrides on your default theme. Learn how override resolution works and why Organizations don't move between environments.
- [How Livry Serves Themes to Your Application at Runtime](https://docs.livry.dev/serving/overview.md): The Serving API delivers a resolved theme for an Organization through a CDN, authenticated with signed URLs rather than bearer tokens.
- [Signed URLs: Authenticating Livry Theme Requests](https://docs.livry.dev/serving/signed-urls.md): Theme requests are authorised with a URL signature computed from an Application's signing key. This page documents the signing scheme.
- [Your Livry Account: Passwordless Sign-In and Teams](https://docs.livry.dev/settings/account.md): Livry accounts sign in with passwordless email or linked Google sign-in. One account can belong to multiple Teams.
- [Livry Plans and Billing: Free and Enterprise Tiers](https://docs.livry.dev/settings/billing.md): Billing attaches to your Team. The Free plan is self-serve; Enterprise is arranged through sales. Livry bills in Australian dollars.
- [Livry FAQ: Environments, Tokens, Signing, and Accounts](https://docs.livry.dev/help/faq.md): Answers to common Livry questions about environment boundaries, schema-less tokens, signed URL authentication, passwordless sign-in, and plans.
- [Troubleshoot Common Livry Issues and Error Messages](https://docs.livry.dev/help/troubleshooting.md): Resolve common Livry issues including login problems, sync failures, notification issues, and integration errors with step-by-step fixes.
- [Livry APIs: Management API and Serving API Overview](https://docs.livry.dev/api/introduction.md): Livry exposes a Management API for administering Organizations, tokens, and Applications, and a Serving API that delivers resolved themes at runtime.
- [Authenticating to the Livry Management and Serving APIs](https://docs.livry.dev/api/authentication.md): The Management API uses OAuth 2.0 bearer tokens for the api.livry.dev audience; the Serving API uses signed URLs backed by an Application signing key.