EVE’s primary production home is AWS (ECS/Fargate, RDS, KMS). Because the application is containerized and cloud-abstracted, the same image deploys onto managed Google Cloud equivalents — a managed-services deployment, not a rewrite. Nothing is stood up (and nothing accrues cost) until a customer contract requires it; the deployment is authored, reviewed, and version-controlled so it can be applied on demand.
What gets deployed
A minimal, production-shaped footprint in a dedicated Google Cloud project. The control plane and durable decision store run on Google Cloud infrastructure — the same governance behavior as the AWS deployment.
| Concern | Google Cloud service | Purpose |
|---|---|---|
| Control plane | Cloud Run | The EVE CoreGuard decision + evidence services (same container image as AWS). |
| Durable store | Cloud SQL for PostgreSQL | Durable, tenant-isolated decision and audit store. |
| Evidence signing | Cloud KMS (ECDSA P-384) | EVE Proof signatures — audit evidence stays offline-verifiable with the public key. |
| Working memory | Memorystore (Redis) | Optional low-latency working set. |
| Secrets | Secret Manager | JWT signing key and database credentials, never in state. |
| Entitlements | Pub/Sub | Marketplace / procurement entitlement events (enabled when applicable). |
| Registry | Artifact Registry | Holds the EVE CoreGuard image. |
| Networking | VPC + Serverless VPC Access | Private connectivity between Cloud Run and the data plane. |
Why “on contract”
A deliberate posture — honest about what is running and what it costs.
No standing cost
The Google Cloud footprint is defined as infrastructure-as-code but not applied. There is no idle GCP project and no bill until a deployment is contracted.
$0 until provisionedDeployed for you
When a contract requires Google Cloud hosting — data residency, committed GCP spend, or internal cloud policy — we provision a dedicated project and run EVE in it.
Dedicated GCP projectSame governance, verifiable
Identical deterministic decisions and EVE Proof evidence as the AWS deployment. Signatures verify offline with the public key — no trust in the host required.
Offline-verifiable evidenceNot a migration
AWS remains EVE’s primary home. The Google Cloud option is additive — a managed-equivalents deployment of the same container image.
Portable by designHow it works
Scope the deployment
We confirm your Google Cloud requirements — region and data residency, sizing, and whether the deployment is dedicated to your organization.
Provision with Terraform
A dedicated Google Cloud project is stood up from version-controlled Terraform: Cloud Run, Cloud SQL, Cloud KMS, and private networking — reviewed before apply.
Run EVE in your Google Cloud
EVE CoreGuard evaluates decisions on Google Cloud infrastructure with the same policy packs and deterministic engine as the AWS deployment.
Verify the evidence
Every governed decision is signed with a Cloud KMS ECDSA P-384 key. Auditors verify the signed decision offline — no live connection to EVE required.
About a Google Cloud Marketplace listing
A Google Cloud Marketplace listing requires a product’s core compute and data plane to run on Google Cloud. EVE CoreGuard is AWS-native, so it is not currently listed on Google Cloud Marketplace — it is publicly listed on the AWS and Azure Marketplaces.
The contracted Google Cloud deployment described here is also the eligibility path to a future Marketplace listing, if and when it makes commercial sense. Until then, EVE deploys on Google Cloud by agreement.
Need EVE in your Google Cloud?
Tell us your requirements and we’ll scope a Google Cloud deployment.
EVE CoreGuard is not SOC 2 certified; SOC 2 Type II is in progress. Patent pending. EVE NeuroSystems LLC.