Run Google Cloud next to everything else you operate
Sencai adds one control plane on top of Google Cloud and whatever else your team runs — Compute Engine and GKE next to Hetzner instances, AWS accounts, or bare-metal servers in your own rack. Connect a project in minutes, keep the account and the bill exactly where they are today, and see everything from one place.
Bring your existing Google Cloud project — nothing migrates
Connecting Google Cloud to Sencai is BYOC by default: bring your own cloud. You link an existing Google Cloud project, Sencai encrypts the credentials at rest, and you can revoke access from the Google Cloud console at any moment — nothing about the account, the contract, or the billing relationship with Google changes. The project stays yours. If you'd rather not hold a direct Google Cloud billing relationship at all, Sencai can provision and bill that capacity under its own account instead: one contract, one invoice. Both models work inside the same organisation — start BYOC on your existing project and add Sencai-billed capacity later, or the other way round, without moving anything.
What Sencai finds the moment you connect
The moment a Google Cloud project is connected, Sencai inventories what's already running in it — Compute Engine instances, VPC networks, storage, Cloud DNS zones — next to whatever you've connected from other providers. There's no migration step and no waiting for a sync job: discovery happens on connection. None of it is placed under active management automatically. Each resource is opt-in, one at a time, so a project full of infrastructure you've never touched in Sencai doesn't suddenly start being provisioned, resized, or torn down by mistake. You choose what Sencai manages and what it simply shows you.
Provision like every other provider, manage DNS live, run GKE from one agent
Start, stop, resize, and destroy Compute Engine instances from the same workflow you use for every other connected provider — no separate console, no provider-specific runbook to remember. DNS records are managed live, directly against Google Cloud: changes you make in Sencai apply straight to your Cloud DNS zones, not to a cached copy in Sencai's own database. If your Google Cloud footprint is GKE-heavy, a separate Kubernetes fleet agent runs inside the cluster for in-cluster inventory and management, alongside the general-purpose fleet agent that handles monitoring, patching, software inventory, and approval-gated runbooks on any Linux server — Compute Engine VM or otherwise. One incident-response runbook, written once, runs the same way on a GKE node as it does on a bare-metal box in your own datacenter.
Frequently asked
Do I need to migrate anything to Google Cloud to start using Sencai?
No. Connecting a Google Cloud project is BYOC — you link the existing project, Sencai encrypts the credentials at rest, and you can revoke access from Google Cloud's own console at any time. The account, contract, and billing relationship stay exactly where they are; nothing moves.
Can I manage Google Cloud and other providers, like AWS or Hetzner, in the same organisation?
Yes. Sencai's inventory, provisioning workflow, audit log, and cost view all work across every connected provider at once, Google Cloud included. You add accounts from as many of the 11 supported providers as you use, and they all show up in the same place.
Who actually holds the Google Cloud billing relationship?
Either you or Sencai, your choice. BYOC keeps your existing Google Cloud project and billing exactly as they are today. If you'd rather not hold that relationship directly, Sencai can provision and bill the capacity under its own account: one invoice. Both can coexist in one organisation.
Does Sencai work with GKE, or just Compute Engine?
Both. Compute Engine instances go through the same provisioning workflow as any other provider. For GKE, a separate Kubernetes fleet agent runs inside the cluster and handles in-cluster inventory and management, so clusters don't disappear into a black box next to your VM-based infrastructure.
How long does it take to go from connecting a project to seeing our infrastructure?
Discovery starts as soon as the project is connected — you can see the inventory within minutes. There's a free plan (1 user, 1 organisation, 5 managed resources, no card required, no time limit) if you want to test further before committing.
Connect your Google Cloud project
Start free: one user and five managed resources, no card and no time limit. Connect your Google Cloud account and see its inventory next to every other cloud you run. See [pricing](/pricing/) for what comes after.