Skip to main content

Model and vocabulary

One brand: a flat map of token path to value, layered on a Theme. It owns values and nothing else — it cannot add, rename, retype or describe a token. See Variants.
Nothing. They are names from earlier versions of the product.Tenant → Environment. Organization → Variant. Application → nothing at all; signing keys belong to a Theme. See the Glossary.
No. Nothing moves between Environments and nothing auto-promotes — that is what makes the isolation real. Script the copy against the API as part of your own release process. See Environments.
Livry has no mode concept. Either put both sets of tokens in one Theme and select between them in your own CSS with prefers-color-scheme, or use two Themes, each with its own Variants. See Importing tokens.

Tokens

No. There is no fixed list of names, and nothing in Livry knows that color.brand means a brand colour. What Livry does impose is the format — W3C DTCG — because that is what makes typing, aliasing and import-from-anything work.
No — it has no vocabulary to check them against. A typo is stored faithfully and shows up as a missing custom property at render time. Always write a var() fallback.
Alias aggressively. If every derived colour is {color.brand} rather than a literal, a brand can rebrand your whole product by setting three values instead of three hundred. See Tokens.
Yes — DTCG, Tokens Studio, Figma Variables and Style Dictionary, detected automatically. Figma takes one mode and Tokens Studio takes one set, and both report what they did not take. See Importing tokens.
They are preserved but never applied. A document that relies on either imports with tokens missing, silently. Use aliases instead.

Serving

No. A new Theme is public, and a public Theme ignores a signature if one is present. Signing is opt-in per Theme. See Signed URLs.
Theme fetches happen in the browser, at volume, and need to be cacheable at the edge. A bearer token would either be exposed client-side or force every request through your own backend.A signed URL can be computed server-side, handed to the browser safely, and cached like any static asset — because holding it is the credential.
latest in sandbox; pinned in production if you want a theme change to ship like any other change, latest if you want publishing to reach users without a deploy. See Caching.
A few seconds for the files to be built, then up to your Environment’s cache lifetime (60s by default), plus up to 5 minutes more if a reader is served stale while it revalidates.Pinned URLs appear as soon as the build finishes and are never stale.
Almost always because the Theme has never been published, or because it does not serve that file. See Troubleshooting.
Not yet. See What is not built yet.

Access

Correct. A Team role grants nothing inside an Environment. Grant them the Environment as well. See Roles.
Not with Livry’s own roles — the finest scope is an Environment role, deliberately. Build a reseller-facing editor against the API with your own authorization on top.
Not properly yet. Machine credentials are not issuable, so the API is reachable only with a user-backed token. See Authentication.
Yes. Accounts and Teams are separate; switch between Teams inside the portal.
There is no password — sign-in is passwordless. Enter your email and follow the code Livry sends. If you have lost access to the email address itself, contact support.

Plans

Free is A0,Prois∗∗A0, Pro is **A9.99/month**, Enterprise is arranged with us. Billing is in Australian dollars and attaches to the Team. See Plans and limits.
There is no in-app upgrade today. Get in touch and we will arrange it — support@livry.dev.
Nothing is deleted. While the provider is retrying, you keep your plan; if it gives up, you fall back to Free limits — existing Environments, Themes and Variants keep working and serving, but you cannot create more.
Not today. The pricing axes are Variants, Environments and Themes.

Still have a question?

support@livry.dev. Livry is early and support is async — if you are evaluating it for something with a deadline, read What is not built yet first.