Features

Everything you need to close the design–development gap.

Contracts, token translation, standards validation, multi-platform support, and team collaboration — in a single platform.

Component contracts

The single source of truth for every component.

Define every aspect of a component in one place: its props, states, variants, slots, accessibility requirements, and platform-specific specs. Contracts are the agreement that both design and development sign off on — before a single line of code is written.

Props, variants, and interaction states
Accessibility requirements per component
Platform-specific implementation notes (Web, iOS, Android)
Linked design tokens and glossary terms
Status tracking: Draft → Proposed → Agreed → Divergent

// Button contract

component: Button

status: agreed

variants:

- primary

- secondary

- ghost

a11y:

wcag: AA

role: button

focus: visible

Design token glossary

Define once. Translate to every framework.

Every design value defined once in pixels, automatically translated to 10+ frameworks. Tailwind classes, CSS variables, SwiftUI values, UIKit constants, Jetpack Compose tokens, Material UI, Bootstrap, vanilla CSS, XML layouts, and more. Rem values shown alongside pixels.

Spacing, typography, colour, border radius
Auto-generated framework translations
Manual overrides with visual indicators
Base font size preference (default 16px)
Rem, em, and px equivalents side by side

TokenTranslations

spacing-4

16px

Tailwind CSSp-4

CSS variables1rem

SwiftUI.spacer(16)

text-sm

13px

Tailwind CSStext-[13px]

CSS variables0.8125rem

SwiftUI.body

radius-lg

8px

Tailwind CSSrounded-lg

CSS variables0.5rem

SwiftUI.cornerRadius(8)

W3C standards engine

Automated compliance. Not a checklist.

Validation against the actual W3C specifications — WCAG 2.2, WAI-ARIA 1.2, HTML5, and CSS. Every contract gets a compliance score. Every audit flags specific violations with fix suggestions. Compliance is binary: it either passes or it fails.

WCAG 2.2 Level A, AA, and AAA checks
WAI-ARIA roles, states, and properties
HTML5 semantic correctness
CSS cascade and computed value checks
Violation details with remediation guidance

Button — Standards audit

94%

WCAG 2.2 AA contrast

Focus indicator visible

ARIA role: button

Minimum touch target 44×44px

Accessible name present

Multi-platform support

One contract. Web, iOS, Android.

Define a component once, then specify implementation details per platform. The glossary translates design values automatically — spacing tokens become SwiftUI padding, UIKit constraints, Jetpack Compose modifiers. One source of truth, three platforms.

Web (Tailwind, CSS, CSS-in-JS)
iOS (SwiftUI, UIKit)
Android (Jetpack Compose, XML, Material 3)
Platform-specific variant overrides
Per-platform code snippets

WebAgreed

class="px-4 py-2 rounded-lg text-sm"

iOSAgreed

.padding(.horizontal, 16).cornerRadius(8)

AndroidAgreed

Modifier.padding(horizontal = 16.dp)

Team collaboration

Role-based access. Free for collaborators.

Invite designers, developers, and QA engineers to your projects. Role-based access keeps everything organised. Only Creators are counted as paid seats — Collaborators and Viewers are always free.

Creator: full edit access, counted as paid seat
Collaborator: edit within projects, always free
Viewer: read-only access, always free
Invite by email, assign roles per project
Audit log on Organisation plan

Creator

Full access · Paid seat

Paid

Collaborator

Edit within projects

Free

Viewer

Read-only access

Free

API-first architecture

Everything accessible via REST API.

Build custom integrations, automate workflows, connect to CI/CD pipelines. API key management built into the platform. Every contract, every audit result, every glossary term — queryable via a consistent REST API.

Full REST API coverage
API key management per project
Rate limits by plan tier
MCP server for AI assistant integration
Webhook support (coming soon)

GET /api/v1/contracts

Authorization: Bearer pk_...

{

"contracts": [

{ "name": "Button", "status": "agreed" },

{ "name": "Input", "status": "proposed" }

]

}

Internationalisation

24 languages. Built for global teams.

The Parlance interface is available in 24 languages from day one. CSS logical properties are used throughout — ensuring right-to-left layouts work correctly. Built from the ground up for international product teams.