Updates
Your instance (your development server) is brought up to new Envoryx versions automatically. You do not need to install or plan anything.
What you need to know
Section titled “What you need to know”- Updates arrive on their own. You do not need to do anything.
- New versions do not reach all customers on the same day. They arrive gradually.
- After an update, the interface may be briefly unreachable. Then reload the page.
- The current version is Envoryx 0.46.0 (as of 27.10.2026).
If something does not work
Section titled “If something does not work”If you notice a problem after an update, restarting the project often helps. If that does not help, open a ticket with us (a message to support). Give the name of your instance. The steps are in the Help chapter.
How updates are rolled out
Section titled “How updates are rolled out”New Envoryx versions do not go to all instances at once, but in rings. A service from Envbay checks hourly whether a new version is ready:
- Ring 0: An internal test instance of Envbay updates first.
- Ring 1: After 24 hours, 10 % of the remaining instances follow, oldest first.
- Ring 2: Afterwards, all remaining instances receive the update, in batches of 5 instances per hour.
Between rings, Envbay checks whether the instances are healthy. If an update fails, the rollout stops and Envbay is notified. An individual instance that does not become healthy after the update returns to its previous version. This way, a faulty release does not reach all customers at once. Your instance always runs on a fixed version number, never on a moving tag such as latest.
Envoryx database migrations run automatically and only forward. Before each migration, Envoryx creates an instance backup (pre-migrate-…); going back to an older version is possible only manually. Details: Updates and versions.
Runtime images of your projects
Section titled “Runtime images of your projects”According to the Envoryx documentation, the author rebuilds the runtime images (PHP, Node.js and so on) when the official image changes, and at least weekly. A running project keeps its image until the next restart; after that, it uses the new one and shows Roll back to return to the previous state. At Envbay this daily restart is switched on: if a project has a newer image, Envoryx restarts it at 4 a.m. (a few seconds). Until then the instance shows that a restart is pending; you can also restart the project yourself earlier. The setting is fixed in the plan and cannot be changed under Settings → General → Image updates.
What you notice
Section titled “What you notice”- The interface may be briefly unreachable when the instance version changes.
- An update affects Envoryx, not the code of your projects. The author describes new features at envoryx.dev.
- As of 27.10.2026: Envoryx 0.46.0.
If you notice a problem after an update, open a ticket with a short description, your instance name and, if possible, the affected project.