Connections
Connect a service once. Every satellite uses it.
Keep your files in your own bucket, pick images from Cloudinary, Bynder or Frontify, post to Slack or Microsoft Teams and deploy on Vercel or Netlify. An owner or admin connects each service once in Orbit, and every satellite that has a use for it works with it.
There is nothing to install and no plugins to keep up to date.
- Your own bucket
- Cloudinary
- Bynder
- Frontify
- Slack
- Microsoft Teams
- Vercel
- Netlify
- Shopify
- Phrase
- Lokalise
- Smartling
- Algolia
How it works
From keys to working in four steps
You keep your own account with each service, and Orbit connects to it. One connection reaches every satellite that has a use for it.
- Open ConnectionsAn owner or admin opens the organisation in Orbit and chooses Connections. Every service is listed with its status and the satellites that use it.
- Fill in the detailsThe address, account name or keys the service gives you. For Slack, add the Bifröst Orbit app to your workspace and pick a channel.
- Test and connectOrbit runs a real check first, such as writing and reading a test file or posting a test message, and only saves a connection that works.
- Every satellite uses itMedia pickers, notices, deploys and fields that need the service pick it up. There is nothing to switch on in each satellite.
In the apps
Set up in Orbit, used where your team works
Connections sits in Orbit, next to your members and sign-in, so a service is set up once for the whole organisation instead of in every tool.
Orbit › Connections
Every service in one place
Owners and admins see every service with its status, and connect, test or change it there.
- Status at a glance: each service shows Active, Failing or Not connected, and a failing one says what went wrong.
- Where it is used: each row lists the satellites that use the service and where the service keeps your data.
- Part of the product: there are no plugins to install, update or switch on in each satellite.
OrbitConnectionsMedia libraries
Pick files from the library your brand team already uses
Connect Cloudinary, Bynder or Frontify and every media picker in CMS Orbit, Travel, Commerce, Booking and Presence Orbit gets From a library, and so does Careers Orbit's uploads picker. The library's own picker does the browsing, so search, folders and permissions work as your team knows them.
Files are linked, not copied: websites get the library's own address and sizes, and an edit in the library shows wherever the file is used.
CMS OrbitMediaSlack and Microsoft Teams
Tell the team in the channel they already read
Review requests, review decisions and releases are posted to a channel such as #trips-team, and Orbit Flows gets a Post to Slack step. Microsoft Teams gets the same notices and flow step through a Teams workflow in the channel.
Messages hold a title and a link, never the content.
OrbitConnectionsVercel and Netlify
Publish, and the website rebuilds
CMS Orbit starts a deploy about a minute after publishing, for each environment you choose, and shows how it went. Many publishes within that minute start one build.
It works the same for websites on Vercel, with a deploy hook, and on Netlify, with a build hook.
CMS OrbitWebsite code
Your own bucket
Your files in your own account, on every plan
Every file your team uploads in any satellite, from images in CMS Orbit's media library to trip photos in Travel Orbit and CVs in Careers Orbit, can be kept in a bucket your organisation owns. Any S3-compatible storage works: AWS S3, Cloudflare R2, IONOS, Hetzner, Wasabi and others. It's on every plan, Starter included.
- Nothing changes for your websites: files keep their addresses and are still served through our image cache, which makes the smaller sizes and modern formats. Your bucket can stay private.
- Move what's already there: Move existing files copies them to your bucket in the background and checks each one before the copy with us is removed. Move back does the reverse.
- Never saved somewhere else: if the bucket stops working, uploads stop with a clear message instead of landing anywhere else.
- Nightly backups, from Growth: each satellite on Growth or higher writes a copy of your content as JSON to
backups/in the bucket every night, kept for 30 days.
Services
Works with the services you already use
Your own S3-compatible storage on every plan, and media libraries, chat, hosting, Shopify, translation and search from Growth. You keep your own account with each service, and Orbit connects to it.
- Every planStorageYour own bucketUploads from every satellite in your own S3-compatible bucket: AWS S3, Cloudflare R2, IONOS, Hetzner, Wasabi and others. From Growth, nightly backups of your content go there too.
- Growth and upMedia librariesCloudinaryBynderFrontifyBrowse your library in its own picker from every media picker. Websites get the widths and formats they ask for, made by the library.
- Growth and upNotificationsSlackMicrosoft TeamsReview requests, review decisions and releases posted to a channel, and a step in Orbit Flows to post there.
- Growth and upPublishingVercelNetlifyCMS Orbit starts a deploy about a minute after publishing, for each environment you choose, and shows how it went.
- Growth and upCommerceShopifyPick products from your shop in a page. The delivery API fills in the current title, price, image and link from Shopify.
- Growth and upTranslationPhraseLokaliseSmartlingSend a page or a folder to your translation service and bring the translation back as drafts in the other language. No translation service? Download XLIFF 2.0 for your translators and upload the translated file.
- Growth and upSearchAlgoliaPublished pages kept in an Algolia index for each environment and language, updated as you publish, with a button to rebuild it.
Plans
Your own bucket on every plan, the rest from Growth
Plans are per satellite. You can connect a service when at least one of your satellites is on Growth or higher, and each satellite uses it while that satellite is on Growth or higher. On Starter the buttons stay visible and say Growth and up.
- Every plan, Starter includedYour own S3-compatible bucket for the uploads of every satellite, with Move existing files and Move back.
- Growth and EnterpriseCloudinary, Bynder, Frontify, Slack, Microsoft Teams, Vercel, Netlify, Shopify, Phrase, Lokalise, Smartling, XLIFF files, Algolia and nightly backups to your bucket.
- CMS OrbitGrowthYour own bucketCloudinarySlackVercel
- Commerce OrbitGrowthYour own bucketCloudinarySlack
- Travel OrbitStarterYour own bucketCloudinaryGrowth and upSlackGrowth and up
Safe by design
Your keys stay yours
- Encrypted, never shown againKeys, secrets and tokens are encrypted when you save them and never sent to the browser. Orbit shows only their last four characters, and you can replace a secret but not read it.
- Checked before savingEvery connection runs a real check first: a test file written, read and deleted, one asset fetched or a test message posted. If it fails, Orbit says why in plain words.
- In the audit trailConnecting, changing, testing and disconnecting are recorded in the organisation's audit trail with the person who did it.
- Owners and admins decideOnly owners and admins connect, change or disconnect a service. Everyone else uses what's connected.
- No private addressesAddresses on private or internal networks are refused, and so are plain http:// addresses. Teams only takes workflow addresses on Microsoft's own domains.
- Disconnect without losing filesDisconnecting deletes the keys from Orbit and nothing in your bucket. A bucket that still holds files can't be disconnected until you move them back.
Questions
About connections
Do we need to install anything to connect a service?
No. Connections are part of Bifröst Orbit, not plugins. An owner or admin connects a service once in Orbit, under Connections, and every satellite that has a use for it works with it. There is nothing to install, update or switch on in each satellite.
Which plans include connections?
Your own S3-compatible bucket is on every plan of every satellite, Starter included. Every other service needs Growth or higher. Plans are per satellite: you can connect a service when at least one of your satellites is on Growth or higher, and each satellite uses it while that satellite is on Growth or higher.
What happens to our files when we connect our own bucket?
New uploads in every satellite go to your bucket, each satellite in its own folder. Files keep their addresses and are still served through our image cache, so the bucket can stay private. Files uploaded before stay with us until you choose Move existing files. Disconnecting deletes the keys from Orbit, never anything in your bucket.
Can anyone read our keys after we save them?
No. Keys, secrets and tokens are encrypted when you save them and never shown again: Orbit shows only their last four characters. Every connect, change, test and disconnect is recorded in the audit trail with the person who did it.
Are files from Cloudinary, Bynder or Frontify copied into Orbit?
No, they're linked. Each file appears in the satellite's media library with the library's address, name, size and alt text when it has it, works in every image field and doesn't count towards your storage. Websites get the library's own address and sizes, and an edit in the library shows wherever the file is used.
Connect what you already use.
Start a trial, connect your own bucket on any plan and try the other services on Growth. The trial is free for 14 days.