Skip to main content

Google Cloud Platform

Run the workload on Google Cloud

We design how an application runs on Google Cloud Platform: the project and IAM layout, the runtime that fits the process, and the data services it is allowed to use. OLIANT is a registered partner in the Google Cloud Partner Network. This page is that platform work.

Illustration for Google Cloud Platform services

What we build on Google Cloud Platform

The platform choice follows the process. A request-sized container, a Kubernetes cluster, and a virtual machine are different operating models, and we pick one.

  • Projects, folders, and IAM

    Each environment gets a project. Folders group those projects when the organization needs it. Service accounts own deploy and runtime access. Human users do not share a key.

    IAM bindings are written down: who can deploy, who can read production data, and which APIs are enabled. A new service starts from that list.

  • Cloud Run, GKE, and Compute Engine

    Cloud Run is the default for a stateless container with HTTP or a job. GKE is for a workload that already needs Kubernetes: several services, a mesh, or a platform team that will run the cluster. Compute Engine is for the process that has to be a VM.

    We do not put a single container on GKE to make the diagram look complete. The runtime matches who will operate it.

  • Data services the application is allowed to touch

    Cloud SQL for relational data the application queries. Cloud Storage for objects and uploads. BigQuery when the work is analysis over large tables, not a row the user is editing. Memorystore when a cache is actually required.

    Pub/Sub carries events between services. A service publishes a message it can name. Consumers are separate deploys with their own service accounts.

  • Build and release

    Cloud Build, or the pipeline you already run, builds the artifact and deploys it into the right project. Environments are not two folders in the same project with a comment that says prod.

    Logs and error reporting are on from the first deploy. A service without a way to tell a failed revision from a healthy one is not ready for traffic.

Typical use cases

These are the platform shapes we set up. They are not a claim about a particular customer's bill or traffic.

  • A container service on Cloud Run

    An API or a worker with a container, a concurrency setting, and a service account that can reach Cloud SQL or Cloud Storage. Revisions are the rollback.

  • A cluster that already has a reason

    GKE when several services share a cluster and someone will own node pools, upgrades, and namespaces. We set the namespace, the workload identity, and the deploy. We do not treat the cluster as a substitute for IAM.

  • Analysis that should not hit the application database

    Events or exports land in BigQuery. The application database stays for transactions. Queries for reporting run against BigQuery, with a dataset and a group that is allowed to read it.

  • An existing application moving onto GCP

    We start with what the process needs: a VM, a container, or a managed SQL instance. The move is a runtime and a data store, plus the IAM that replaces the old shared login.

How we work

Google Cloud work starts with identity and projects. Product selection comes after we know who deploys and where data lives.

  • Draw the projects and the accounts

    Development, staging, and production are separate projects unless there is a written reason not to. Service accounts are created for deploy and for runtime. Keys are a last resort.

  • Match the runtime to the process

    HTTP container, Kubernetes workload, scheduled job, or VM. We name the Google Cloud product and the operational task it creates, including who upgrades it.

  • Put data in the service that fits the question

    Transactions in Cloud SQL. Objects in Cloud Storage. Analytical queries in BigQuery. The application gets credentials for the one it needs, not for the whole project.

  • Deploy from a pipeline into that project

    The pipeline identity can deploy to the target project and cannot rummage through another environment. A rollback is a previous revision or a previous image, tried before the production project depends on it.

Our Google Cloud work

  • Client project, live in production

    Gmail-native outreach and thread tracking for a client platform

    Our client's users needed to email their contacts without leaving the platform, and then copy replies back into it by hand, which was slow and error-prone. We built a Gmail integration that lets them start conversations from the app's own interface, using their own Google Workspace accounts. Every reply, forward and new participant on those threads is then captured, analyzed and saved automatically, with no extra work.

    Privacy by design. Users connect their Gmail account once, through Google-verified OAuth with sensitive-scope permissions. The app never reads the inbox: it only follows threads the user started through the app, and ignores everything else.

    • Gmail API. Sending as the user and receiving change notifications
    • Cloud Pub/Sub. Streams inbox events to the backend for asynchronous processing
    • Google Cloud IAM. Service-account credentials securing every Google-side call
    • OpenTofu. Infrastructure-as-code templates for the Google Cloud environment, reproducible and version-controlled
    • AWS Lambda + API Gateway. The client's serverless backend, receiving Google Cloud events and processing them
    • PostgreSQL. A complete record of every tracked thread and its activity

Start with the project layout

Tell us what runs today and who is allowed to deploy. We will place it on Cloud Run, GKE, or Compute Engine with IAM to match.

Schedule a call

Why OLIANT

Google Cloud Platform at OLIANT is the project, the identity, and the runtime. OLIANT is a registered partner in the Google Cloud Partner Network.

  • IAM before the product icon

    Projects and service accounts are the first deliverable. A runtime is added only after we know who can deploy it.

  • One runtime, with an operator

    Cloud Run, GKE, or Compute Engine is chosen with the person who will upgrade it. The diagram and the on-call task match.

  • Data access is specific

    Cloud SQL, Cloud Storage, and BigQuery are granted per service account. Reporting does not log into the transaction database.

Frequently asked questions

Questions about how we use Google Cloud Platform.

OLIANT is a registered partner in the Google Cloud Partner Network. On this page that means we design and run workloads on Google Cloud Platform: projects, IAM, and the managed services the application uses.

A Google Cloud layout you can explain

Bring the current hosting and the people who deploy. We will propose the projects, the runtime, and the data services.

Illustration for the Google Cloud Platform closing invitation