Skip to main content

August 2026

Direct read-only database access (BYOS)​

You can now connect BI tools (Metabase, Power BI, Grafana) or your own scripts straight to a deployment's PostgreSQL database on your server. Each branch gets a dedicated read-only role with a one-time password, connections require TLS verified against a CA certificate you download from the dashboard, and everything stays blocked until you add the allowed IP addresses to the branch's allowlist.

Enable it from the branch's Database access card. Every allowlist change is enforced on your server before it is saved, passwords can be rotated at any time, and the role is capped in connections and query time so reporting cannot starve your Odoo instance.

See Databases on BYOS.

Bring your own PostgreSQL (BYOS)​

Servers no longer have to run the PostgreSQL instance the installer sets up. When registering a server you now choose where the Odoo databases live: on the server itself (default, unchanged) or on an external / managed PostgreSQL such as Amazon RDS, Google Cloud SQL, Azure Database, or your own cluster.

In external mode the installer asks for the connection details directly on your server; credentials never leave it. TLS settings are passed through to every deployment, and each deployment still gets its own database and role.

See Databases on BYOS.

Projects without custom code​

Creating a project no longer requires a Git repository. The new New Project wizard starts by asking whether the project will use custom code:

  • No, standard Odoo is enough: Skysize deploys standard Odoo with no repository to connect. You install the apps you need from inside Odoo, and you can still create staging environments (copies of your production database) from the Branches tab with New staging.
  • Yes, we'll write custom code: the Git flow you already know, now with the option to have Skysize create the repository for you under one of your accounts.

Projects without a repository can be given one later: Settings > Repository > Add a repository lets you pick (or create) the repository and choose the branch that deploys to production. Your production database is kept, the repository's other branches appear on the Branches tab, and deploy-on-push works from then on.

See Projects Without Custom Code and the updated Deploy Your First Instance tutorial.

Size your own server: workers and memory​

Projects on Bring Your Own Server now choose their own sizing under Settings > Workers and memory: how many Odoo workers to run, how many cron workers handle scheduled actions, and how much memory per worker each process may use. Leave workers at 0 for a single process that serves HTTP and cron together, or set 2 or more for multiprocess mode.

Before you apply, the dashboard estimates the maximum RAM the deployment may use, every process at its ceiling plus container headroom, so you can check the server has it. Apply and restart restarts the production deployment. The sizing applies to production only; staging and development keep their fixed single-process resources.

The same section now holds the Request timeout and Cron worker timeout settings for every project, managed hosting included; Cron worker max age was renamed Cron worker timeout.

BYOS backups go to your own storage​

Backup targets for BYOS projects are now exclusively your own: Skysize's platform storage is no longer offered as a target, and any project still pointing at it has been detached. A BYOS project without a backup target makes no backups and now says so in a banner on the project page.

Create a Filesystem, AWS S3, or Google Cloud Storage target under Settings > Backup Target, use Test to verify it, then select it. The configuration field explains the keys each type expects. See Operating on BYOS.

Uptime on the Monitoring tab​

Every deployment's Monitoring tab now shows an uptime percentage next to its CPU, memory, and response time charts, over any range from the last hour to the last 30 days.

The figure comes from health checks performed every 30 seconds against your running instance, and it is fair to you: time spent in planned maintenance (a build, update, restore, or restart you triggered, plus the short moment Odoo needs to boot afterwards) is excluded from the calculation, and the card tells you how much was excluded. Uptime follows your deployment's database, so pushing updates does not reset it.

Free Sandbox instances are not monitored, since they sleep when inactive.

See Deployments for details.

Connect claude.ai with one click​

The MCP endpoint now supports OAuth, so claude.ai and the Claude desktop and mobile apps can connect as a custom connector: add https://app.skysize.io/mcp in Claude's connector settings, approve the request on the Skysize consent page, and you are done. No token to create or copy.

Connections made this way appear under Account > AI Agents, marked (OAuth), and can be revoked there at any time. Access renews by itself while the connector is in use; a connector unused for 30 days simply asks you to approve again.

Header-based clients such as Claude Code, Cursor, and Windsurf keep working with access tokens as before.

See Connect an AI Agent (MCP).

Longer time limits for heavy operations​

Installing a large app such as Inventory or Accounting, or running a big import, used to hit Odoo's default request limits (2 minutes wall-clock, 1 minute CPU) and fail halfway, especially on the Free Sandbox. Every deployment now runs with a 15-minute limit for both, so those operations complete.

Two related settings live under Settings > Workers and memory, and both are expressed in minutes:

  • Request timeout caps how long a single request may run before Odoo aborts it. It now sets both Odoo's real-time and CPU-time limits at once. Leave it at 0 for the platform default (15 minutes).
  • Cron worker timeout (new) caps how long a scheduled-action worker stays alive before Odoo restarts it, so a stuck scheduled action can no longer block cron indefinitely. Odoo's default is no limit; Skysize now applies 15 minutes. Leave it at 0 for that default.

Changes apply on the next deployment. Free Sandbox projects run on the platform defaults; changing these limits requires a paid plan.

See Time Limits.