Support
rqlite has been maintained by the same developer since 2014. Community help is free.
Community
Community support
Best effort, but questions and bug reports get answered.
Bug reports
Open an issue on GitHub for bugs and feature requests. Include the rqlite version, how you run it, and the steps to reproduce.
Security vulnerabilities
Commercial
Working with the maintainer
Some organizations need a named engineer under contract before they can run software in production. That is available.
- Architecture and deployment review
- Production hardening covering security, backups, monitoring, and Kubernetes
- Performance tuning and capacity planning
- Bug fixes and feature development on a defined timeline
- Training for engineering and operations teams
Contact
Fixed-scope projects or an ongoing retainer. Email a short description of how you use rqlite and what you need.
hello@philipotoole.comThe maintainer
Philip O’Toole
Philip created rqlite and has led its development ever since, through more than a decade of continuous releases. He has spent over fifteen years building distributed systems, databases, and large-scale data infrastructure. He has presented rqlite and distributed systems in Go at GopherCon, spoken at AWS re:Invent on large-scale log aggregation and analytics, and presented rqlite to the Carnegie Mellon Database Group.
Read more at philipotoole.com, or find him on GitHub.
rqlite at a glance
- Maintained since
- 2014, with regular releases
- License
- MIT
- Adoption
- Over 1.2 million Docker Hub pulls
- Hardened images
- FIPS-validated images built and maintained by Chainguard
- Security
- Advisories published on GitHub
- Continuity
- MIT-licensed. All code, history, releases, and discussion are public on GitHub.