GizmoData Cloud
The best way to run DuckDB in the cloud — fully managed GizmoSQL in every cloud and region you need, controlled from a single pane of glass.
Provision DuckDB-powered Arrow Flight SQL clusters, DuckLake catalogs, secrets and the Kubernetes infrastructure beneath them across AWS, Google Cloud and Azure. One control plane, one set of permissions, one audit trail — with the data plane wherever your data already lives.
One production environment, four GizmoSQL clusters, three clouds — Azure, Google Cloud and AWS (in two regions) — all running side by side.
The data plane goes where your data is. The control plane stays in one place.
Most “multi-cloud” platforms mean one deployment per cloud, each with its own console. GizmoData Cloud runs a single control plane that manages Kubernetes data planes in AWS, Google Cloud and Azure at the same time — so a project can have its EU clusters in Ireland, its ML feature store next to GCS in Oregon, and its finance reporting on Azure, and you administer all of it from one organization with one set of roles.
Amazon Web Services
AWS
EKS data planes with Graviton NVMe shapes (r8gd), S3-backed DuckLake, NLB-terminated TLS.
Google Cloud
GCP
GKE data planes on Axion (C4A) local-SSD shapes, GCS-backed DuckLake, per-cloud tuning profiles.
Microsoft Azure
Azure
AKS data planes, Azure Blob / ADLS-backed DuckLake, and Azure Marketplace billing on the roadmap.
Region-aware placement
Catalogs, secrets, firewall rules and Kubernetes clusters can all be qualified by cloud and region. When a cluster is created, defaults resolve to the nearest matching region up the scope chain — exact region first, then cloud-wide, then neutral.
Egress governance, built in
Turn on cross-region mount governance and the platform refuses to attach a catalog whose data lives in a different region from the compute — the exact error tells you which region each side is in. No surprise inter-region bills.
Shapes that match the cloud
Instance sizes are cloud-specific (r8gd on AWS, C4A on GCP, …) and validated against the target Kubernetes cluster, so you cannot accidentally ask an EKS cluster for an Azure shape.
Provision GizmoSQL clusters in any cloud, from one screen
Every cluster is a fully managed GizmoSQL deployment — DuckDB behind Apache Arrow Flight SQL — on Kubernetes in the cloud and region you choose. Pick an instance shape, mount your catalogs and secrets, and it is serving queries in minutes.
- Instance shapes per cloud: AWS Graviton NVMe (r8gd), GCP Axion local-SSD (C4A), Azure — picked from a live, priced menu
- Autoscaling (min/max replicas, CPU & memory targets) plus calendar-based autoscaling schedules
- Core or Enterprise license editions; instrumentation & query-log catalogs; OAuth/SSO; read-only and lockdown modes
- Start, stop, edit and auto-terminate idle clusters — with the cost shown before you commit
Lakehouse catalogs that follow your data — not the other way round
A catalog is a DuckLake (or PostgreSQL) metastore plus the object storage that holds its Parquet data. Register one and mount it to as many clusters as you like; GizmoData Cloud keeps track of which clusters have it attached, migrates it automatically, and can set it as the default for a whole scope.
- DuckLake catalogs on S3, GCS, Azure Blob/ADLS or Cloudflare R2 — with a PostgreSQL metastore you bring or we manage
- Region-aware: each catalog knows the cloud and region its data lives in, so compute can be placed next to it
- Cross-region mount governance: organizations can block mounting a catalog from a different region, so you never pay surprise egress
- Schema browser and refresh without spinning up compute; per-catalog access rules; encrypted catalogs; history retention for instrumentation catalogs
Credentials stored once, mounted everywhere they belong
S3, GCS, Azure Storage, PostgreSQL and ADBC credentials are encrypted at rest in the control plane and injected into GizmoSQL pods as DuckDB secrets at start-up. Scope a secret to an organization, project, environment or a single deployment target and it is available to every cluster underneath.
- Typed secret templates per provider — including AWS credential chains (IRSA / instance profiles) with no static keys
- Catalog-managed secrets are created and rotated alongside the catalog that owns them
- External secret providers: read from AWS Secrets Manager or your own store instead of copying values in
- One-click “mount to scoped clusters” pushes a new secret to every running cluster in scope
Query any cluster from the browser — as yourself
A Monaco-powered SQL editor is built into every cluster. Sessions run under your own Nexus permissions (admin, user or read-only), results stream back over Arrow Flight SQL, and saved SQL scripts can be attached as cluster start-up scripts.
- Multi-statement batches, run-selection, row limits and query timeouts
- Catalog and schema pickers populated live from the engine
- Generate a scoped connection token for DBeaver, Python (ADBC), JDBC or the GizmoSQL UI
Bring your own Kubernetes — or use ours
The control plane is cloud-agnostic. Register EKS, GKE and AKS clusters (yours or GizmoData-managed) and mark a default per cloud at any scope; new GizmoSQL clusters resolve the nearest default up the hierarchy exactly as provisioning will. Firewall rules, node-scheduling profiles, workload identities and cloud-tuning profiles are managed the same way.
- Seven registered Kubernetes clusters across three clouds in the example above — each with its own ingress domain
- Firewall rules (CIDR allow-lists) applied at the load balancer, defaulted per organization
- Node-scheduling profiles and workload identities for IRSA / Workload Identity access to storage
- Cloud-tuning profiles: per-cloud DuckDB thread and memory tuning, applied and reported per cluster
Guided where it helps, explicit where it matters
The cluster wizard walks you through Kubernetes cluster, shape, engine, catalogs, secrets, security and autoscaling — inheriting scope defaults at every step, and showing you exactly what it resolved.
The best way to run DuckDB in the cloud
A bold claim, so here is the case. DuckDB is the fastest analytical engine most teams will ever touch — but on its own it is a library. GizmoData Nexus is the control plane that turns it into a secure, multi-tenant, multi-cloud service: GizmoSQL for the serving, DuckLake for the data, and everything around them handled.
Real DuckDB, served properly
GizmoSQL wraps the actual DuckDB engine in an Apache Arrow Flight SQL server — concurrent sessions, TLS, authentication, and columnar results streamed to any Arrow client. Not a serverless facade in front of a different engine.
Hardware DuckDB was made for
Single-node analytics wants big memory and fast local disk. Nexus provisions GizmoSQL on memory-optimised, local-NVMe shapes — AWS Graviton r8gd, GCP Axion C4A local-SSD — with per-cloud thread and memory tuning applied automatically.
DuckLake as a first-class citizen
Lakehouse catalogs on S3, GCS or Azure with a PostgreSQL metastore are a native object — mountable to any number of clusters, region-aware, schema-browsable without compute, and governed so scans never silently cross regions.
Any cloud, any region, one console
A single control plane manages Kubernetes data planes in AWS, Google Cloud and Azure at once. Put compute next to each dataset and administer everything with one hierarchy, one set of roles, one audit trail.
Enterprise controls without the enterprise price tag
SSO/OAuth, per-catalog permissions, firewall rules, encrypted secrets, workload identities, instrumentation catalogs and query queuing — the pieces you would otherwise bolt on yourself, already wired in.
Operated like software, not snowflakes
Every deployment is a versioned Helm release with a changelog, an automated end-to-end smoke test that provisions a real cluster and runs a query, and rollback on failure. Upgrades are boring — on purpose.
Everything else a data platform needs
Not a thin wrapper around a container — the operational layer your team would otherwise have to build.
Organizations, projects & environments
A real hierarchy — organization → project → environment → deployment target — so production and staging never share defaults by accident.
Role-based access at every level
Admin, writer and reader roles scoped to an organization, project or environment. Invite teammates by email; roles flow down the hierarchy.
Audit trail
Every change made through the API is recorded — who, what, when and with which request — and searchable from the portal.
Autoscaling & schedules
Scale replicas on CPU and memory targets, or on a calendar: scale up for the morning dashboard rush, down for the weekend.
Firewall rules & TLS everywhere
CIDR allow-lists per cluster, TLS terminated at the load balancer or the pod, and OAuth/SSO for GizmoSQL sessions.
Instrumentation & query logs
Point a cluster at an instrumentation catalog and every query, session and P99 lands in DuckLake tables you can query yourself.
Database files
Upload DuckDB files to a persistent volume with S3 backups, mount them read-only or single-writer, and import them as a background job.
Built-in support & incidents
Open a ticket from any cluster, see platform incidents in-app, and get Sev-1 SMS paging on Enterprise plans.
SQL scripts & notebooks
Save SQL scripts to reuse across clusters or run them at start-up; notebooks for exploratory analysis.
Frequently Asked Questions
What is GizmoData Cloud?
GizmoData Cloud is the fully managed service for GizmoSQL. Its control plane — the Nexus portal and API — lets you provision GizmoSQL clusters, DuckLake catalogs, secrets and infrastructure across AWS, Google Cloud and Microsoft Azure from a single pane of glass, with organization/project/environment scoping, role-based access and an audit trail.
Which clouds and regions does GizmoData Cloud support?
The data plane runs on Kubernetes in AWS (EKS), Google Cloud (GKE) and Microsoft Azure (AKS). You can register clusters in as many regions as you need and set a default per cloud at any scope. Because catalogs are region-aware, GizmoData Cloud can place compute next to your data and can block cross-region mounts that would incur egress.
Is the control plane tied to one cloud?
No. The control plane is cloud-agnostic and can manage Kubernetes clusters in several clouds at once. GizmoData also offers Cloud at Customer, where the control plane and data planes run inside your own cloud account — see gizmodata.com/cloud/at-customer.
What is a DuckLake catalog?
DuckLake is the open lakehouse format from the DuckDB team: a SQL metastore (PostgreSQL) plus Parquet files in object storage. In GizmoData Cloud a catalog bundles the metastore credentials, the storage credentials and the data path, so it can be mounted to any number of GizmoSQL clusters and shared across teams.
Can I bring my own Kubernetes clusters, storage or credentials?
Yes. Register your own EKS/GKE/AKS clusters, point catalogs at your own buckets and metastores, and read credentials from your own secret store via an external secret provider. GizmoData-managed infrastructure is available where you would rather not run it yourself.
How do I get access?
GizmoData Cloud is in early access. Contact us and we will set up an organization for you — or, if you already run GizmoSQL Enterprise, we can host it for you today.