Self-hosting is on the roadmap.
It isn't available yet and we aren't going to put a date on it. Today AZ-Five is hosted and operated by us. This page exists so you know where we intend to go, not to imply you can do it now.
What we intend to build.
The architecture was chosen with this in mind — open storage formats, a query engine that reads tables in place, and every connection expressed as configuration. None of that makes it shipped, and we would rather say so than let a roadmap item sell the product for us.
- The same product, not a cut-down build
- The intention is one image running everything the hosted platform runs — ingestion, pipelines, quality, lineage, dashboards, product analytics and model monitoring. A self-hosted edition that quietly drops half the network would not be worth shipping.
- Your object storage, your database
- The lakehouse is already open Parquet with a Delta transaction log, and the application already reads every connection from configuration. Pointing it at storage and a database you operate is the substance of the work.
- What it will ask of you
- Somewhere to run containers, a PostgreSQL instance, a Redis-compatible cache and S3-compatible object storage — plus someone willing to own upgrades. That last one is the real cost, and it is why hosted is the default recommendation.
STATUS · PLANNED · NO SHIP DATE
If this is a requirement, tell us.
Self-hosting moves up the list when it is blocking a real decision rather than appearing on a wish list. If your procurement or compliance position needs it, say so at hello@az-five.com — and in the meantime, Enterprise runs on a dedicated single-tenant instance, which solves the isolation half of the problem today.
See EnterpriseThe hosted platform is ready now.
Everything on the network, running today, with unlimited seats and no card required.