Preview for change review
Create Preview environments for GitHub projects or container images. Test changes, share the version under review with your team, and validate the result before updating the primary application.
Both paths lead to a temporary environment, but they start from different origins and keep the preparation work clear.
For projects that already live in a repository and need to review a pull request targeting a chosen branch.
The flow follows pull requests from the same repository; forks do not use this Preview.
For applications already packaged as an image and ready for Zenifra’s official publishing workflow.
The workflow is configured by your team; variables, port, and plan follow project settings.
Illustrative demo
In this example store, the next version adds an address field to checkout. Compare both versions before publishing. An illustrative interface with fictional data.
Production URL your customers access
https://loja.clients.zenifra.com
Example store / Checkout
Current version
Preview URL you access to validate your code change
https://loja-pr-2.clients.zenifra.com
Example store / Checkout
Next version
Each project has its own URL. Open the preview URL, test the new address field, and share the version with your team.
Native GitHub Previews are removed when the pull request closes. For images, configure removal in the Action workflow. The configured expiration also removes the environment automatically; an update renews that lifetime.
No. Inherited variables can point to the same database, queue, or service. Review them before testing so a change does not write to shared data.
Preview storage starts empty. If the application needs seed data, plan test data or a safe validation source.
Preview uses the primary project plan and is billed hourly in Brazilian reais. The estimate combines the number of Previews, active hours for each one, and the plan’s hourly price. Check current prices in the calculator.
After validation, publish the version through the primary project’s configured workflow. Preview is not automatically promoted to the primary application.
Team access
Organize projects by company or client, invite your team, and define the access each person needs without sharing a single account.
Invite your team to an organization and keep track of members and pending invitations.
Permissions combine a resource and an action, with configurable scope for each project.
Choose who can view and publish Previews while keeping billing access separate.
Capacity decision
Use the calculator to estimate 30 days with one API instance and one PostgreSQL instance. Choose plans and storage for your project.
Open calculator