Weaviate Launches Enterprise and Platform Editions

The release adds security, scaling and high-availability features while GraphQL is phased out in favor of native client libraries and gRPC and REST APIs.

Updated on Nov. 18, 2026 in Software

Long receding aisle of unlabeled dark steel server racks under cool blue light, with fiber-optic cables running overhead toward a distant rack.
Weaviate released general availability of its Enterprise and Platform Editions with version 1.40, adding security and high-availability features while phasing out GraphQL. AI Illustration. Upload story photo >

Weaviate announced general availability of its Enterprise Edition and Platform Edition with version 1.40. The editions add security, scaling and high-availability capabilities, and the company has deprecated GraphQL.

Why it matters

The move targets organizations that need production-grade controls for running vector databases at scale. Developers relying on GraphQL will need to migrate to native clients, gRPC or REST as the platform changes.

Version 1.40 introduces Shard Self-Recovery for automated recovery, Deduplicated Backups to cut backup storage and time, and Namespaces for control-plane and data isolation in shared clusters. The company did not disclose performance benchmarks for these features in the announcement.

The players

Weaviate

Weaviate is an open-source vector database company whose software is widely used for building AI search and retrieval applications.

The details

The Enterprise and Platform Editions were announced from Amsterdam. New Cloud clusters are now created without GraphQL, and the company has moved toward native client libraries and gRPC and REST APIs.

Timeline

  1. November 18, 2026: Weaviate announces general availability of the Enterprise and Platform Editions.

  2. December 1, 2026: Clusters that have not used GraphQL in the past 30 days are scheduled for shutdown.

  3. May 1, 2027: All remaining GraphQL clusters are scheduled for shutdown.

  4. First self-hosted minor release after May 1, 2027: GraphQL is disabled by default.

The Tech Race

The shift away from GraphQL moves Weaviate toward the gRPC and REST interfaces that most production vector database platforms use. It also positions the company to compete on enterprise security and high-availability features rather than on query-language flexibility.

Developers using GraphQL with Weaviate will need to move to native client libraries, gRPC or REST before the scheduled shutdowns. Teams running self-hosted deployments should plan for GraphQL to be disabled by default in the first minor release after May 1, 2027.

The takeaway

Teams using GraphQL with Weaviate should audit their cluster usage now and begin migrating to gRPC or REST ahead of the shutdown dates. Starting early reduces the risk of disruption when the deadlines arrive.

What happens next

Clusters unused on GraphQL for 30 days are scheduled for shutdown on December 1, 2026, and all remaining GraphQL clusters on May 1, 2027, with GraphQL disabled by default in the first self-hosted minor release after that date.

Further reading

Explore more software coverage to see how database and developer tooling changes like this one fit into the wider industry.

More information

Visit the Weaviate company website for product documentation and release details.

Source note: This article includes information reported by Brockville Recorder & Times.