3 min read
Deleted by mistake? How CMS Orbit lets you undo it
Deleted the wrong page or published the wrong words? The bin, version history and audit trail make it easy to put right, and permanent deletion rare and deliberate.
Trust centre
Organisations that answer for what they publish need to know where their data lives, who can reach it and what happens when something fails. Here is how Bifröst Orbit looks after it, what you can count on when something goes wrong, and how we test it.
At a glance
Open
The code, packages and API documents anyone can read, without asking us.
Security
Deletion
Deleting a page, file or website moves it to the bin, where it can be restored. By default, only the Owner can erase anything for good, and deleting a whole organisation has to be confirmed in Orbit before anything is erased.
AI agents
An agent acts for one person and never has more rights than they do. It can't publish, change protected prices or settings, or read the audit trail, and every page change it makes needs a person's approval.
Resilience
Bifröst Orbit is designed to keep services available when infrastructure or individual applications run into problems. Automatic failover, database replication, independent satellites and resilient event delivery keep the platform running when something goes wrong.
If this happens
The things most likely to go wrong, and what you would notice.
Commitments
What each case means for your data, and how we make sure it holds.
What it means
Seconds of data at most, because the standby has every change as it happens. Back within minutes, automatically.
How we check
We switch servers off in production on purpose, every quarter.
What it means
Back from the most recent backup: at most an hour of changes.
How we check
Backups are restored on a separate machine and the apps started on them, every month.
What it means
We work to 99.9%, about 45 minutes a month. Enterprise customers can have it in their contract, with service credits.
How we check
Checked from outside every minute, and shown on the status page.
Drills
A plan that hasn't been tested is a hope. We switch things off in production on purpose, watch what happens and fix what we find.
Data protection
We use a few providers to run the service. What each one does, where and under which safeguards is on the sub-processors page.
Environment
What our hosting provider, IONOS, reports for its own data centres, and how we keep our own share small.
Accessibility
We aim for WCAG 2.2 AA on the website, in the docs and in every app, in light and dark mode, and check every screen with automated tests in both.
Bifröst Orbit takes security seriously, tests continuously and keeps improving. Security isn't a one-off exercise: we keep checking the platform for weaknesses and fix what we find.
We believe security belongs in the way a platform is designed, built and run, not added afterwards. If you find something we missed, tell us below.
If you find a vulnerability in Bifröst Orbit, email security@bifrostorbit.com. A person on our team reads every report. You can also use Report a vulnerability on any of our public repositories on GitHub, and our security.txt lists the same address.
We won't take legal action against research that follows these rules in good faith.
From the blog
3 min read
Deleted the wrong page or published the wrong words? The bin, version history and audit trail make it easy to put right, and permanent deletion rare and deliberate.
4 min read
Where your data lives, who can get in and what happens when something goes wrong, with links to the privacy policy, data processing agreement and sub-processors.
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.
Send us your security questionnaire, or tell us what your organisation needs to know, and we'll answer it.