genblaze-google
Google provider adapters for genblaze — Veo text-to-video and Imagen text-to-image — with SHA-256 provenance manifests on every output.
genblaze-google wraps Google's generative media models (Veo 2, Veo 3, Imagen 3) as genblaze providers via the unified google-genai SDK. Works with both Gemini API keys and Google Cloud Vertex AI authentication. Compose Veo/Imagen calls into multi-step AI pipelines, persist outputs to Backblaze B2 or any S3-compatible store, and emit a tamper-evident provenance manifest for every run.
Why genblaze-google
- Veo 3 with synchronized audio — text-to-video + native audio, wrapped in a provenance manifest.
- Imagen 3 high-fidelity images — photorealistic stills with full parameter tracking.
- Two auth modes — Gemini API (
GEMINI_API_KEY) for quick start, Vertex AI for enterprise / GCP orgs. - Same SDK, any provider — swap to Sora, Runway, Luma, Flux without rewriting pipeline logic.
- Provenance by default — SHA-256 hash + canonical manifest on every generation.
- Durable storage — plug
genblaze-s3in for Backblaze B2 / AWS S3 / Cloudflare R2 / MinIO.
Providers + models
| Provider class | Modality | Models |
|---|---|---|
VeoProvider |
video | veo-3.0-generate-001 (with audio), veo-3.0-fast-generate-001, veo-2.0-generate-001 |
ImagenProvider |
image | imagen-3.0-generate-002, imagen-3.0-fast-generate-001 |
Each is registered via entry points (google-veo, google-imagen).
Install
pip install genblaze-google
Quickstart — Veo 3 text-to-video (with audio)
export GEMINI_API_KEY="..." # or use Vertex AI auth
from genblaze_core import Modality, Pipeline
from genblaze_google import VeoProvider
run, manifest = (
Pipeline("veo-demo")
.step(VeoProvider(), model="veo-3.0-generate-001",
prompt="A time-lapse of a coral reef coming to life, colorful fish "
"swimming through vibrant coral, natural ocean lighting",
modality=Modality.VIDEO,
aspect_ratio="16:9", duration_seconds="8", resolution="720p",
enhance_prompt=True)
.run(timeout=600)
)
print(run.steps[0].assets[0].url, manifest.canonical_hash)
Vertex AI auth instead:
provider = VeoProvider(project="my-gcp-project", location="us-central1")
Vertex returns generated video bytes inline (no Files API on Vertex), so
fetch_output() saves them to a local file and exposes a file:// asset —
pass output_dir to control where those files land (default: system temp),
same as ImagenProvider below.
Quickstart — Imagen 3 text-to-image
from genblaze_google import ImagenProvider
run, manifest = (
Pipeline("imagen-demo")
.step(ImagenProvider(output_dir="output/images"),
model="imagen-3.0-generate-002",
prompt="A photorealistic aerial view of a coral reef teeming with tropical fish",
modality=Modality.IMAGE, aspect_ratio="16:9")
.run(timeout=120)
)
Persist to Backblaze B2
from genblaze_core import KeyStrategy, ObjectStorageSink
from genblaze_s3 import S3StorageBackend
storage = ObjectStorageSink(
S3StorageBackend.for_backblaze("my-bucket"),
key_strategy=KeyStrategy.HIERARCHICAL,
)
# pass sink=storage to .run(…) to push assets + manifest to B2
Backblaze B2 is the recommended default sink for genblaze — cost-efficient, S3-compatible, with Object Lock for tamper-evident manifests.
Credentials
| Auth mode | Env var / config |
|---|---|
| Gemini API (quickest) | GEMINI_API_KEY — https://aistudio.google.com/apikey |
| Vertex AI | VeoProvider(project=..., location=...) + gcloud auth application-default login |
Documentation
- Main repo: https://github.com/backblaze-labs/genblaze
- Examples:
veo_video_pipeline.py·imagen_pipeline.py
Related packages
genblaze-core— the pipeline SDKgenblaze-s3— durable storage on Backblaze B2 and other S3-compatible backends
License
MIT
Metadata
Release files for genblaze-google 0.3.4
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| genblaze_google-0.3.4.tar.gz | 33.4 kB | With provenance | Details for genblaze_google-0.3.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| genblaze_google-0.3.4-py3-none-any.whl | Python 3 | none | any | Details for genblaze_google-0.3.4-py3-none-any.whl |
Total release size: 61.5 kB
Release files / genblaze_google-0.3.4.tar.gz
| Download URL | genblaze_google-0.3.4.tar.gz |
|---|---|
| Size | 33.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
17a2b7e8ffbf6cd3d3cf3de964b0ff84102f475d5f51c4ce6887656b13f7c54a
|
|
BLAKE2b-256 checksum How to use checksums |
370f9b9c291296eb1f6f4d21de9d5289f5ba89ddad91ac18062b448efd773fd4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.
Transparency logRelease files / genblaze_google-0.3.4-py3-none-any.whl
| Download URL | genblaze_google-0.3.4-py3-none-any.whl |
|---|---|
| Size | 28.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2e0ab6855b3c617b73131107870558fb59cf4b368a5c57ab0e483011f432c3ee
|
|
BLAKE2b-256 checksum How to use checksums |
0fb015fe1d842672c3a05f3df21e04b082583fc09d93a395b4f7fcb659b9b59d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.
Transparency logSecurity for genblaze-google 0.3.4
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for genblaze_google-0.3.4.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 28, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.