Core concepts

A handful of nouns carry most of Klyo. Learn these and the rest of the app reads easily.

Organization

The tenant. Everything you do happens inside one Organization, and an Organization never sees another Organization's data. It owns its own Cloud Storage bucket, its own templates, its own members, and (once onboarded) its own Google Cloud project for running generation. You can belong to more than one Organization and switch between them.

Catalogue item

A reusable piece of a creative: a product, a customer segment, a city, a message. Catalogue items live in catalogues, which are just named lists you define (for example "Segments" or "Products"). A catalogue item fills the fields its list declares, carries a description that also steers the prompts that use it, and can link to assets. Catalogue items are the raw material the matrix is built from. See Catalogues.

Campaign and the matrix

A campaign holds a brief and points at exactly one template. You choose axes for it, where each axis is one of your catalogues, and Klyo multiplies the axes together into a matrix of every combination. You can drop combinations you do not want with exclusions. The matrix preview tells you how many valid combination packages you would get before you commit. See Campaigns.

Template and template version

A template is a Creatomate video or image template, mirrored into Klyo as a parsed manifest: its slots, fields, and transitions. Templates are read-only in Klyo; you change them in Creatomate and sync. Every structural change publishes a new immutable template version, so you keep a history of what the template looked like over time. See Templates.

Combination Package and freeze-at-render

A combination package is one cell of the matrix made real: one template filled with one valid combination of catalogue items. You produce combination packages by expanding a campaign. Expansion is repeatable: run it again and Klyo only adds what is new.

The key rule is freeze-at-render. While a combination package is still being configured, it follows the latest template and matrix. The moment it is rendered, its output is frozen. A later edit upstream never silently re-renders it. Producing a new output is always an explicit step. Rendering itself can mean a shared clip composed with per-cell catalogue items, or a video generated fresh for that one combination; see Generation and render for which applies. The Render Queue is where you watch every combination package on its way to a Final Video. Once that Final Video is approved, the combination package can be activated. See Render Queue.

Activation

The last stage: getting an approved Final Video out to a channel. You connect a channel once on the Organization page's Connections tab (owned YouTube, Google Ads, or DV360), pick an activation target on the Template step, and push approved combinations from the Activation queue. Before the push, the Publishing step sets how each video publishes: a title that fills in per combination, the description, tags, and privacy. A creative can also be hosted first: uploaded to your YouTube channel unlisted with nothing released, so a later push or handoff pack reuses that upload. The builder's Hosting step walks this ahead of the queue. An owned-YouTube target uploads automatically; it serves once you set its visibility in YouTube Studio. A Google Ads or DV360 target hands off a downloadable pack you finish in that tool. Every push records where the creative landed, so measurement can trace back to it. See Activation and Channel connections.

Asset

A file: an upload, or something Klyo generated. Assets live in a folder tree over your Organization's Cloud Storage bucket. Generated assets are system-managed and read-only, which is freeze-at-render showing up at the storage layer. See Assets.

Action

The audit unit. Every change you make (create a campaign, sync templates, invite a member) is recorded as an Action with who did it, what it touched, and how it ended. Actions power the activity feed, the failure console, and notifications. See Activity and failures.

Roles and platform admin

Inside an Organization your role (admin, member, read-only) decides what you can change. Separately, a platform admin is a Digitl operator (the team that runs Klyo) who can see across Organizations to onboard clients and watch for failures. The two are independent: a platform admin still acts inside one Organization at a time. See Organizations and members and Administration.