> ## 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.

# Livry Quickstart: From Sign-Up to a Rendered Theme

> Create your Livry account, define a default theme, add your first branded Organization, and fetch a resolved theme over a signed URL.

Get from signed-up to a theme rendering in your application.

<Steps>
  <Step title="Create an account">
    Sign up at the Livry developer portal. Enter your email and follow the link Livry sends you — there's no password to choose. See [Account](/settings/account).
  </Step>

  <Step title="Pick an environment">
    Your Team starts with a sandbox Tenant. Build against sandbox; keep live for production traffic. Remember that Organizations don't move between the two — see [Organizations and overrides](/theming/organizations).
  </Step>

  <Step title="Define your default theme">
    Store the tokens your interface renders with as a JSON document. Livry doesn't impose a vocabulary — use the names your design system already uses. See [Tokens](/theming/tokens).
  </Step>

  <Step title="Create an Organization">
    Each brand you serve is an Organization holding overrides on the default theme. Start with one, overriding just a colour, to see resolution working end to end.
  </Step>

  <Step title="Create an Application">
    An Application holds the signing key used to authorise theme requests. Store the key server-side. See [Signed URLs](/serving/signed-urls).
  </Step>

  <Step title="Fetch a theme">
    Construct a signed URL for your Organization, fetch it from your frontend, and map the returned tokens onto your components. See [Serving overview](/serving/overview).
  </Step>
</Steps>

<Info>
  **Worked example pending.** Each step above needs the concrete portal navigation, a real token document, and a runnable code sample before this page does its job. Written as-is it orients a reader; it does not yet get them to a rendered theme.
</Info>