Hasura on Google Cloud Run

Hasura is an open-source, Apache 2.0-licensed engine that gives you an instant, realtime GraphQL (and REST) API over a PostgreSQL database, with fine-grained role-based authorization, event triggers, and a built-in admin console. This module deploys the Hasura GraphQL Engine (hasura/graphql-engine) on Cloud Run v2 on top of the App_CloudRun foundation, which provisions and manages the shared Google Cloud infrastructure.

This guide focuses on the cloud services Hasura uses and how to explore and operate them from the Google Cloud Console and the command line. For the mechanics common to every Cloud Run application — service identity, ingress and load balancing, scaling and concurrency, CI/CD, Cloud Armor, IAP, Binary Authorization, VPC Service Controls, backups, and the deployment lifecycle — refer to the App_CloudRun foundation guide rather than repeating them here.

---

What Hasura costs on RAD, and how that compares

Running Hasura on Cloud Run in your own Google Cloud project costs about $67.80/month in Google Cloud charges, on top of a one-off 75-credit RAD module fee charged once at deploy time. Hasura's own commercial cloud product has pivoted away from hosting the classic open-source GraphQL Engine this module deploys — its current pricing page (checked 8 October 2026) only lists the newer "DDN" supergraph product, with no separate plan for the Community Edition engine, so that isn't a fair comparison to quote here. In a RAD-managed project the module fee drops to 67.5 credits (10% lower) and the running cost is metered hourly in credits instead of billed directly by Google — see Pause it for free below for the one RAD-managed advantage a self-hosted VPS cannot match — or see the GKE guide if you'd rather run it on Kubernetes.

What you pay on RAD

	Own project	RAD-managed project
Module fee (one-off)	75 credits	67.5 credits (10% lower)
Build time	~3-6 credits per build, either way	~3-6 credits per build, either way
Google Cloud running cost	$67.80/month, billed by Google at list price	~26 credits/day, metered at list price plus RAD's margin

Default running cost in your own project

Resource	US$/month (Google list price, us-central1)
Cloud Run, 1x vCPU / 0.5 GiB (scaleToZero)	$10.78
Cloud SQL for PostgreSQL, 1 vCPU / 3.75 GB, zonal, 10 GB SSD	$51.02
Cloud NAT and networking	$5.00
Cloud Storage (add-ons, backups)	$1.00
Total	$67.80

How it compares

• A self-managed comparison instead: Hetzner CPX22 (2 vCPU/4GB) runs about $24/mo, a DigitalOcean 2 vCPU/4GB Droplet is the same $24/mo, and a GCP Compute Engine e2-standard-2 (2 vCPU/8GB) is about $49/mo — enough to run Hasura's engine and its Postgres database together on one box.
• The 1 vCPU/0.5 GiB engine itself is light; most of the running cost above is the dedicated Postgres instance GraphQL introspection needs to stay fast, which a self-managed box would need too.
• As elsewhere, the VPS figures above are cheaper in cash terms but carry no managed backups, patching, or secret rotation — RAD's Cloud SQL, Secret Manager and monitoring cover that for you.

Pause it for free: delete a RAD-managed project, restore it when you need it

This is the headline advantage of a RAD-managed project, and it costs nothing while paused. Deleting a RAD-managed project unlinks its billing first, then asks Google to delete the project outright — Google's own 30-day recoverable soft delete. Unlike deleting one module, this does not tear down Cloud SQL, any VM, or the compute resource one by one: the whole project simply stops, and nothing is charged while it waits, because billing is already unlinked.

Restoring, within 30 days and only by the project's owner, asks Google to undelete the project and reattaches its billing account, then asks you to run Update on each deployment to confirm everything came back. Because nothing was individually destroyed, that Update finds the same resources already there — it is a check, not a rebuild, and an Update never charges the module fee again. This costs only a handful of credits (under US$1) in total for a typical 2-3-deployment chain.

What this needs: you must own the project (not one RAD only manages billing for), you must restore it yourself within 30 days — after that Google deletes it for good — and restoring is admitted like creating a new project, so your purchased credit balance must still clear the tier's floor (100 credits for the sandbox tier most study/demo use fits). Google says most services are fully working again within 36 hours of a restore.

One real gap: nightly backups are written to a bucket inside the project, and that bucket has Cloud Storage's soft-delete explicitly turned off, so it is very likely gone as soon as you delete the project — even though the project itself is recoverable for 30 days. If you've customised Hasura and want to keep that work, copy a backup out (to Google Drive, or a bucket outside the project) before deleting. For a default install with nothing irreplaceable in it, this does not matter.

Pay only while you use it, the other way: delete and redeploy

In your own project, or once 30 days have passed on a RAD-managed one, there is no free pause — deleting removes the resources for good, and bringing Hasura back means redeploying from scratch. That costs about 78-81 credits (the 75-credit module fee plus a build).

Deleting only saves money once Hasura would otherwise sit unused long enough to clear that redeploy cost against its own running cost — for Hasura, that's about 4 days or more. Most of that running cost is usually the database (and, where this module uses one, the shared file-server VM or GKE cluster) — those stop only once nothing else in the project uses them, so deleting this app while something else shares the project saves only its own compute share.

Keep data first: nightly backups go to a bucket inside the deployment and are deleted with it, so copy the latest backup out before deleting if you want to keep it.

Lab sessions and Managed Environments

Lab sessions, for training: a trainer runs a session for a class. Each participant gets the app in their own Google Cloud project for 15 minutes to 24 hours, within an allowance the trainer sets. Either the trainer funds every place, or each participant pays for their own. Everything is deleted when the session ends and unused credits go back to the trainer.

Managed Environments, for consultancies: a partner runs the app for a client from a ring-fenced wallet it funds, and settles with the client directly. If the wallet runs low, billing pauses and the data is kept, so nobody receives an unexpected charge. At the end the partner hands the project over and the deployments become the client's own.

Credits can be bought in more than 20 currencies, including XAF, XOF, NGN, GHS, KES and ZAR, by card, bank transfer or mobile money.

Sources (8 October 2026): Google Cloud Billing Catalog API list prices; radmodules.dev/pricing for RAD's own fees and daily-credit estimates; Google's project delete/restore documentation for the pause/restore claims.

1. Overview

Hasura runs as a single Haskell container on Cloud Run v2. The deployment wires together a focused set of Google Cloud services:

Capability	Google Cloud service	Notes
Compute	Cloud Run v2	Haskell service, 1 vCPU / 512 MiB by default, serverless autoscaling; scale-to-zero supported
Database	Cloud SQL for PostgreSQL 15	Required — Hasura's metadata catalog and default data source both live in Postgres
Object storage	None	Hasura is stateless; no bucket is provisioned
Secrets	Secret Manager	Auto-generated HASURA_GRAPHQL_ADMIN_SECRET; database password
Ingress	Cloud Run URL / Cloud Load Balancing	Default run.app URL; optional external HTTPS load balancer + custom domain

Sensible defaults worth knowing up front:

• PostgreSQL 15 is mandatory. The database engine is fixed by the shared application layer; Hasura keeps its own metadata catalog in Postgres, so no other engine is supported.
• The admin secret gates everything sensitive. HASURA_GRAPHQL_ADMIN_SECRET is generated automatically and stored in Secret Manager. It protects the /console UI and the /v1/graphql and /v1/metadata APIs. /healthz stays public for health probes.
• Two connection URLs are assembled in-container. The custom image entrypoint builds HASURA_GRAPHQL_DATABASE_URL (default data source) and HASURA_GRAPHQL_METADATA_DATABASE_URL (Hasura's metadata store) from the injected DB_* variables at runtime — Cloud Run does not interpolate $(VAR) in env values, so this cannot be done at plan time.
• Scale-to-zero is enabled by default (min_instance_count = 0, cpu_always_allocated = false). Because all state is external in Postgres, a cold-started instance serves correctly; cold starts add a few seconds of latency to the first request after idle. Set min_instance_count = 1 for latency-sensitive APIs.
• Public ingress by default. ingress_settings = "all" so clients and the console can reach the service. Enabling IAP protects the whole service — including the API — behind Google identity.
• The console ships enabled. HASURA_GRAPHQL_ENABLE_CONSOLE = "true" serves the admin console at /console. Disable it in production if you manage metadata purely via CI (hasura CLI / migrations).
• No storage, no Redis, no NFS. storage_buckets = [], enable_redis = false, enable_nfs = false — everything lives in PostgreSQL.

---

2. Google Cloud Services & How to Explore Them

All commands assume PROJECT and REGION are set. Service and resource names are reported in the deployment Outputs.

A. Cloud Run — the Hasura service

Hasura runs as a Cloud Run v2 service that autoscales by request load between the minimum and maximum instance counts. Each deployment creates an immutable revision; traffic can be split across revisions for safe rollouts.

• Console: Cloud Run → select the service for revisions, traffic, logs, and metrics.
• CLI:

  gcloud run services list --project "$PROJECT" --region "$REGION"
  gcloud run services describe <service-name> --project "$PROJECT" --region "$REGION"
  gcloud run revisions list --service <service-name> --project "$PROJECT" --region "$REGION"

See App_CloudRun for scaling, concurrency, execution environment, and traffic splitting.

B. Cloud SQL for PostgreSQL 15

Hasura stores its metadata catalog (tracked tables, relationships, permissions, event triggers) and your application data in a managed Cloud SQL for PostgreSQL 15 instance. The service connects privately through the Cloud SQL Auth Proxy over a Unix socket; no public IP is exposed. On first deploy an initialization Job creates the application database and user; Hasura installs its metadata schema on first boot.

• Console: SQL → select the instance for connections, backups, flags, metrics.
• CLI:

  gcloud sql instances list --project "$PROJECT"
  gcloud sql instances describe <instance-name> --project "$PROJECT"
  gcloud sql connect <instance-name> --user=<db-user> --database=<db-name> --project "$PROJECT"

The instance name, database, user, and password secret are in the Outputs. See App_CloudRun for the connection model, backups, and password rotation.

C. Secret Manager

One cryptographic secret is generated automatically and stored in Secret Manager: HASURA_GRAPHQL_ADMIN_SECRET (grants full access to the GraphQL/metadata APIs and the console). The database password is managed separately by the foundation.

• Console: Security → Secret Manager.
• CLI:

  gcloud secrets list --project "$PROJECT"
  # The admin secret — use it as the x-hasura-admin-secret header:
  gcloud secrets versions access latest --secret=<admin-secret-name> --project "$PROJECT"

See App_CloudRun for injection and rotation details.

D. Networking & ingress

The service is reachable at its run.app URL by default. An external HTTPS load balancer with a custom domain, Cloud CDN, and Cloud Armor can be layered on; ingress settings and VPC egress control connectivity.

• Console: Cloud Run (service URL); Network services → Load balancing.
• CLI:

  gcloud run services describe <service-name> --region "$REGION" --format='value(status.url)'
  gcloud compute addresses list --project "$PROJECT"

See App_CloudRun.

E. Cloud Logging & Monitoring

Container logs flow to Cloud Logging; Cloud Run and Cloud SQL metrics flow to Cloud Monitoring, with an optional uptime check (targeting /healthz) and alert policies.

• Console: Logging → Logs Explorer; Monitoring → Dashboards / Alerting.
• CLI:

  gcloud run services logs read <service-name> --project "$PROJECT" --region "$REGION" --limit 50

---

3. Hasura Application Behaviour

• First-deploy database setup. An initialization Job runs create-db-and-user.sh using postgres:15-alpine. It connects through the Cloud SQL Auth Proxy and idempotently creates the application database and user and grants privileges. The job is safe to re-run.
• Metadata catalog on start. Hasura installs and migrates its own metadata catalog schema in Postgres on startup, so upgrading the image version applies catalog changes without a separate migration step. Your tracked-table metadata persists in the database across revisions.
• Two connection URLs, assembled in-container. The entrypoint builds both HASURA_GRAPHQL_DATABASE_URL and HASURA_GRAPHQL_METADATA_DATABASE_URL from the injected DB_* variables, URL-encoding the password and branching on DB_HOST (socket dir → libpq socket form; loopback → plain; private IP → sslmode=require).
• Admin secret is the security boundary. Send it as the x-hasura-admin-secret header. Retrieve it:

  gcloud secrets versions access latest --secret=<admin-secret-name> --project "$PROJECT"
  # Then, e.g.:
  curl -s "$SERVICE_URL/v1/graphql" \
    -H "x-hasura-admin-secret: <secret>" \
    -H 'Content-Type: application/json' \
    -d '{"query":"{ __schema { queryType { name } } }"}'

• Health path. Startup and liveness probes target /healthz — the public, unauthenticated endpoint that returns 200 once the engine is up and connected to Postgres. Do not repoint probes at /v1/graphql or /console (both 401 without the admin secret).
• Console access. Open $SERVICE_URL/console in a browser and paste the admin secret when prompted to track tables, define permissions, and run GraphQL queries.
• Inspect job execution:

  gcloud run jobs list --project "$PROJECT" --region "$REGION"
  gcloud run jobs executions list --job <job-name> --project "$PROJECT" --region "$REGION"

---

4. Configuration Variables

Variables are grouped exactly as they appear on the deployment platform. Only settings specific to or notable for Hasura are listed; every other input is inherited from App_CloudRun with its standard behaviour.

Group 1 — Project & Identity

Variable	Default	Description
project_id	(required)	Target Google Cloud project.
region	us-central1	Region for the service and regional resources.

Group 2 — Deployment Environment

Variable	Default	Description
tenant_id	demo	Short suffix that makes resource names unique per environment.
support_users	[]	Emails granted project access and monitoring alerts.
resource_labels	{}	Labels applied to all resources.

Group 3 — Application Identity

Variable	Default	Description
application_name	hasura	Base name for resources. Do not change after first deploy.
application_display_name	Hasura	Human-readable name shown in the Console.
application_description	Hasura GraphQL Engine on Cloud Run	Service description.
application_version	v2.36.0	Hasura image tag; latest is remapped to a pinned v2.x tag at build time.
application_database_name	hasura	PostgreSQL database name. Immutable after first deploy.
application_database_user	hasura	Application database user. Password auto-generated in Secret Manager.

Group 4 — Runtime & Scaling

Variable	Default	Description
deploy_application	true	Set false to provision infrastructure only.
container_image_source	custom	custom builds a wrapper image that assembles the DSNs; prebuilt requires manual URL config.
cpu_limit	1000m	CPU per instance; 1 vCPU suits most workloads.
memory_limit	512Mi	Memory per instance; raise for high query concurrency.
min_instance_count	0	0 enables scale-to-zero (safe — all state is in Postgres).
max_instance_count	3	Autoscaling upper bound; Hasura scales horizontally.
container_port	8080	Hasura binds HASURA_GRAPHQL_SERVER_PORT = 8080.
cpu_always_allocated	false	Request-based billing — Hasura does no background work between requests.
execution_environment	gen2	Gen2 recommended.
timeout_seconds	300	Maximum request duration (raise for long subscriptions/streaming).
enable_cloudsql_volume	true	Cloud SQL Auth Proxy socket for the Postgres connection.
enable_image_mirroring	true	Mirror the Hasura image into Artifact Registry.
traffic_split	[]	Split traffic across revisions for staged rollouts.
max_revisions_to_retain	7	How many old revisions to keep.

Group 5 — Access & Ingress Control

Variable	Default	Description
ingress_settings	all	all allows external clients and the console to reach the service.
vpc_egress_setting	PRIVATE_RANGES_ONLY	Route only RFC 1918 traffic via VPC.
enable_iap	false	Require Google sign-in in front of the whole service (API included).
iap_authorized_users / iap_authorized_groups	[]	Who may access through IAP.

Group 6 — Environment Variables & Secrets

Variable	Default	Description
environment_variables	{}	Extra HASURA_GRAPHQL_* settings (e.g. HASURA_GRAPHQL_DEV_MODE, HASURA_GRAPHQL_CORS_DOMAIN). Do not set the two *_DATABASE_URL values or the admin secret here — they are managed automatically.
secret_environment_variables	{}	Map of env var → Secret Manager secret name.
secret_propagation_delay	30	Seconds to wait after secret creation before proceeding.
secret_rotation_period	2592000s	Secret Manager rotation notification frequency.

Group 7 — Backup & Restore

Variable	Default	Description
backup_schedule	0 2 * * *	Automated backup cron (UTC).
backup_retention_days	7	Retention; raise for production/compliance.
enable_backup_import / backup_source / backup_file / backup_format	restore options	Restore from a backup on deploy.

Group 8 — CI/CD & Binary Authorization

Standard App_CloudRun Cloud Build / Cloud Deploy integration — see App_CloudRun. Key inputs: enable_cicd_trigger, github_repository_url, github_token, enable_cloud_deploy, enable_binary_authorization.

Group 9 — Custom SQL Scripts

enable_custom_sql_scripts, custom_sql_scripts_bucket, custom_sql_scripts_path, custom_sql_scripts_use_root — run SQL from a GCS bucket after provisioning. See App_CloudRun.

Group 10 — Load Balancer, CDN & Image Retention

Variable	Default	Description
enable_cloud_armor	false	Provision Global HTTPS LB + Cloud Armor WAF.
admin_ip_ranges	[]	CIDR ranges exempted from WAF rules.
application_domains	[]	Custom domain names for the HTTPS LB.
enable_cdn	false	Enable Cloud CDN on the HTTPS LB backend.
max_images_to_retain / delete_untagged_images / image_retention_days	(set)	Artifact Registry cleanup policy.

Group 11 — Storage & Filesystem

Variable	Default	Description
create_cloud_storage	true	Create GCS buckets defined in storage_buckets.
storage_buckets	[]	Empty — Hasura requires no file storage.
enable_nfs	false	Not required for Hasura.
gcs_volumes	[]	GCS Fuse volume mounts (requires gen2).
manage_storage_kms_iam / enable_artifact_registry_cmek	false	CMEK options.

Group 12 — Database Backend

Variable	Default	Description
database_type	POSTGRES_15	Fixed — Hasura requires PostgreSQL.
database_password_length	32	Generated password length (16–64).
enable_auto_password_rotation / rotation_propagation_delay_sec	off	DB password rotation.
enable_postgres_extensions / postgres_extensions	off / []	Optional Postgres extensions.

Group 13 — Jobs & Scheduled Tasks

Variable	Default	Description
initialization_jobs	[]	Leave empty to use the built-in db-init job.
cron_jobs	[]	Recurring Cloud Scheduler + Cloud Run Jobs.
additional_services	[]	Extra Cloud Run services deployed alongside Hasura.

Group 14 — Observability & Health

Variable	Default	Description
startup_probe	HTTP /healthz	Application-level startup probe.
liveness_probe	HTTP /healthz	Application-level liveness probe.
startup_probe_config	HTTP /healthz	Cloud Run startup probe (foundation-level).
health_check_config	HTTP /healthz	Cloud Run liveness probe (foundation-level).
uptime_check_config	{ enabled=false, path="/healthz" }	Cloud Monitoring uptime check. Disabled by default; enable for production monitoring.
alert_policies	[]	Metric alert policies.

Group 16 — Redis

Variable	Default	Description
enable_redis	false	Hasura does not require Redis.
redis_host	""	Only used when enable_redis = true.
redis_port	6379	Redis port.

Group 22 — VPC Service Controls & Audit Logging

Variable	Default	Description
enable_vpc_sc	false	Enforce a VPC-SC perimeter (requires organization_id for folder-nested projects).
vpc_cidr_ranges / vpc_sc_dry_run	(set)	Access level CIDRs / dry-run mode.
enable_audit_logging	false	Detailed Cloud Audit Logs.

---

5. Outputs

Returned on a successful deployment — the quickest way to locate and explore the running resources.

Output	Description
service_name	Cloud Run service name.
service_url	Default run.app URL of the service.
service_location	Region the service runs in.
stage_services	Stage-specific service URLs (Cloud Deploy).
load_balancer_ip / load_balancer_url	External HTTPS load balancer IP / URL (when enabled).
database_instance_name	Cloud SQL instance name.
database_name / database_user	Application database name / user.
database_password_secret	Secret Manager secret holding the DB password.
database_host / database_port	DB endpoint / port.
storage_buckets	Created Cloud Storage buckets (empty for Hasura).
network_name / network_exists / regions	VPC network, presence, regions.
container_image / container_registry	Deployed image and Artifact Registry repo.
monitoring_enabled / monitoring_notification_channels / uptime_check_names	Monitoring status, channels, uptime checks.
initialization_jobs	Names of the setup jobs.
deployment_id / tenant_id / resource_prefix	Naming identifiers.
project_id / project_number	Project identifiers.
cicd_enabled / github_repository_url / cicd_configuration	CI/CD status and details.
artifact_registry_repository / cloudbuild_trigger_name / cloudbuild_trigger_id	Registry and build trigger.
vpc_sc_enabled / vpc_sc_perimeter_name / vpc_sc_dry_run_mode	VPC-SC status.
audit_logging_enabled / artifact_registry_cmek_enabled	Audit logging and CMEK status.

---

6. Configuration Pitfalls & Sensible Defaults

Risk: Critical (data loss / outage / security) — High (service degraded) — Medium (cost or partial degradation) — Low (minor).

Inherited plan-time validation. This module passes its configuration through the App_CloudRun foundation engine, which validates values and combinations at plan time — a read replica without its primary, IAP with no authorized identities, a gen1 runtime with NFS/GCS mounts, a database_type that does not match an enabled extension, an out-of-range redis_port/backup_retention_days. Invalid configuration fails the plan with a clear, named error before any resource is created, so most mistakes below are caught up front rather than at apply or runtime.

Setting	Sensible value	Risk	Consequence if wrong
HASURA_GRAPHQL_ADMIN_SECRET (auto-generated)	Keep in Secret Manager; rotate deliberately	Critical	It is the only guard on the GraphQL/metadata APIs and console — exposing it grants full read/write to every tracked table.
application_database_name / application_database_user	Set once	Critical	Immutable after first deploy; renaming recreates the DB/user and orphans the metadata catalog and all data.
enable_backup_import	false unless restoring	Critical	Enabling without a valid backup_file fails the import job.
startup_probe / liveness_probe path	/healthz	High	Pointing a probe at /v1/graphql or /console returns 401 — the revision never becomes Ready even though the engine booted.
HASURA_GRAPHQL_ENABLE_CONSOLE	false in production	High	Leaving the console on in production widens the attack surface; manage metadata via the hasura CLI/migrations instead.
ingress_settings + enable_iap	all; IAP only if the API can be identity-gated	High	IAP blocks all unauthenticated requests including programmatic API clients that authenticate with the admin/JWT header, not Google identity.
container_image_source	custom	High	prebuilt skips the entrypoint that assembles the two *_DATABASE_URL values — the engine starts with no database and every request fails.
memory_limit	512Mi+	Medium	Very large metadata or high query concurrency can OOM below 512 MiB; the gen2 environment floors memory at 512 MiB regardless.
min_instance_count	0 (or 1 for latency)	Medium	Scale-to-zero adds a few seconds of cold-start latency to the first request after idle; set 1 for latency-sensitive APIs.
backup_retention_days	7 (raise for prod)	Medium	Too short for compliance retention.
enable_cloud_armor	enable for production	Medium	The API and console are publicly reachable without WAF protection.

---

For the foundation behaviour referenced throughout — service identity, scaling and concurrency, ingress and load balancing, CI/CD, Cloud Armor, IAP, Binary Authorization, VPC-SC, backups, and image mirroring — see App_CloudRun. Hasura-specific application configuration shared with the GKE variant is described in Hasura_Common.

Related guides

• Hands-on lab: Hasura on Cloud Run — deploy it step by step, with the console screens and commands at each stage.
• Hasura on GKE Autopilot — the same application on Kubernetes, for when you need the other deployment target.
• Hasura Common — Shared Application Configuration — the configuration shared by both deployment targets.
• Deployed alongside Supabase on GKE Autopilot, Directus on Cloud Run, Meilisearch on GKE Autopilot in the Application Backend Services solution.