How to leverage Google Cloud Platform (GCP) credits with info@deliverypilot.net
to power 200 autonomous bots with maximum cost efficiency, zero downtime, and serverless scalability.
Running 200 bots on traditional always-on VMs will burn credits rapidly ($200โ$500/month).
By decomposing the 179+ bot manifests from bots/4_Formula/manifest.json into three tiers,
we make your GCP credits last 5x to 10x longer:
| Bot Workload Type | Bot Count (% of Fleet) | GCP Architecture | Credit Impact |
|---|---|---|---|
| Tier 1: Scheduled / Cron News scrapers, daily mail digest, financial checks, sync jobs |
~120 bots (60%) | Cloud Run Jobs + Cloud Scheduler Containers spin up, execute task, shut down. |
Free Tier / Micro-cents Scales to 0. Billed only per millisecond of compute. |
| Tier 2: Webhook / Event-Driven Google Chat responders, Zulip stream relays, API webhooks |
~50 bots (25%) | Cloud Run Services (Scale-to-Zero) Receives HTTP POST, processes in memory, idles. |
Negligible 2 million free invocations/month. |
| Tier 3: Stateful / Persistent Browser & Grok Agents GrokBot computer use, desktop workers, long browser sessions |
~30 bots (15%) | GCE Spot VM (e2-standard-4) Persistent worker host running headless Chromium & Hermes. |
60โ91% Discount ~$15โ$25/mo on Spot VMs instead of $120/mo standard. |
| AI Inference (LLM Calls) Thinking log, bot summarization, decision loops |
All 200 bots | Vertex AI (Gemini 1.5 Flash / Pro) Use native GCP Vertex AI endpoints. |
Billed to GCP Credits Cuts out third-party credit card token bills. |
Switch CLI account to info@deliverypilot.net and configure the dedicated project:
# Login with deliverypilot account
gcloud auth login info@deliverypilot.net
# Select active Rakazo project
gcloud config set project rakazo-fleet
# Link billing account to apply your credits
gcloud billing accounts list
gcloud billing projects link rakazo-fleet \
--billing-account=<YOUR_BILLING_ACCOUNT_ID>
# Enable required GCP APIs
gcloud services enable \
run.googleapis.com \
cloudscheduler.googleapis.com \
secretmanager.googleapis.com \
artifactregistry.googleapis.com \
aiplatform.googleapis.com \
compute.googleapis.com
Centralize all bot tokens, Zulip keys, and webhook targets in Google Secret Manager:
# Create secret vault in GCP
gcloud secrets create RAKAZO_ENV_SECRETS --replication-policy="automatic"
# Load environment configuration
gcloud secrets versions add RAKAZO_ENV_SECRETS \
--data-file=".env.production"
# Grant Cloud Run runner access
gcloud secrets add-iam-policy-binding RAKAZO_ENV_SECRETS \
--member="serviceAccount:rakazo-runner@rakazo-fleet.iam.gserviceaccount.com" \
--role="roles/secretmanager.secretAccessor"
Package the web runner that coordinates GrokBot and Hermes executions:
# Create Google Artifact Registry repository
gcloud artifacts repositories create rakazo-repo \
--repository-format=docker \
--location=europe-west2 \
--description="Rakazo Docker Repository"
# Build and push runner image
gcloud builds submit --tag \
europe-west2-docker.pkg.dev/rakazo-fleet/rakazo-repo/runner:latest .
Use manifest.json to register and trigger bots seamlessly via Cloud Scheduler:
# Deploy the central web gateway on Cloud Run
gcloud run deploy rakazo-web \
--image=europe-west2-docker.pkg.dev/rakazo-fleet/rakazo-repo/runner:latest \
--platform=managed \
--region=europe-west2 \
--allow-unauthenticated \
--min-instances=0 \
--max-instances=10 \
--port=30150
# Example: Schedule a daily bot run (Cron)
gcloud scheduler jobs create http bot-daily-mail \
--schedule="0 8 * * *" \
--time-zone="Europe/London" \
--uri="https://rakazo-web-<hash>.a.run.app/api/run/daily-mail-analysis" \
--http-method=POST
--min-instances=0 so you pay $0 when no requests are being processed.