PL EN

Package P3 · from €600

Deploying your application on Google Cloud

I launch or move your application to Google Cloud so the whole environment is described in code (Terraform), secure from day one and reproducible in minutes — instead of manual clicking in the console that nobody remembers later.

Ask about this package Proof in code

When it makes sense

  • Your app runs on a single server and the risk of it going down keeps growing.
  • You want to move to the cloud but aren’t sure whether to pick Cloud Run, GKE or a plain VM.
  • Your GCP environment was built by hand and nobody knows exactly what’s configured.
  • Passwords and keys live in code or in server environment variables.

What you get

  • containerised application (lean image, no root privileges)
  • infrastructure in Terraform: Cloud Run or GKE, database, network, permissions
  • secrets in Secret Manager, a separate account for each service
  • documentation: how to rebuild and extend the environment
Delivery time
7–15 business days
Price
from €600
Ask about this package

How it works

  1. 01

    Choosing the architecture

    I pick the simplest setup that meets the requirements — often Cloud Run instead of full Kubernetes.

  2. 02

    Container

    I package the app in a lean image without root privileges, ready to run in the cloud.

  3. 03

    Infrastructure in Terraform

    Network, the service (Cloud Run or GKE), Cloud SQL, Secret Manager and IAM — all in the repository.

  4. 04

    Launch and documentation

    Deployment, verification and a guide on how to rebuild and extend the environment.

Proof in code

The entire infrastructure of GCP-Image-Processing-Pub-Sub — a private GKE cluster, Cloud SQL, Pub/Sub, Cloud Storage, Artifact Registry and permissions — is built with Terraform (9 modules, dev and prod), without a single static key thanks to Workload Identity.

Technologies

  • Google Cloud
  • Cloud Run
  • GKE
  • Cloud SQL
  • Terraform
  • Secret Manager
  • IAM
  • Docker

Questions about this package

Q1

Cloud Run or Kubernetes (GKE)?

For one or a few HTTP services, usually Cloud Run: you pay for usage and don’t maintain a cluster. I choose GKE when there are many services, background processing, custom network policies or several environments on one cluster.

Q2

How much will the cloud itself cost?

It depends on traffic and services. Small apps on Cloud Run often cost little, but e.g. a Cloud SQL database has a fixed monthly cost. Before we start I’ll prepare a cost estimate and set up budget alerts so the bill doesn’t surprise you.

Q3

Will I depend on you?

No. The infrastructure lives in your repository and your Google Cloud account, with documentation. Any engineer who knows Terraform can take it over.

Let’s talk about your project

Briefly describe what you have today and what you want to achieve. I reply within 1 business day and send a quote within 48 hours.

Ask about this package

Other packages