We are building a managed OpenSearch service

OpenSearch has reached a stable release. We said in January that the answer to the Elasticsearch relicensing was an engine that is genuinely open with more than one vendor behind it, and this is the one. A managed service is in build.

Why this fork and not another

When Elastic relicensed, the question was never whether somebody would fork the code. Anyone could. The question was whether a fork would attract enough independent maintenance to still be alive in three years.

OpenSearch is Apache 2.0 throughout, including the security, alerting and SQL plugins that used to sit under Elastic’s own licence, and it has more than one company’s roadmap holding it up. That is the test we said we would apply.

What the service will be

The same shape as our Elasticsearch service: a cluster sized by tier and node count, priced by the machine, with provisioning, upgrades, backups and monitoring run by us.

We are also building the migration path, because a managed service that can only be entered is not much of an improvement on the thing it replaced. Moving an existing Elasticsearch cluster across should be something we do with you, not something you schedule a weekend for.

When

In the coming months. Elasticsearch clusters keep running here in the meantime and nobody is being moved on a timetable of ours.

If you are weighing the same decision for your own stack, hello@clusternest.com reaches us and we are happy to talk about it before there is anything to sell you.