GCP Quickstart 1-Click Cloud Shell & gcloud CLI 10,000 Evaluation Requests Included

1-Click Google Cloud Compute Engine Deployment Guide

Launch Enterprise PII Guardrails into your Google Cloud Platform project in under 3 minutes. Test real-time PII redaction, custom regex engines, and LLM integrations with zero initial setup and automatic evaluation licensing (10,000 requests included).

Automated Google Cloud Deployment

Deploy Directly via Cloud Shell or gcloud CLI

Provisions an Ubuntu 24.04 LTS e2-standard-2 instance (2 vCPU, 8GB RAM) with 30 GB balanced persistent disk, auto-managed Docker runtime, and pre-activated evaluation license (10,000 requests quota).

🚀 Launch in Cloud Shell ↗ Download Script

Lifecycle & Node-Locked Conversion Pipeline

1
Deploy & Evaluate

1-Click Cloud Shell or gcloud boots the Ubuntu VM with an automatic evaluation license (10,000 requests quota). Zero sales call or upfront commitment required.

2
Locate Server HWID

Log into the Studio Web UI. The Licensing tab displays your instance's unique, persistent Hardware ID (e.g. A1B2-C3D4-E5F6-7890).

3
In-Place Upgrade

Email the HWID to activate a permanent Node-Locked Production license. Paste the key into the UI—zero data loss, zero re-deployments.

Step-by-Step Deployment Instructions

STEP 1 • Choose Your Deployment Method

Choose whichever deployment method fits your infrastructure workflow:

Method 1: Interactive Cloud Shell

Click Launch in Cloud Shell above. Run cd deployments/gcp && ./deploy.sh to step through the interactive configuration wizard.

Method 2: Direct gcloud CLI 1-Liner

Click Copy gcloud Command. Paste into your local terminal with Google Cloud SDK installed to launch immediately.

Method 3: Terraform / OpenTofu

Use the enterprise Terraform module in deployments/gcp/ for automated CI/CD and GitOps platform pipelines.

Key configuration options supported via metadata and environment variables:

gui_password Master password for the Studio Web UI (admin). Minimum 8 characters.
company_name Company or organization name for white-labeling the Web Studio and Reports (Default: GCP Demo).
Machine Type Default is e2-standard-2 (2 vCPU, 8GB RAM). Scalable to higher compute tiers (c2-standard-4) for heavy workloads.
Persistent Boot Disk 30 GB balanced persistent disk (pd-balanced) retaining encrypted SQLCipher databases across VM restarts.
STEP 2 • Access the Web Studio & API

Once the Compute Engine VM shows RUNNING and initialization completes (~2 to 3 minutes), navigate to:

Studio Web UI: http://<GCP_EXTERNAL_IP>:8000
Interactive OpenAPI Docs: http://<GCP_EXTERNAL_IP>:8000/docs

Log in with username admin and the password you defined in Step 1.

💡 How to find your Live External IP:
  • In Cloud Shell terminal, run: gcloud compute instances list
  • In GCP Console, go to: Compute Engine > VM instances to view the External IP column.
STEP 3 • Upgrade to Node-Locked Production

All audit logs, custom regex patterns, and compliance rules are saved in persistent encrypted storage at /opt/piiguardrails/data. You never need to rebuild or redeploy when your evaluation finishes:

  1. In the Studio Web UI, go to the Licensing tab.
  2. Copy your 16-character Server Hardware ID (e.g. A1B2-C3D4-E5F6-7890).
  3. Email piiguardrails@gmail.com with your Hardware ID and preferred tier (Standard or Enterprise).
  4. Paste your issued commercial key into the license field and click Activate.

Security & Architecture Guarantees

🔒 100% In-VPC Data Sovereignty

No telemetry or inspection payloads ever leave your Google Cloud VPC. All NLP tokenization and redactions run locally on your VM.

🛡️ AES-256 SQLCipher Database

Every database record is encrypted at rest using an automated 256-bit passphrase stored securely on the host.

💾 Persistent Disk Across Reboots

Your database and configuration persist across VM stops, reboots, and maintenance events on the Google Cloud Persistent Disk.

⚙️ Auto-Restart Daemon

Managed via systemd supervisor to ensure high availability and automatic recovery in case of system reboots.