Hi,

When running Odoo.sh, storage often grows much faster than the production database because every staging branch and backup multiplies the data footprint. The main driver of this growth is the way Odoo stores attachments (ir.attachment) directly inside the PostgreSQL database. To control this, many companies keep Odoo.sh for its convenient deployment and staging management but offload heavy file storage to external cloud services.

Within the Odoo ecosystem, both Google and Microsoft are well-supported. Odoo Enterprise’s Documents app integrates natively with Google Drive and OneDrive, so users can work with files directly from their cloud. For offloading binary data to reduce DB bloat, there are OCA/community modules that connect Odoo to Google Cloud Storage, Azure Blob Storage, or Amazon S3. In practice, Google integrations tend to be more commonly deployed and smoother to set up, while Microsoft is often preferred if a company is already invested in the O365/Azure stack.

In short, the best strategy is to continue using Odoo.sh for deployment but move attachments and documents to external storage. This reduces database growth significantly while letting you choose between Google or Microsoft depending on your existing IT environment.

Hope it helps

Hi Carlos,

When deleting the attachment record, are you automatically deleting the actual files?

Hey Friendrich! 👋

I noticed your staging environment is using a surprisingly high amount of GB. A colleague solved a similar issue by:

1. Temporarily moving media files to their local hard drive
2. Reuploading them to de data base only when pushing to production

Also, you might delete some files:

🔹 Enable developer mode
🔹 On the main dashboard, use the spacebar to open the search bar
🔹 Type "attachments" and select the first option
🔹 Sort files by size and remove unnecessary ones

Hope this helps!