> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to use app versioning to test changes without affecting people already using it
- URL: https://blog.jestor.com/app-versioning-test-changes/
- Published: 2026-07-12T00:32:26.000Z
- Updated: 2026-07-12T00:32:26.000Z
- Author: Bruno Bannach

Any change to an app in use — layout, automation, Kanban — can show up broken for whoever is working in it at that moment. In version **8.0**, Jestor isolates the published version (production) from the version being edited (staging), with **instant rollback** if something goes wrong.

## What is environment isolation, and why does it exist?

Environment isolation is the technical separation between what end users see (**production**) and what the builder is testing (**staging**) — the no-code platform equivalent of the staging vs. production environment concept from software development.

| Environment                | Who accesses it          | Instability risk                  |
| -------------------------- | ------------------------ | --------------------------------- |
| **Production (published)** | All app users            | Zero, locked version              |
| **Staging (being edited)** | Only those in build mode | Isolated, no impact on production |

## How to use app versioning in Jestor

- **Automatic publishing by default:** the app publishes the latest version, unless manually locked.
- **Locked version as stable:** you pin a specific version as production while testing the next one.
- **New version on every change:** each saved edit automatically generates a numbered version.
- **Instant rollback:** restore any previous version with no downtime.

**How to configure it in Jestor:** in build mode, lock the current version as stable and keep editing — the changes stay isolated until you switch which version is published.

## Why choose Jestor for this kind of control?

The key differentiator is **one-click rollback** combined with full isolation between staging and production — the end user never notices what's being tested. Built for anyone building critical operational processes, where instability has a real cost.

## Frequently Asked Questions

**What do end users see while a new version is being tested?** Only the version locked as stable; staging versions are visible only to those in build mode.

**How do I roll back to a previous version if something goes wrong?** You can restore any previous version at any time, with one click.

**Does versioning work for any app inside Jestor?** Yes, it's available for every app built on the platform starting with version 8.0.

## Reference video

Check out other practical tutorials on the [Jestor YouTube channel](https://www.youtube.com/@jestorbr?ref=blog.jestor.com).

## Get to know Jestor

With Jestor, you can automate workflows, connect departments, and build internal systems your way — all with no code and with AI support. Get to know Jestor at jestor.com and discover how to take your company's management to a new level of efficiency and integration.