Skip to main content

June 2026

Per-deployment monitoring​

Every deployment now has a Monitoring tab with CPU, memory, and HTTP response time for its container, plotted over a time range you choose. Metrics are sampled continuously and kept for 30 days.

This is the fastest way to tell an application bug from a resource problem: a memory curve climbing toward the limit explains a container that keeps dying far better than a traceback does.

Build log viewer​

Logs are now split by source, so you can jump straight to the output you need instead of scrolling one merged stream. A selector switches between the runtime log of the running instance, the module installation output, the update output, and the test output.

You can also narrow the view to a date range, and build logs remain readable after the deployment has finished, and even after it is removed.

See View Logs.

Control what development builds install and test​

Development branches gained build settings so a branch build does what your workflow actually needs:

  • Module installation. Install every Odoo module found in the repository (the default), or list exactly the modules you want installed on the development database.
  • Tests. Filter which tests run after installation using test tags, or run the tests of the selected modules only.

See Branch Types.

Development deployments are removed after 24 hours​

Development deployments are now clearly marked as temporary: their database is removed 24 hours after the build, and the dashboard warns you while the deployment is still running.

Pushing again rebuilds the branch from scratch, so a development instance is always a fresh environment rather than a long-lived one holding data you were relying on. Use a staging branch for anything you need to keep.

Custom domains and SSL moved to the branch​

Domain settings now live on the branch they apply to, rather than in a separate project-wide list, so it is clear which deployment a hostname serves.

HTTPS is always enabled for custom domains. The former toggle is gone: certificates are provisioned and renewed automatically, and there is no reason to serve a production site without them.

See Add a Custom Domain.

Environment variables and deployment settings​

  • Environment variables are managed per environment, so development, staging, and production can carry different values for the same variable.
  • Request timeout. A new project setting caps how many seconds a single request may run before Odoo aborts it. Leave it at 0 to use Odoo's default. It applies from the next deployment onward.
  • Webhook status. Project settings now show whether the Git provider webhook that triggers automatic builds on push is registered, and under which provider ID.

Faster and clearer backup imports​

Backup uploads now go directly to storage rather than through the dashboard, which makes importing a large Odoo backup substantially faster and far less likely to time out.

Imported backups are labelled as such in the backup list, so an archive you brought in from another host is easy to tell apart from one Skysize created. The backup list also refreshes on its own as operations complete, with no page reload.

See Manage Backups and Import an Existing Odoo Backup.

Project invitations​

Invitations now have their own page. An invitation link opens a dedicated screen rather than dropping you into the dashboard, and an invitation addressed to somebody else shows a clear message instead of a generic error.

See Manage Users and Groups.

Smaller improvements​

  • Deployment list. Deployments are ordered newest first across all branches, and the filters on the project page now work as expected.
  • Clearer build states. Queued builds show as "queued" rather than an unknown operation, and import completion reports success correctly.
  • Storage usage. The storage breakdown reports backup totals in the correct unit and classifies deployments by their branch type.
  • Payments. Your primary payment method is preselected, and errors returned during payment or subscription changes are shown in full instead of a generic failure message.
  • Free tier. Features that require a paid plan are now consistently marked across the dashboard. See Free Tier.