Deploy

Run gene.zip in your own cloud

Deploy the compression engine into your own Google Cloud project on Confidential Space. Your genomic data never leaves your network, and the engine runs sealed (you can't see inside it; output is encrypted).

Before you start

Your gene.zip API key — this is also your cloud license key. Create one on your dashboard (or settings) and use it as GENE_LICENSE_KEY below.
A Google Cloud project and a GCS bucket with a BAM in it.

Option A — One click (Cloud Shell)

Open Cloud Shell with the deploy tutorial pre-loaded, then paste your API key (license key) and bucket paths when prompted:

Open in Google Cloud Shell repo activates the button

Option B — One command

In Cloud Shell (or any terminal with gcloud):

export PROJECT=$(gcloud config get-value project)
export GENE_LICENSE_KEY=gz_live_xxxxxxxx          # your gene.zip API key (= license key) from /dashboard
export INPUT=gs://YOUR_BUCKET/sample.bam          # your BAM
export OUTPUT=gs://YOUR_BUCKET/sample.bcz.enc     # compressed output

curl -fsSL https://gene.zip/cloud/gcp.sh | bash

The script enables the needed APIs, creates a workload service account scoped to your bucket, and launches the confidential job. Watch for the result:

gcloud storage ls $OUTPUT     # appears in ~1–2 minutes

Restore (decode) — always available

Decoding never needs a license check, so you always have access to your data:

export OP=decompress
export INPUT=gs://YOUR_BUCKET/sample.bcz.enc
export OUTPUT=gs://YOUR_BUCKET/restored.bam
curl -fsSL https://gene.zip/cloud/gcp.sh | bash

What you get

Your data stays in your VPC — gene.zip never receives it.
Sealed engine — runs on Confidential Space (encrypted memory, no SSH); the codec is native, not inspectable.
Encrypted output — you only ever see your original data and an encrypted .bcz.enc.
Pay-per-use — short-lived confidential VM (Google bill) + your gene.zip plan for stored data.

Options: MODE=lossless|8bin|2bin (codec fidelity); OP=deep co-compresses a BAM + its FASTQ(s). Need a no-internet network? Use Cloud NAT for egress to the license endpoint — ask us for the locked-down variant.

AWS & Azure coming soon

The same confidential-compute deployment is rolling out for AWS Nitro Enclaves and Azure Confidential Containers. Contact us for early access.