On your own servers you run Solr and everything around it. On Opensolr you still own schema.xml and solrconfig.xml; the servers, the restarts, the backups and the error reports around them are handled for you.
Who does each job. Replication and failover run on a resilient cluster; daily backups on plans that include them.
01 · What Opensolr does for you
- Runs the servers, Java and Solr. A watchdog checks every server and restarts Solr when it stops.
- Backs up your index every day at midnight UTC once you turn on the daily schedule, on plans with backups. You can download every backup.
- Keeps a resilient cluster in step: one master and replicas behind one address. Standalone or cluster.
- Explains Solr errors in plain words where it can, with the full stack trace: Error Audit.
- Protects every index with a username and password from the start; IP rules per request handler let you keep writes for your server only.
02 · What stays yours
- Every configuration file: edit it in the browser, upload a ZIP, synonyms, stopwords and protwords.
- Your data, your queries, your Solr clients and modules.
- Your choice of region: where the index runs and on which Solr version.
03 · Real production example
LexFacie, a legal research platform, runs their entire site search on Opensolr using the web crawler with auto enrichment and the embeddable search widget. They are not a tech company — they are lawyers who wanted great search without a DevOps team. They got it. The crawler indexes their content automatically, the widget is live on their site, and they have never once worried about JVM heap settings.
04 · When self-hosting fits
You have Solr expertise in house and want to own every layer: the servers, the upgrades, the replication and the night calls.
Try it on your own data. Site search comes on top: Enterprise Site Search, all in one. Create a free account, see the plans on Pricing, or watch it work first: live demos and RAG in 60 seconds.