4 min read
CMS Orbit now speaks PHP, Swift and Kotlin
Laravel and Symfony websites and native iOS and Android apps get official SDKs too. All four are typed, open source and read the same content.
CMS Orbit CLI
npx cms-orbit covers what developers do outside the editor. Keep content types and components in your repository, move content and media as files, run migrations with a dry run first and start a website from a starter, signed in as you with your own role.
A session with Northwilds
Sign in in the browser, write the schema to files, add a field, see the change and push it. Then pull the trips as JSON and try a migration without saving anything.
--publish$ npx cms-orbit loginSigned in to https://app.bifrostorbit.com/cms as Ingrid Lund (ingrid@northwilds.com).$ npx cms-orbit schema initWrote 12 content types and 34 components of Northwilds to cms/schema.# Add a season field to cms/schema/components/trip-hero.ts$ npx cms-orbit schema diffComponents ~ trip-hero (Trip hero) + field season (select)0 to add, 1 to change, 0 to remove.$ npx cms-orbit schema pushApply 1 change to Northwilds? [y/N] yApplied 1 of 1 change.Undo with: cms-orbit schema rollback 2026-11-15T09-30-00-000Z-schema-push$ npx cms-orbit content pull --folder tripsPulled 32 entries into cms/content.$ npx cms-orbit migrations run cms/migrations/2026-11-15-hero.ts --dry-runDry run: 9 of 41 entries would change for the hero component. Nothing was saved.Every command
One command line for the schema, content, media, taxonomies and migrations of your spaces. It comes with the JavaScript SDK from 0.16.0, and runs with npx.
Signed in as you
cms-orbit login opens CMS Orbit's sign-in in your browser. You sign in as you always do, check what the command line asks for and select Allow. From then on it can do what you can do, in every organisation you belong to, with your role's permissions there.
What it changes is recorded as you, marked "(command line)", in the audit log and in each page's history. It renews itself each hour while you use it, ends after 30 days without use, and you can sign out any computer under Your account.
Schema as code
schema init writes each content type and component as a TypeScript file, typed so your editor completes the settings and field types. Change the schema in the same commit as the components that render it, and review both together.
types generate --from cms/schema writes the types from the files themselves, so they follow the schema before you push.
import type { CmsComponentDefinition } from "@bifrost-orbit-cms/sdk";export default { key: "trip-hero", name: "Trip hero", group: "Trips", fields: [ { key: "heading", name: "Heading", type: "text", required: true }, { key: "season", name: "Season", type: "select", options: [{ label: "Summer", value: "summer" }, { label: "Winter", value: "winter" }] }, { key: "photo", name: "Photo", type: "asset" }, ], mainHeading: "heading",} satisfies CmsComponentDefinition;Safe by default
Migrations
migrations generate hero writes a script for a component or content type, with its fields typed. Your function gets every block of that type, at any depth, and returns it changed.
run --dry-run shows each entry's changes and saves nothingrollback last puts the drafts backexport const target = { component: "hero" } as const;export default function migrate(block: Block<HeroFields>): Block<HeroFields> | null { if (block.fields.size === "large") block.fields.size = "full"; return block;}Start a project
Starters
Each starter is the finished code of a quickstart in the docs. The command points it at your space, and asks which framework when you don't say.
Scripts and CI
Questions
No. It comes with the JavaScript SDK, @bifrost-orbit-cms/sdk, from version 0.16.0, so npx cms-orbit runs it straight away. To pin a version, add the SDK to your project and call it from your package.json scripts. It needs Node.js where you run it, not in your website or app, so PHP, Swift and Kotlin projects use it too.
What the person who signed in can do, with their role's permissions in each organisation they belong to. If their role changes, so does what the command line can do. Every change is recorded as them, marked (command line), in the audit log and in each page's history. Creating management tokens and handing over an organisation stay in the browser.
Content commands work on Staging unless you pass --environment production, and they save drafts: nothing goes live unless you pass --publish and your role may publish there. The schema is shared by every environment of a space, so schema push shows the changes and asks first, refuses to drop fields that hold content unless you pass --allow-destructive, and saves a snapshot that schema rollback puts back.
Yes. Create a management token and set it as ORBIT_TOKEN; a token always comes before a stored sign-in. --yes applies without asking, --json prints only JSON, and schema diff --exit-code fails the build when your files and the space differ. Requests that meet 429 or 503 are tried again, and every change carries an Idempotency-Key, so a retried change is made only once.
Under Your account in CMS Orbit, each computer where you ran cms-orbit login is listed with when it was last used. Sign it out there, or choose Sign out everywhere. Owners and administrators see everyone's command-line sign-ins on the organisation's Management tokens page. A sign-in that isn't used ends by itself after 30 days.
From the blog
4 min read
Laravel and Symfony websites and native iOS and Android apps get official SDKs too. All four are typed, open source and read the same content.
3 min read
Show editors their draft on the real website, updating as they type. Here are the four small pieces your website needs, and what each one does.
4 min read
How CMS Orbit keeps content right: reviews on every plan, approval steps and review dates on Growth, approved claims, emergency publishing and a record of every change.
Start a trial, run npx cms-orbit login and write your space's schema to files. The trial is free for 14 days.