Information Security Policy
This is how Opensolr protects the two things you trust us with: your account, and the data inside your indexes. It covers what we hold, where it lives, who can reach it and what keeps it that way. We review it every quarter and update it as the platform changes.
The five gates, in the order a request meets them.
Opensolr is certified for information security management and for quality management. Both are audited standards, not self-declared ones. About our certifications
We re-run our internal security review every quarter, patch what it finds across the fleet and refresh the published security overview with the results.
Our controls are mapped to the five SOC 2 Trust Services Criteria and to the SIG and CAIQ questionnaires. A PDF security overview, completed questionnaires, a data processing agreement and an architecture overview are available on request. Open the Trust Center
02 · What we hold, and where
Account data
Your email address and password, your API keys and the log of what was done in your account. Payment details never reach our servers: billing runs through Stripe. You see your account in the Control Panel; team members never do.
Index data
The documents you index, the configuration files of the index and the log of requests made to it. You pick the region when you create an index, from datacenters run by AWS, Hetzner, HostHatch and Alibaba Cloud. The data stays where you put it.
03 · Who can get in
Your sign-in
A password, and optionally a second factor: an authenticator app, SMS codes and recovery codes. reCAPTCHA protects the sign-in, registration and password reset forms. Two-factor authentication.
New accounts are screened
An address is checked before the registration code is sent: why an address can be refused.
Teams instead of shared logins
Colleagues sign in with their own account and work only on the indexes you share with them, with full control of those indexes. They never see your account, billing, keys or team. Removing a member ends the access at once. Teams.
A password on every index
Every request to an index needs its username and password. HTTP Basic Auth and the defaults of a new index.
IP rules per request handler
Let the world search, but let only your own server write. IP restriction.
Browser calls only from your domains
Cross-origin requests straight to an index work only from the origins we whitelisted for it. CORS and origin whitelisting.
04 · API keys
One master key per account can do everything; scoped keys can do only what you grant, on the indexes you pick, until a date you choose. Only you manage the keys of your account. Rate limits and monthly quotas count against the account, whichever key is used. Master key and scoped keys.
05 · Staying up
Backups you control
Back up an index whenever you want, or every day, download the files and restore the whole index or its configuration. Backups.
A watchdog that restarts
The servers are checked all the time, and a server that stops answering gets its services restarted automatically.
Abuse is dropped early
Every Solr server limits requests and connections per address in its firewall, so a flood is discarded before it reaches Solr.
You are told
Abusive query patterns on your index trigger an alert to you.
06 · Hardening and trail
Solr is never public
Solr listens on localhost only. The single way in is HTTPS with valid credentials, from an allowed address.
Risky features off
The data import handler is off by default: DataImport Handler. Known vulnerabilities are mitigated on every Solr version we run: log4j, for example.
Logs you can read
The Account › Action Log of your account, and the request log of each index in its analytics. Analytics and logs.
We collect the minimum an account needs and nothing more. We do not sell, trade or share personal information, and you can ask for your account and its data to be erased at any time. The full terms are in our GDPR privacy agreement and our privacy policy. A data processing agreement is available on request.
These are the third parties that help us deliver the service, and what each one handles.
| Provider | Purpose | Data handled |
|---|---|---|
| AWS, Hetzner, HostHatch, Alibaba Cloud | Datacenters for hosted indexes, by region | Your index data, in the region you chose |
| Stripe | Payments and billing | Payment details, never stored by Opensolr |
| Twilio / Authy | Two-factor authentication delivery | Phone number, only if you enable it |
If you believe you have found a security issue in Opensolr, write to support@opensolr.com or use the contact form. We respond promptly, we do not pursue good-faith researchers, and we say thank you. The same addresses work for questions about this policy, for questionnaire requests and for a data processing agreement.
The detail behind this page
The Trust Center maps every control above to the SOC 2 criteria and the SIG and CAIQ questionnaires, with a downloadable PDF.
Open the Trust CenterMaster key versus scoped keys
