Updates and maintenance
Updates are our job, not yours. Nothing to click, nothing to migrate, no release notes to read, unless you want to.
Tried first#
Every new version runs on an instance of ours first, never on your app. Only once it starts cleanly and is reachable there do we release it. That costs a few days, and in exchange no update reaches you that we have not seen ourselves.
When it happens#
At night, at 3 a.m. in your app’s region. The app is briefly unreachable while it happens, usually seconds, at most a few minutes.
Notice#
When an update is coming that concerns you, we send an email beforehand. Whether you want those messages is set per app under SettingsGeneral.
Stopped apps#
A stopped app is brought up to date at its next start, not before.
Careful
So do not leave one stopped for months. The more versions an app skips at once, the more likely something breaks on the way.
Security#
Updates that close a security hole take priority over the usual rhythm.
When something is different afterwards#
New versions sometimes change how an app looks or what it can do. That is decided by the people who build it, not by us. What changed is in the project’s release notes. If the app does not start at all after an update, write to us, ideally with a look at the log.
Was this page helpful?