Our open-source command-line tool takes manual content updates out of your development process. Developed and copyrighted by MSQ DX and released under the MIT license, it exports a stack to files, versions them in Git and imports them into any stack, so every stack runs the same content model.
97%
Less annual labor than manual administration
84%
Less labor than custom API scripts in year one
63%
Less labor than the Contentstack CLI
Manual stack changes cost you time and put every release at risk.
Copying content types, global fields and entries between stacks by hand does not scale past one developer. Stacks drift apart, work gets overwritten and a failed deployment leaves no clean way back.
How Beacon works _
Three automated steps replace manual stack copying.
Step 1: Export
Serialize a stack's entries, assets, content types, global fields and taxonomies to files. No more copying by hand.
Step 2: Version
Commit the files to Git. Review diffs and merge without overwriting work, so every change is tracked and deployed through CI/CD.
Step 3: Import
Deserialize the stored state into any target stack. Stacks stay identical, and a previous state can be restored after a failed release.
What Beacon Delivers _
One tool gives leaders speed and engineers control.
For marketing and digital leaders
| For developers and architects
|
Beacon Capabilities _
One workflow covers every stage of a stack release.
Full stack exportSerializes entries, assets, content types, global fields and taxonomies into the file systems. |
Version-controlled content modelsStores serialized data under version control for tracking and CI/CD deployment.
|
Sync across stacksDeserializes stored data into a target stack and restores its state. |
Supports backup and recoveryCreates local backups of stack contents so earlier schema files can be restored after a failed deployment. |
Stack reset utilityRemoves all content from a stack and fits into any script or pipeline. |
Beacon Frequently Asked Questions
What platform can I use Beacon on?
Beacon is built for Contentstack, the headless CMS. It works across your Contentstack stacks and is available in the Contentstack Marketplace.
What does Beacon move between stacks?
Entries, assets, content types, global fields and taxonomies. Beacon serializes them to the file system and deserializes them into any target stack.
Does Beacon work with CI/CD?
Yes. Beacon stores stack data as files under version control, which supports automated stack deployment through your CI/CD pipelines.
Is Beacon open-source?
Yes. Beacon is an open-source command-line tool (CLI) developed and copyrighted by MSQ DX, released under the MIT license.
Who should use Beacon?
Developers on Contentstack projects, especially in fast-paced, collaborative teams, and organizations that want enterprise-grade governance and automation across their Contentstack workflows.
Where do I get Beacon?
Download it from the Contentstack Marketplace, or schedule a live demo to see it in action first.
Where can developers find the Beacon repository?
Beacon’s source code is on GitHub. Developers can review the code before they install it.