Skip to main content
Google Cloud Platform Guide

Deploy Odoo on Google Cloud Platform

Step-by-step guide to deploy Odoo on Google Cloud Platform using Compute Engine. Learn how to create instances, configure firewall rules, and connect OEC.sh for easy management.

10-15 min read
Updated January 2026
Beginner Friendly

1Prerequisites

Before deploying Odoo on Google Cloud Platform, ensure you have the following ready:

GCP Account

  • Active Google Cloud account
  • Billing enabled on your project
  • Access to Compute Engine API
  • GCP free tier eligible (optional)

OEC.sh Account

  • Free or paid OEC.sh account
  • SSH key pair generated
  • Basic understanding of Odoo
  • Domain name (optional)

GCP Free Tier

Google Cloud offers $300 in free credits for new accounts, plus always-free tier resources including 1 e2-micro instance. Perfect for testing Odoo deployments.

2Create GCP Compute Engine Instance

Create a new Compute Engine VM instance that will host your Odoo installation. Follow these steps in the GCP Console.

Step 1: Open Compute Engine

  1. Go to the GCP Console
  2. Navigate to Compute Engine > VM instances
  3. Click "Create Instance"

Step 2: Configure Instance Settings

Nameodoo-production
Regionus-central1 (Iowa)
Zoneus-central1-a
Machine typee2-medium (2 vCPU, 4 GB)
Boot disk OSUbuntu 22.04 LTS
Boot disk size50 GB SSD

Step 3: Configure Boot Disk

  1. Click "Change" under Boot disk
  2. Select "Ubuntu" as the Operating System
  3. Choose "Ubuntu 22.04 LTS" version
  4. Select "SSD persistent disk" for Boot disk type
  5. Set size to 50 GB (or more for larger deployments)
  6. Click "Select"

Step 4: Configure Networking

  1. Expand "Advanced options" > "Networking"
  2. Under "Network tags", add: http-server and https-server
  3. Under External IPv4 address, select "Reserve static external IP address"
  4. Name it odoo-ip and reserve

Important: Reserve Static IP

Always reserve a static IP for production Odoo instances. Without it, your IP may change when the VM restarts, breaking your domain configuration.

Alternative: Using gcloud CLI

Create instance with gcloud CLIbash
# Create the VM instance using gcloud CLI
gcloud compute instances create odoo-production \
--zone=us-central1-a \
--machine-type=e2-medium \
--image-family=ubuntu-2204-lts \
--image-project=ubuntu-os-cloud \
--boot-disk-size=50GB \
--boot-disk-type=pd-ssd \
--tags=http-server,https-server
# Reserve a static IP
gcloud compute addresses create odoo-ip \
--region=us-central1
# Assign static IP to instance
gcloud compute instances delete-access-config odoo-production \
--zone=us-central1-a \
--access-config-name="External NAT"
gcloud compute instances add-access-config odoo-production \
--zone=us-central1-a \
--address=$(gcloud compute addresses describe odoo-ip --region=us-central1 --format='value(address)')

3Configure Firewall Rules

GCP uses VPC firewall rules to control traffic to your instances. We need to allow HTTP, HTTPS, and SSH access.

Default Firewall Rules

If you added the http-server and https-server tags, GCP automatically applies these rules:

Rule NamePortProtocolSource
default-allow-http80TCP0.0.0.0/0
default-allow-https443TCP0.0.0.0/0
default-allow-ssh22TCP0.0.0.0/0

Create Custom Firewall Rules (if needed)

Create firewall rules via gcloudbash
# Allow HTTP traffic
gcloud compute firewall-rules create allow-http \
--allow tcp:80 \
--target-tags http-server \
--description "Allow HTTP traffic"
# Allow HTTPS traffic
gcloud compute firewall-rules create allow-https \
--allow tcp:443 \
--target-tags https-server \
--description "Allow HTTPS traffic"
# Allow Odoo direct access (optional, for testing)
gcloud compute firewall-rules create allow-odoo \
--allow tcp:8069 \
--target-tags odoo-server \
--description "Allow Odoo direct access"

Security Best Practice

In production, do not expose port 8069 directly. Use Nginx as a reverse proxy (handled automatically by OEC.sh) and only allow ports 80 and 443.

4Connect OEC.sh to Your Server

Now that your GCP instance is running, connect it to OEC.sh for easy Odoo deployment and management.

Step 1: Get Your Server IP

Get instance IPbash
# Get the external IP of your instance
gcloud compute instances describe odoo-production \
--zone=us-central1-a \
--format='get(networkInterfaces[0].accessConfigs[0].natIP)'

Or find the IP in the GCP Console under Compute Engine > VM instances.

Step 2: Add Server to OEC.sh

  1. Log in to your OEC.sh dashboard
  2. Click "Add Server" or "Connect Server"
  3. Select "Bring Your Own Server" option
  4. Enter your GCP instance's external IP address
  5. Copy the OEC.sh SSH public key provided

Step 3: Add OEC.sh SSH Key to GCP Instance

SSH into your GCP instance and add the OEC.sh public key:

Add SSH keybash
# SSH into your GCP instance
gcloud compute ssh odoo-production --zone=us-central1-a
# Add the OEC.sh public key to authorized_keys
echo "ssh-rsa AAAA...your-oecsh-key-here..." >> ~/.ssh/authorized_keys
# Set correct permissions
chmod 600 ~/.ssh/authorized_keys

Alternatively, add the key via GCP Console:

  1. Go to Compute Engine > Metadata
  2. Click "SSH Keys" tab
  3. Click "Add Item"
  4. Paste the OEC.sh public key
  5. Click "Save"

Step 4: Verify Connection

Return to the OEC.sh dashboard and click "Verify Connection". OEC.sh will test SSH access to your server.

Connection Successful

Once verified, your GCP server is ready for Odoo deployment. OEC.sh will handle all the infrastructure setup automatically.

5Deploy Odoo

With your GCP server connected to OEC.sh, deploying Odoo is just a few clicks away.

Step 1: Create New Project

  1. In OEC.sh dashboard, click "New Project"
  2. Select your connected GCP server
  3. Choose Odoo version (17 or 18 recommended)
  4. Select Community or Enterprise edition

Step 2: Configure Deployment

Odoo Version17.0 or 18.0
EditionCommunity / Enterprise
PostgreSQLAuto-configured
NginxAuto-configured
BackupsDaily (configurable)

Step 3: Deploy

  1. Review your configuration
  2. Click "Deploy"
  3. Wait 3-5 minutes for deployment to complete
  4. Access Odoo at your server's IP address

What OEC.sh Configures

OEC.sh automatically installs and configures: Odoo, PostgreSQL, Nginx reverse proxy, SSL certificates, automated backups, log rotation, and monitoring.

6Configure Domain & SSL

Set up your custom domain and enable HTTPS for secure access to your Odoo instance.

Step 1: Configure DNS

Add a DNS A record pointing your domain to your GCP instance's static IP:

TypeNameValueTTL
A@YOUR_GCP_IP3600
AwwwYOUR_GCP_IP3600

Step 2: Add Domain in OEC.sh

  1. Go to your project in OEC.sh dashboard
  2. Navigate to "Domains" section
  3. Click "Add Domain"
  4. Enter your domain name (e.g., odoo.yourdomain.com)
  5. Click "Add"

Step 3: Enable SSL

OEC.sh automatically provisions and renews SSL certificates via Let's Encrypt:

  1. Click "Enable SSL" next to your domain
  2. Wait for DNS propagation (up to 15 minutes)
  3. SSL certificate is automatically issued and installed
  4. Your Odoo is now accessible via HTTPS

Deployment Complete

Your Odoo instance is now running on Google Cloud Platform with automatic SSL, backups, and monitoring powered by OEC.sh.

7GCP Instance Recommendations

Choose the right GCP instance type based on your Odoo workload and user count:

Instance TypevCPUsMemoryUse CaseUsers
e2-small2 vCPUs (shared)2 GBDevelopment / Testing1-5 users
e2-medium2 vCPUs (shared)4 GBSmall Production5-15 users
e2-standard-22 vCPUs (dedicated)8 GBMedium Production15-50 users
e2-standard-44 vCPUs (dedicated)16 GBLarge Production50-100 users

Development

e2-small

2 shared vCPUs, 2GB RAM. For testing and development only.

Recommended

e2-standard-2

2 dedicated vCPUs, 8GB RAM. Best for most production workloads.

High Performance

e2-standard-4

4 dedicated vCPUs, 16GB RAM. For large deployments with heavy traffic.

Scaling Tip

Start with e2-medium for small production workloads. GCP allows easy scaling - you can resize your instance at any time with minimal downtime.

8Cost Comparison: GCP + OEC.sh vs Odoo.sh

Compare the total cost of running Odoo on GCP with OEC.sh versus Odoo.sh hosting:

ConfigurationGCP + OEC.shOdoo.shSavings
Development
e2-small, 2GB RAM
$21/mo$32/mo34%
Small Production
e2-medium, 4GB RAM
$53/mo$132/mo60%
Medium Production
e2-standard-2, 8GB RAM
$98/mo$264/mo63%
Large Production
e2-standard-4, 16GB RAM
$147/mo$528/mo72%

Save Up to 72% vs Odoo.sh

By using GCP with OEC.sh, you get full control over your infrastructure while saving significantly compared to Odoo.sh. Plus, you keep your data on your own servers.

What You Get with GCP + OEC.sh

Full root access to your server
No vendor lock-in
Automated backups to 7+ destinations
One-click Odoo updates
Custom domain & SSL included
Git integration & CI/CD
24/7 monitoring & alerts
SSH access for customization

9Frequently Asked Questions

Ready to Deploy Odoo on GCP?

Get started with OEC.sh and deploy Odoo on Google Cloud Platform in minutes. Enjoy automated backups, one-click updates, and 24/7 monitoring.

Related Guides

Deploy Odoo on Google Cloud Today

Skip the manual setup. Deploy Odoo on GCP in minutes with OEC.sh. Start free, scale as you grow.

5 min
Deployment Time
72%
Cost Savings
$0
Free Plan