Skip to main content
Your work reaches every universe the same way: you push to Git, and the universe pulls. Nothing is pushed into a universe from outside. Reviews, approvals and protected branches all stay in your Git, where you already run them. Version history covers workflows today: every save is kept, and the History panel on the canvas restores any version. Your studio work’s history is your Git history.

​
One org, one repo

Each org is its own Git repo, and the repo IS the org: its folders sit at the root.
Make one in an empty folder. It asks for the org’s name and gives you the baseline: your tokens, your identity, Git and a pull-request check.
For examples to read and copy, clone the demo org, Acme. A universe can hold several orgs, each pulled from its own repo. Two orgs may each have an app called chat. A node type is one per platform, so give a node you copy your own type.

​
Connecting a universe to your repo

An admin connects the org once, on its Source tab in the universe (Connect a repo). A push then reaches the universe in seconds. Without the webhook, the universe checks every five minutes, and Sync now pulls at once. Before applying anything it runs the same checks your pull request ran, and if anything fails it applies nothing and keeps serving the last good version. To roll back, revert in Git, or point production at the previous tag. Workflows are not in Git yet. Moving one from UAT to production today means rebuilding it on the production canvas. Publishing a workflow to your repo is planned.

​
What never moves

Data stays in the universe it was made in, whichever way you run.
  • Content and your Spatial map. Each universe ingests its own. UAT and dev take a safe test set; production takes the real content. Real data never leaves production, and a map is never copied: the same content ingested twice gives a different map.
  • Conversations, memory and traces.
  • Credentials. Secrets are entered in each environment. A secret that has been in a test environment is a test secret.

​
Day-two operations

Once a universe is running, the routine work is small and each piece has a runbook. Your work is not in that list. It reaches a universe from your repo and needs no platform deployment.

​
Next steps

Runbooks

Upgrade, migrate, back up and roll back a running universe.

studio

Make an org repo and build what your universe pulls.