Release notes

v25.1

Self-managed Materialize is available as a paid Enterprise Edition and a free Community Edition:

	Enterprise Edition	Community Edition
Maximum Usage Limits (Memory)	None	24 GiB
Maximum Usage Limits (Disk)	None	48 GiB
Support	Per terms of your license	Community slack
License	Paid Enterprise License - Contact Us	BSL/Privacy Policy

Materialize Operator

For self-managed deployments, Materialize provides the Materialize Operator. The Materialize Operator manages Materialize environments within your Kubernetes infrastructure.

Materialize provides the Materialize Operator Helm Chart, a Helm Chart for installing and upgrading the Materialize Operator. The chart repository is: https://materializeinc.github.io/materialize.

Releases and Compatibility

Materialize Operator	orchestratord version	environmentd version	Release date	Notes
v25.1.7	v0.138.0	v0.130.8	2025-04-08
v25.1.6	v0.130.8	v0.130.8	2025-03-26	This release uses an incorrect version of `orchestratord` as its default (v0.130.8 instead of v0.138.0). This has been fixed in v25.1.7.
v25.1.5	v0.138.0	v0.130.7	2025-03-25
v25.1.4	v0.138.0	v0.130.7	2025-03-25
v25.1.2	v0.130.4	v0.130.4	2025-03-11

Terraform helpers

To help you get started, Materialize also provides some template Terraforms.

! Important:

These modules are intended for evaluation/demonstration purposes and for serving as a template when building your own production deployment. The modules should not be directly relied upon for production deployments: future releases of the modules will contain breaking changes. Instead, to use as a starting point for your own production deployment, either:

Fork the repo and pin to a specific version; or
Use the code as a reference when developing your own deployment.

Sample Module	Description
terraform-helm-materialize	A sample Terraform module for installing the Materialize Helm chart into a Kubernetes cluster.
Materialize on AWS	A sample Terraform module for deploying Materialize on AWS Cloud Platform with all required infrastructure components. See Install on AWS for an example usage.
Materialize on Azure	A sample Terraform module for deploying Materialize on Azure with all required infrastructure components. See Install on Azure for an example usage.
Materialize on Google Cloud Platform (GCP)	A sample Terraform module for deploying Materialize on Google Cloud Platform (GCP) with all required infrastructure components. See Install on GCP for an example usage.

Terraform version	Notable changes
v0.4.3	Defaults to using Materialize Operator v25.1.7 (via `terraform-helm-materialize` v0.1.12). Versions v0.4.0 defaulted to Materialize Operator v25.1.6 which used an incorrect version of the `orchestratord`).
v0.4.0	By default, deploys `cert-manager` and a self-signed `ClusterIssuer`.
v0.3.1	By default, deploys OpenEBS and NVMe instance storage to enable spill-to-disk.
v0.3.0	By default, deploys the AWS Load Balancer Controller as well as Network Load Balancers (NLBs) for each Materialize instance (i.e., the `create_nlb` flag defaults to `true`). The NLBs, by default, are configured to be internal (i.e., the `internal_nlb` flag defaults to `true`).
v0.2.7	Initial release of Materialize on AWS.

If upgrading from a deployment that was set up using an earlier version of the Terraform modules, additional considerations may apply when using an updated Terraform modules to your existing deployments.

See also Upgrade Notes for release-specific upgrade notes.

Terraform version	Notable changes
v0.3.4	Defaults to using Materialize Operator v25.1.7 (via `terraform-helm-materialize` v0.1.12). Version v0.3.1 defaulted to Materialize Operator v25.1.6 which used an incorrect version of the `orchestratord`).
v0.3.1	By default, deploys load balancers for each Materialize instance (i.e., the `create_load_balancer` flag defaults to `true`). The load balancers, by default, are configured to be internal (i.e., the `internal_load_balancer` flag defaults to `true`).
v0.3.0	By default, deploys `cert-manager` and a self-signed `ClusterIssuer`.
v0.2.0	The providers must be specified. The `examples/simple/main.tf` has been updated to reflect this. The network_config is now a required input. Previously, a default value was provided. The `examples/simple/main.tf` has been updated to reflect this.
v0.1.4	Initial release of Materialize on Azure.

See also Upgrade Notes for release specific notes.

Terraform version	Notable changes
v0.4.0	By default, deploys OpenEBS and NVMe instance storage to enable spill-to-disk. Associated with this change, the default `gke_config.machine_type` has changed from `e2-standard-4` to `n2-highmem-8`.
v0.3.4	Defaults to using Materialize Operator v25.1.7 (via `terraform-helm-materialize` v0.1.12). Versions v0.3.0-v0.3.3 defaulted to Materialize Operator v25.1.6 which used an incorrect version of the `orchestratord`.
v0.3.1	Added configuration options (`storage_bucket_versioning` and `storage_bucket_version_ttl`) for storage bucket versioning. By default, versioning is disabled (i.e., `storage_bucket_versioning` is set to `false`).
v0.3.0	By default, deploys `cert-manager` and a self-signed `ClusterIssuer`. By default, deploys load balancers for each Materialize instance (i.e., the `create_load_balancer` flag defaults to `true`). The load balancers, by default, are configured to be internal (i.e., the `internal_load_balancer` flag defaults to `true`). The network_config variable no longer has a default value. Previously, a default value was provided.
v0.2.0	The providers must be specified. The `examples/simple/main.tf` has been updated to reflect this.
v0.1.7	Initial release of Materialize on GCP.

See also Upgrade Notes for release specific notes.

Known Limitations

Item	Status
IAM Built-in authorization mechanisms.	In progress
License Compliance License key support to make it easier to comply with license terms.	In progress
Spill to disk Provide Terraform modules to set up locally-attached NVMe storage to support workloads that are larger than can fit into memory.	AWS: Available in Materialize on AWS Terraform v0.3.1+ GCP: Available in Materialize on GCP Terraform v0.4.0+ Azure: In progress
Ingress from outside cluster Provide Terraform modules to set up ingress from outside the Kubernetes cluster hosting self-managed Materialize.	AWS: Available in Materialize on AWS Terraform v0.3.0+ GCP:Available in Materialize on GCP Terraform v0.3.0+ Azure: Available in Materialize on Azure Terraform v0.3.1+
AWS Connections AWS connections require backing cluster that hosts Materialize to be AWS EKS.
EKS/Azure Connections
Temporal Filtering Memory optimizations for filtering time-series data are not yet implemented.

Self-managed versioning and lifecycle

Self-managed Materialize uses a calendar versioning (calver) scheme of the form vYY.R.PP where:

YY indicates the year.
R indicates major release.
PP indicates the patch number.

For Self-managed Materialize, Materialize supports the latest 2 major releases.