About Environments

A publishing environment is a specific destination where your content (such as entries or assets) is delivered when published. Environments act as distinct channels tailored to specific publishing needs.

For example, you can use environments to preview content on an internal channel, such as a staging or pre-production website, accessible only to authorized users.

Organizations have complete control over the environments they create and how they use them to align with their requirements and workflows.

Note: Environments are global modules available across all branches of your stack. Any environment created in the main branch is accessible in all other branches.

With Contentstack, you can publish content across multiple environments.

For example, if your website has development and production environments, you can publish your content in the development environment to preview it before publishing it live in the production environment.

Note: Content published in Contentstack doesn't automatically appear on your website or app. Your website or application must have specific code to fetch this content from Contentstack.

In Contentstack, you can create specialized publishing environments customized for specific channels or purposes, such as mobile apps or social media.

Note: Contentstack's Automate and Webhooks can automatically publish your content to social media platforms, simplifying content distribution.

You can use Webhooks to deploy published content simultaneously across multiple servers within a single publishing environment.

Imagine your company runs a website on several servers in different regions, like the US, Europe, and Asia. When you publish new content in an environment, webhooks instantly alert all servers. This triggers each server to fetch and deploy the content immediately, ensuring efficient and synchronized global updates.