How do I move off Weaviate Cloud HA-by-Default Pricing Transition without getting stuck?
Choose whether to stay on Weaviate Cloud, switch deployment tier, or move off-platform now that new Weaviate Cloud pricing makes paid clusters HA by default and bills storage plus backups separately.
Blockers
- Weaviate's October 2025 pricing update states that all paid plans moved to HA by default.
- Weaviate's October 2025 pricing update states that storage became an explicit pricing dimension in addition to vector dimensions.
- Weaviate's October 2025 pricing update states that backups became an explicit pricing dimension and are billed separately.
Who this is for
- cost-sensitive
- low-ops
- enterprise
Candidates
Stay on Weaviate Cloud Flex
As of 2026-04-02, Weaviate's current pricing page lists Flex as the entry paid plan starting at "$45 /mo" with monthly pay-as-you-go billing. Flex runs on Shared Cloud and includes HA / replication with a 99.5% uptime target. Weaviate's October 2025 pricing update states that all paid plans moved to HA by default and that storage and backups became explicit pricing dimensions in addition to vector dimensions. The pricing FAQ says the monthly minimum covers vector dimensions and storage, while backups are billed on top based on data volume and retention.
When to choose
Use this when you want the lowest managed-cloud entry point and can stay within Shared Cloud operational limits. It is the best fit when low-ops matters more than avoiding the new HA baseline cost model, because Flex is now the cheapest paid HA option Weaviate publishes.
Tradeoffs
Lowest published paid entry price and managed operations, but you accept HA-driven replication costs and separate backup charges. SLA and support are weaker than the higher contracted tiers.
Cautions
As of 2026-04-02, this transition has already occurred for new customers. Vector-dimension billing now multiplies by replication factor because paid clusters are HA, and backups are not included in the monthly minimum.
Move to Weaviate Cloud Premium
As of 2026-04-02, Weaviate's pricing page lists Premium starting at "$400 /mo" with a prepaid commitment model. The plan includes stronger support, higher reliability targets, and a choice of shared or dedicated deployment on the pricing page, with up to 99.95% uptime. The compare table shows 30-day backup retention for Premium shared deployment and 45-day retention for Premium dedicated deployment, and the SLA page matches those retention windows for subscriptions beginning October 27, 2025 or later. Premium also exposes enterprise features such as SSO/SAML, and dedicated deployment adds features like BYO IdP, HIPAA, PrivateLink on AWS, and customer-managed keys.
When to choose
Use this when you are staying on Weaviate Cloud but need stronger SLAs, longer backup retention, or dedicated infrastructure. It is the current managed path when compliance, security controls, or higher-severity support response matter more than entry cost.
Tradeoffs
Higher minimum spend and sales-led commitment, but better uptime targets, support response, and security/compliance options. It reduces migration work compared with leaving Weaviate Cloud.
Cautions
The October 2025 announcement described a three-plan structure including "Plus," but as of 2026-04-02 the public pricing page prominently lists Flex and Premium. Check official sales documentation before budgeting around contracted plan naming or deployment packaging.
Move off Weaviate Cloud and self-manage Weaviate OSS
Weaviate's October 2025 pricing update explicitly says OSS installations remain an option if you prefer to self-manage. The current pricing FAQ also states that Weaviate Cloud uses the open-source Weaviate project, while the managed service adds administration relief and extra hosted features such as integrated services. As of 2026-04-02, this is the main way to avoid the managed-cloud pricing transition rather than merely changing Weaviate Cloud tier. It also preserves access to deployment patterns that Weaviate says are only available on Dedicated Cloud or self-hosted setups, such as moving tenants between hot, warm, and cold storage.
When to choose
Use this when the October 2025 cloud pricing changes materially worsen your cost model or when you need full deployment control. It is the better fit when you are willing to absorb infrastructure and operations work to avoid managed-plan minimums and packaging constraints.
Tradeoffs
Maximum control and no dependency on Weaviate Cloud plan packaging, but you lose the managed service's automated operations, bundled SLAs, and support posture. You also take on backup, uptime, and upgrade responsibility yourself.
Cautions
Weaviate's public cloud pricing pages do not publish a self-hosting TCO comparison, so check official docs and your own infra costs before committing. If you rely on Weaviate Cloud support-managed backup restore workflows, those do not carry over automatically to self-managed deployments.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "How do I move off Weaviate Cloud HA-by-Default Pricing Transition without getting stuck?"