Hey Team,

The new Qovery console is coming on May 11, and you can already try it today. A preview banner is live at the bottom of the current console: one click and you are in. We have been rebuilding the entire UI from the ground up, and this is your chance to explore it before it becomes the default for everyone. Do not wait for the rollout to discover it.


New console: preview now open, live on May 11

The new Qovery console has been in the works for a while, and it is now available for early access. A banner at the bottom of the current console invites you to switch and try it out before the official rollout on May 11.

The redesign is not a facelift. The entire navigation and UX has been rethought from the ground up to reduce friction for teams managing multiple projects and environments. Key additions include a new organization overview that gives you a single-pane view across all your projects, a native dark mode, and a modernized interface that better reflects how teams actually use the platform day to day.

If you find something that feels off during the preview period, now is the right time to flag it. Try the new console


CLI: filter logs by service with --service

Running qovery logs on a deployment with multiple services used to mean scrolling through a combined stream to find what you actually needed. You can now pass --service to scope the output to a specific service directly from the command line. This is particularly useful in CI pipelines and during incident triage where you need fast, targeted output without opening the console. See CLI docs


Minor updates

  • Terraform deployment failures: clearer PVC storage errors: When a Terraform deployment fails because PVC storage is insufficient, the error message now surfaces that root cause explicitly instead of showing a generic failure. This saves time during incident investigation on clusters with constrained storage.
  • SAML / Auth0: IdP group names with unsupported characters: Fixed a bug where certain IdP group names caused SAML authentication to fail. Teams using SSO with group-based access control should no longer encounter this.

The main action item from this release: try the new console before May 11 and share any feedback early. The preview banner is live for everyone, and the team is actively monitoring for issues before the full rollout.

Talk soon, The Qovery Team