Store your entire design system in the cloud and work on it with your team. A new collaborator can check out a ready-to-run project without finding a repository or copying files by hand. Token edits merge on their own, components version without ever clobbering someone's work, and conflicts resolve with a single click, including a semantic AI merge. Available on Pro and Enterprise.
Start on a New Machine
Cloud Project checkout gives every teammate the same starting point. It downloads the latest project source from main, verifies every file, restores the current token and component state, installs the project's dependencies, and opens the project in Spektral.
Publish the starting point
A project owner signs in, opens the project on main, and selects Sync. After token and component sync completes without conflicts, Spektral publishes the latest project source as the team's checkout snapshot.
Check out the project
A collaborator signs in to the same team, selects Cloud Project on the welcome screen, chooses the project and a parent folder, and waits while Spektral prepares and opens the local workspace.
owner: main → Sync → cloud checkout is ready
teammate: Cloud Project → choose project → choose folder
→ verify files → restore sync state → install dependencies → openIf a project is marked Not published, someone with a local copy needs to open main and complete one successful sync first.
Git Is Optional
Cloud Project checkout is not a Git clone and does not require a Git host, repository URL, or access token. Spektral carries the project source needed to work in the desktop app, while its own branches, change requests, releases, and live sync are managed by Spektral. Your team can still use Git alongside Spektral for source control, CI, or wider engineering workflows.
Git branches and Spektral cloud branches are independent: using both does not mirror names or couple checkouts. The desktop Git chip keeps repository status and GitHub pull requests close at hand. With GitHub CLI installed and signed in, Spektral can create a pull request directly; otherwise it pushes and opens a compare link in your browser.
What Moves Between Machines
Included
Tokens, component source and stories, specs, platform configuration, package manifests, scripts, documentation, and other project source files.
Kept local
Secrets such as .env*, .dev.vars, and .npmrc; Git metadata; dependencies; build output; coverage; and machine-local .spektral state. Each collaborator supplies their own local credentials where needed.
Everything Stays in Sync
Sign in to Spektral on the desktop app and your design system syncs with your team automatically, no commits, no branches, no merge commands. You keep editing exactly as you do today; a teammate's changes flow in on their own, and yours flow out. The cloud is the source of truth, and what's on your machine is a working copy that catches up to it.
You edit a token or a component ↓ syncs to the cloud automatically ↓ your teammates' apps pull it in real time ↓ everyone converges on the same design system
Tokens Just Merge
Design tokens never show you a conflict dialog. If you change a color while a teammate changes the spacing scale, both edits land, Spektral merges them automatically. If two people touch the very same token, the most recent edit wins, consistently, on every machine. It's built on a conflict-free merge model, so every client is guaranteed to arrive at the same result no matter what order changes show up in.
No conflict prompts
Different tokens edited at once? Both apply. There's nothing to resolve.
Deterministic
The same token edited twice resolves the same way everywhere, no drift between teammates.
Offline-friendly
Edit offline; your changes reconcile cleanly the next time you're connected.
When Two People Edit the Same Component
Component code has to compile, so Spektral never blindly merges two versions of a file. Each component is versioned as a whole. If you and a teammate both change the same component at the same time, Spektral catches it and asks how you'd like to reconcile, it will never silently overwrite anyone's work. You get three choices:
Keep theirs
Take your teammate's version. Preview it first, then adopt it, yours steps aside.
Keep mine
Keep your version and publish it as the next one. Their change stays in the history.
Rebase with AI
Let Spektral re-apply your change on top of their current version, a real merge of intent, not lines.
Merge with AI, Not Line Numbers
Rebase with AI is the part that makes component conflicts painless. Instead of a line-by-line merge that leaves you untangling <<<<<<< markers, Spektral takes your teammate's current component and re-applies the change you were making, the way you'd have written it against their version if you'd started from there. It reads both sides and produces one coherent component that still compiles. The kind of merge a person would do by hand, done for you.
Their version (current) + your change → one merged component reads both, keeps their structure, re-applies your intent runs the usual token & accessibility checks
In Real Time
When a teammate saves, you see it, the app syncs the moment their change lands rather than on a timer. A live indicator in the header shows when you're connected to your team. If the connection drops, Spektral keeps everything current by checking in on a short interval, so you never miss a change; reconnecting just makes it instant again.
Where Your Work Lives
Your design system is stored on your team in Spektral's cloud, the latest project checkout, token history, and every component version, with files kept as de-duplicated, content-addressed blobs so identical content is stored once. Editing happens in the desktop app; the browser is for viewing and review. Because the cloud is authoritative, a teammate can create a fresh working copy from the welcome screen and continue from the current main state.
Portable
Collaboration runs on Spektral's cloud out of the box. For teams that need everything inside their own perimeter, the same sync, versioning, and real-time model runs self-hosted against your own database and storage, no third-party services required.
Getting Started
On Pro or Enterprise, sign in to the desktop app and open an existing local project to publish it, or select Cloud Project to check out one your team has already published. Free plans continue to work entirely on your own machine; cloud checkout, sync, and collaboration require Pro or Enterprise.