The core: PHOENIX Cloud · Overview
Updates and releases
How updates reach your site, what we do before every update, and how you hear about new features.
Because every system runs on one core, an update to the core reaches every customer, and an update to your system reaches every site that uses it. You never install anything.
Before every update
- Tested before it reaches customer sites.
- Backed up: every site is in the nightly backup, so a recent copy always exists.
- Short restart: most updates need a restart of about 30 seconds.
How features move from Coming to Available
Every feature on this site carries a status: Available, Coming November 2026, Coming 2027 or Planned. We do not show a feature as working until it works in the demo. When it ships, its badge changes to Available here and on the product page.
Hearing about changes
- This Knowledge Base is updated with every change; each page shows when it was last updated.
- What’s new, a page of release notes, is coming to this Knowledge Base.
Related pages
-
How the core works
The Hub, your site and the set-up agent: what each part does, and what happens in the minutes after a new site is ordered.
-
Backups and recovery
Backups of your site are part of the service. When they are taken, where they are kept, and how a restore works.
-
One core, many systems
Every PHOENIX system runs on the same core. What the core does, what a system adds, how we manage it, and why it matters to you.
Still have a question?
Ask the PHOENIX assistant in the chat at the bottom right, or send us a message. We reply within one business day.
