Test content model changes in a staging environment
Clone your production repository, try new page types and slices on copies of your real pages, and push them live once they work. Your production website stays untouched while you test.

Test model changes against real content
An environment is a copy of your production repository, with its page types, slices, custom types, pages, and media files. Change your models there without touching what your visitors see.
Create an environment from your repository settings
Test new slices and fields on copies of your pages
Resync from production at the start of each development cycle

Switch environments from the Prismic CLI
Set an active environment and the Prismic CLI points your model pulls and pushes at it. Your local website fetches that environment’s content, and production keeps using your production repository.
Select an environment with one CLI command
Pull, change, and push your models in that environment
Switch back to production and push the tested changes

Test your next model change in staging
Talk to our team about adding environments to your Prismic plan.
Questions about environments
Features that work alongside environments
Slices
Build on-brand pages from reusable sections.
Preview
See every change before it’s live.
Releases
Schedule content to go live on time.
Media library
Create visually engaging pages fast.
User roles
Give each person the right access.
AI features
Create and update pages with the AI tools you already use.
Localization
Make your website relevant across markets.
Migration
Move your website to Prismic with your AI coding agent.