Skip to main content

October 2026

A public REST API​

Your own scripts, CI pipelines and business tools can now operate your Skysize projects through a REST API: trigger a rebuild after a merge and follow it until it finishes, read logs, metrics and the audit log, take a backup before a risky change, change environment variables, or create a new SaaS database on demand and get its address back.

Create a token under Account > API Tokens, choose REST API, and pick an access level: Read only (preselected), Read and write, or Full. Send it in the X-API-Token header. Each token only does what you could do yourself in the dashboard, and is limited to 120 requests per minute.

The REST API is available on paid plans. See Use the REST API, and the API reference for every endpoint, now linked from the top of these docs.

API Tokens page, and Claude in one click​

The Account > AI Agents page is now Account > API Tokens, since the same page creates tokens for the REST API and for AI agents (MCP). Old links still lead there.

A new Add to Claude button opens Claude's connector settings with Skysize already filled in. Confirm, approve the request on the Skysize consent page, and claude.ai or the Claude apps can read your build results, logs, slow queries and metrics. No token to copy.

See Connect an AI Agent (MCP).

The Maintainer role​

A new project role sits between Developer and Admin. Maintainers see everything and have full control of staging, but cannot touch production: they read every log and health detail, log in as any Odoo user (recorded in the audit log), take and download backups, and rebuild, restore or import into staging branches. It is built for junior developers, functional consultants and internal staff who need a place to test an Odoo upgrade or an older backup.

See Access Management.

Odoo image updates​

Skysize rebuilds the Odoo images every week from the latest upstream commits of your Odoo version, so security and bug fixes reach you without touching your code. The Odoo image card on production and staging shows the build you run, the newest one, and the upstream commits each contains.

Choose under Settings, Odoo image updates, how production follows: Automatic moves it to the newest build every week in your region's maintenance window, Manual keeps it on its build until you click Update image, where you can also pick an earlier build. Staging always runs the newest build, so you see what production will get. Production never stays on the same build for more than 30 days, and admins are reminded a week before.

An image update recreates the container on the new image, checks that Odoo answers before switching traffic, and rolls back on its own if it does not. Your database, files and modules are not touched.

See Odoo Image Updates.

Outbound traffic in your project settings​

A new Outbound traffic card in project Settings shows what the project sent to the internet this month: website and API, backup downloads and off-site copies, and the date the count starts again. Outbound traffic is included in every plan under fair use: nothing is billed for it, and we contact you first if a project's traffic is unusually high.

See Outbound Traffic.

GitHub connects through a GitHub App​

GitHub connections now use a GitHub App, so you choose which repositories Skysize can reach instead of granting access to all of them. Repository pickers list what the app can reach and link to its settings.

Builds and tests also report back to GitHub as Skysize / build and Skysize / tests checks on your commits, and you can turn them off per project. If GitHub stops accepting a connection's token, your Git connections page shows Reconnect needed with a Reconnect button instead of failing with a generic error.

If you connected GitHub before this change, reconnect it to limit its access. See Connect GitHub.

Backup targets on your own server​

Projects on your own server can now store backups in Azure Blob Storage, with an access key or the server's managed identity. A new S3-compatible (Wasabi, R2, MinIO...) type covers other providers.

Adding a target is now a form with one field per setting instead of a JSON box, and secrets are no longer shown back. Connection tests and downloads always run on your server.

See Backups on BYOS.

Server-wide modules per branch​

A branch can now load its own Odoo server-wide modules, so you can try one on a development branch without touching production. Set them under Server-wide modules on the branch, and set Default server-wide modules in project Settings for every new branch to start with.

Cancel a running test​

Cancel Tests now stops the test run of a development build after it has deployed, which frees the server for your next build. The deployment keeps running.

Clearer backup imports​

The dashboard now checks your file before uploading it, and refuses a zip with no dump.sql or with dump.sql inside a folder. A restore that fails now always says why. Dumps made with PostgreSQL 18 also load on servers running an older version.

See Import an Existing Odoo Backup.

Private registries and GitLab on your own server​

Custom Docker images can now come from any private registry you log in to with docker login on the server, or from private Amazon ECR using the server's AWS credentials. See Custom Docker image.

GitLab repositories on HTTPS URLs or on an SSH port other than 22 now connect and clone correctly.