Choose for the workload you have—and the platform you want
Support Solr today. Build a credible modernization path for tomorrow.
The right provider should stabilize production, improve search quality, and give you an honest choice between continuing on Solr and validating a move to NextSearch 2.3.
Response model
Match incident severity to an explicit response and escalation process.
Engineering continuity
Ask who learns your schema, topology, queries, and operating constraints.
Modernization option
Require an upgrade or migration path backed by workload-specific evidence.
Provider comparison
Three different support models
This is a fit-based comparison, not a universal ranking. Confirm current SLAs, staffing, scope, and commercial terms directly with each provider.
Nextbrick
Independent specialistBest fit: Independent Solr engineering, production support, and migration
A specialist option for teams that need hands-on SolrCloud operations, performance and relevance engineering, upgrades, or an evidence-led move to NextSearch 2.3.
Lucidworks
Best fit: Organizations already standardized on Fusion
A commercial search platform and support path for teams whose Solr environment is part of a Lucidworks Fusion deployment.
Apache Solr community
Best fit: Self-sufficient teams without a production SLA requirement
Project documentation and community channels are valuable for research and troubleshooting, but they do not replace a contracted incident-response SLA.
One team for Solr support and NextSearch 2.3 migration.
Keep Solr stable while Nextbrick inventories compatibility, benchmarks production-shaped workloads, validates relevance and field parity, and prepares a staged cutover with rollback planning.
See the Solr-to-NextSearch plan
Not sure whether to support, upgrade, or migrate?
Start with the current workload, risks, costs, and roadmap. The recommendation should follow the evidence.