Skip to content
Book a free 30-minute call with an engineer

Google Cloud development

Cloud Run, BigQuery and Firebase for products that live on data

Cloud RunGKECloud SQLFirestoreBigQueryPub/SubCloud StorageCloud BuildTerraformVertex AI

Cloud & DevOps

Building with Google Cloud

Google Cloud is a good home for products that lean on data or already use Firebase. Cloud Run is one of the easiest ways we know to run containers in production, BigQuery handles analytics at almost any size, and Firebase sits on the same platform for mobile auth and push.

We set up GCP projects with Terraform, separate staging from production properly, and keep IAM roles tight. Most of our GCP work is SaaS backends on Cloud Run with Cloud SQL, plus reporting built on BigQuery once a product has enough data to report on.

cloudbuild.yamlYAML
1steps:​
2 - name: gcr.io/cloud-builders/docker​
3 args: ["build", "-t", "$_IMAGE:$SHORT_SHA", "."]​
4 - name: gcr.io/cloud-builders/docker​
5 args: ["push", "$_IMAGE:$SHORT_SHA"]​
6 - name: gcr.io/google.com/cloudsdktool/cloud-sdk​
7 entrypoint: gcloud​
8 args:​
9 - run​
10 - deploy​
11 - api​
12 - --image=$_IMAGE:$SHORT_SHA​
13 - --region=europe-west2​

The kind of Google Cloud code our team writes every week.

What we build with Google Cloud

  1. 01

    Cloud Run services

    Containerized APIs and workers that scale on request volume and drop to zero overnight.

  2. 02

    GKE clusters

    Managed Kubernetes on GKE Autopilot or Standard when you have enough services to justify it.

  3. 03

    BigQuery analytics

    Event pipelines into BigQuery and dashboards your team and customers can actually read.

  4. 04

    Firebase backends

    Auth, Firestore, Cloud Functions and FCM for mobile apps, with security rules that are tested.

  5. 05

    Migration to GCP

    Moving workloads from other clouds or on-premise servers with planned cutovers.

  6. 06

    AI on Vertex

    Gemini models and Vertex AI for document processing, search and classification features.

Why teams pick Google Cloud

01

Simple container hosting

Cloud Run takes a container image and gives you HTTPS, autoscaling and per-request billing with very little setup.

02

Strong data tools

BigQuery, Pub/Sub and Dataflow make it straightforward to add reporting and event processing later.

03

Firebase on the same platform

Mobile features and server-side services share one project, one billing account and one set of permissions.

04

Fair pricing for small teams

Per-second billing, sustained-use discounts and generous free tiers keep early bills low.

Good fits

  • Containerized SaaS backends
  • Mobile apps on Firebase
  • Product analytics and reporting
  • Event-driven integrations
  • AI-powered features

Where we use it

Google Cloud questions

Is Google Cloud a good fit for startups?

Often, yes. Cloud Run and Firebase let a small team ship without managing servers, and the startup credits program can cover a lot of the first year. If you need a service that only AWS offers, we'll tell you before you commit.

How is GCP different from AWS or Azure for our project?

For a typical SaaS app, all three can do the job. GCP tends to be simpler for containers and analytics, AWS has the widest service catalog, and Azure fits companies already on Microsoft 365. We usually match the cloud to your team's existing experience and customer requirements.

Can you add analytics dashboards to our SaaS using BigQuery?

Yes. We stream product events into BigQuery, model them into clean tables and build dashboards in Looker Studio or inside your own app. Customer-facing reporting gets row-level security so each tenant only sees its own data.

Do you handle security and access control on GCP?

Yes. We use separate projects per environment, service accounts with minimal roles, Secret Manager for credentials and audit logging. VPC Service Controls get added when compliance needs call for them.

Pairs well with