Skip to content
Grails
ENES
Sign up

Engines

In the app

Know what changed, and how much it matters.

Every time you sync your library, a version is created. 30+ rules analyze each changed component, token and style, and detetrmine if it´s considered a major or minor change.

Sign up for freeGet the Figma plugin

Closed alpha: request access at no cost during the period.

Capabilities

What you can do

  • Traceability by design

    Each sync generates a version update, along with who made it, when, an optional sync note, and an auto-generated summary of what changed.”

  • The Version Enginge

    Changes in properties, variants, layers, swapped nested components, a style that drops a token for a raw value, and more. Designers don’t mark anything: the engine decides.

  • Inherited versions

    When a token changes, the components that use it get a version marked Inherited, so the effect of a change propagates across the whole system.

  • Style elements are versioned too

    Tokens, Typography and Styles get their own version as a whole, on each sync that changes them, listed under the sync’s note.

  • A changelog for the whole system

    The design system changelog shows the commit cadence, each sync with its author and note, and what was added, modified and removed.

  • Team activity

    Every action within Grails is tracked. The Overview displays an activity feed of what the team did, with search and filters by action type and author.

Everything is related

Connected to

Nothing in a design system stands alone. These are the features this one works with.

See your own design system in Grails.

Request access, connect the Figma plugin and scan a file. Nothing is synced until you start it.

Sign up for freeGet the Figma plugin

While in Alpha, we are working 1:1 with teams to improve the product. Access during this period is per-request only.