Google Cloud
Compute Engine VMs, ready for your apps
Connect a Google Cloud project with a service account key and create Compute Engine VMs, provisioned for PHP or Node.js, in one go. Each gets a static address, and the same key manages the domains in your Cloud DNS.
Connect once, create servers in one go
- 1
Enable the APIs
In the Google Cloud console, choose the project and enable the Compute Engine API and the Cloud DNS API.
- 2
Create a service account key
Give a service account the roles Compute Admin and DNS Administrator, add a JSON key and paste the file under Settings → Integrations. It is checked right away and stored encrypted.
- 3
Create a server
Choose a region and a machine type. The VM runs Ubuntu 24.04 and is provisioned for your apps.
Regions and machine types
Google Cloud runs VMs in zones, so New server lists one zone per region, such as Netherlands (europe-west4-a), European ones first. Choose from shared-core (e2-micro to e2-medium), general purpose (e2, n2), compute-optimized (c3) and memory-optimized (n2-highmem) machine types.
What one service account key covers
Compute Engine VMs
Servers for every role: app, web, worker, database, cache, Meilisearch or load balancer, each with a firewall and automatic security updates.
VPC networks
VMs join the project's default network or one you choose. Let Vimonto Deploy create a network with a subnet in every region, and your servers reach each other on private addresses.
Cloud DNS
Domains in your Cloud DNS zones get their A and
wwwrecords set for you when you add them to a site, and HTTPS is requested once they resolve.A static address
Every server gets a static external address, so it keeps it when the VM is stopped. Deleting the server deletes the VM and then the address.
One firewall, on the server
One firewall rule per network lets traffic in to VMs tagged
vimonto, and the firewall on the server (ufw), which you manage in Vimonto Deploy, decides what gets through.
Backups and billing
Database backups go to an S3-compatible bucket you own: Amazon S3, Hetzner Object Storage, DigitalOcean Spaces, Cloudflare R2, or any other S3-compatible storage where you enter the endpoint yourself.
Servers are created in your own Google Cloud project and billed by Google. Google's API has no price per machine type, so check them in Google's pricing calculator. Vimonto Deploy charges nothing per server.
Google Cloud questions
Which roles does the service account need?
Compute Admin for servers, networks, firewall rules and addresses, and DNS Administrator for Cloud DNS. When an API is not enabled or a role is missing, Vimonto Deploy shows Google's own message, which says what to turn on.
Why does the wizard show no prices for Google Cloud?
Google's API does not publish a price per machine type, so Vimonto Deploy shows the sizes without one rather than guess. Google bills the VM, its disk and its address to your project.
Can I use a VM I already run on Google Cloud?
Yes, as a custom VPS: on a clean Ubuntu 24.04 VM, run the connect command and it is provisioned like any other server. Allow ports 22, 80 and 443 in its network's firewall first.
What does it cost?
The free plan covers 1 server and 3 sites with every feature. Premium is €15 per month per organization, without limits. Vimonto Deploy charges nothing per server: Google bills the server directly.
Related pages
- ServersProvisioning for every role: app, web, worker, database, cache, search and load balancer servers.
- LaravelZero-downtime Laravel deploys, with Horizon, Reverb, Pulse, queues and the scheduler a switch away.
- Sites and domainsSites from framework presets, automatic DNS, free SSL, site features and Nginx you can edit.
- Amazon Web ServicesEC2 instances in every AWS region, with fixed Elastic IPs, VPC networks and Route 53 DNS.
Your next deploy could be live before your coffee is.
Create an organization, connect a server and push. That is all.