YugabyteDB Managed vs Self-Hosted License and Support — what do I need to change?
Decide whether to adopt YugabyteDB managed service or self-host now that support boundaries, feature packaging, and enterprise licensing matter more than raw benchmark claims.
Blockers
- package/yugabytedb-v2025.2 — EOL 2028-06-11
- package/yugabytedb-v2024.1 — EOL 2026-03-07
- package/yugabytedb-v2.20 — EOL 2026-05-13
- Lock-in via package/yba-installer
- support_ended_and_migration_needed
Who this is for
- enterprise
- compliance
- low-ops
- cost-sensitive
- high-scale
Candidates
YugabyteDB Aeon managed service
YugabyteDB Aeon is Yugabyte's fully managed DBaaS on AWS, Azure, and GCP. As of 2026-03-20, Aeon pricing starts at "$125 / vCPU / month" for Standard and "$167 / vCPU / month" for Professional; Enterprise pricing is contact-sales, and storage plus transfer are billed separately. Yugabyte states the same pricing model applies across Aeon deployment options, including BYOC, with billing by the minute under pay-as-you-go or by committed vCPU under subscription. The official pricing and product pages position Aeon as the low-ops path with managed upgrades, automatic backups, and 365x24x7 support.
When to choose
Use this when "low-ops" plus "enterprise" or "compliance" matters more than infrastructure control. The decisive factor is that Yugabyte owns upgrades and day-2 operations while keeping the product packaging consistent across fully managed and BYOC deployments.
Tradeoffs
Fastest path to production and clearest vendor support boundary, but it is the highest direct software spend and Enterprise-tier features still move you into contact-sales pricing.
Cautions
As of 2026-03-20, self-service migration from Sandbox to Dedicated is not supported, so trial-to-production handoff may need vendor help. Sandbox clusters are free but limited to one node, 10GB, and a preview release, so they are not a production baseline.
Self-host YugabyteDB OSS directly
YugabyteDB itself is Apache 2.0 licensed, and Yugabyte states that as of early 2025 all previously commercial enterprise features are available in the open source project, with no separate Community versus Enterprise database editions. As of 2026-03-20, the latest listed LTS release series is "v2025.2", released on 2025-12-11 with maintenance support through 2027-12-11 and EOL on 2028-06-11. This removes the old database-feature licensing blocker, but your team still owns provisioning, upgrades, backups, observability, and incident response. The database software is free, but the operational burden is yours.
When to choose
Use this when "cost-sensitive" and infrastructure control matter more than vendor-operated convenience, and your team can run a distributed SQL system safely. The decisive factor is that the database feature boundary is now open source, so the remaining decision is mainly ops ownership versus managed support.
Tradeoffs
No database license fee and no feature gating inside the core database, but you lose managed upgrades, unified billing, and the cleanest escalation path during incidents.
Cautions
As of 2026-03-20, release support windows matter: "v2024.1" reached EOL on 2026-03-07, and "v2.20" reaches EOL on 2026-05-13. Do not treat old 2.x series builds as a safe long-term default when newer 2024.x and 2025.x series are the supported lines.
Self-host with YugabyteDB Anywhere
YugabyteDB Anywhere is Yugabyte's self-managed control plane for running YugabyteDB in your own cloud, data center, or Kubernetes environment. Official comparison pages describe it as "managed by you with Yugabyte orchestration software," the middle ground between Aeon and pure OSS. As of 2026-03-20, YugabyteDB Anywhere uses the same current release train naming as YugabyteDB, with "v2025.2" as the latest listed LTS series, but Anywhere can only deploy equivalent or earlier YugabyteDB versions than the Anywhere instance itself. As of 2026-03-20, public list pricing for Anywhere is not shown on the official pricing page, so check official sales docs.
When to choose
Use this when you need private-cloud or on-prem placement and want a vendor control plane without handing runtime custody fully to Yugabyte. The decisive factor is whether your compliance or network boundary forces self-hosting but you still want structured orchestration and lifecycle tooling.
Tradeoffs
Stronger operational tooling than pure OSS self-hosting, but still not low-ops in the same way as Aeon because infrastructure and platform operations remain your responsibility.
Cautions
As of 2026-03-20, YugabyteDB Anywhere support for Replicated installation has already ended; new installs must use YBA Installer, and older Replicated installs need migration. If you want a newer YugabyteDB version, you may need to upgrade YugabyteDB Anywhere first because it cannot deploy newer database versions than itself.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "YugabyteDB Managed vs Self-Hosted License and Support — what do I need to change?"