# Support Tank: The Battle-Ready Rust Data Layer
Hey there! 👋
If you're here, you probably know that working with databases in Rust can sometimes feel like a tough mission. You either get raw SQL strings that break at runtime, or heavy ORMs that hide too much magic and fight the borrow checker.
I built Tank because I wanted a third option. I wanted a tool that respects your intelligence as a developer but handles the heavy lifting. I wanted something that felt like **standard equipment**: reliable, modular, and ready for any terrain, whether that's a simple local SQLite file or a complex distributed ScyllaDB cluster. The list of supported database is long and keeps growing.
### Why Sponsor?
Tank is a "clean-slate" project. That means no legacy baggage, but it also means a lot of ground to cover. I'm writing and maintaining drivers for everything from Postgres to DuckDB to Valkey, ensuring they all speak the same language without losing their unique strengths.
Maintaining a project like this takes serious hours. It involves:
- **Constant Refactoring:** Rust is evolving, and Tank evolves with it to stay ergonomic and performant.
- **Driver Maintenance:** Databases change, protocols update, and edge cases appear. Keeping `tank-postgres`, `tank-mysql`, `tank-mongo`, and others in sync is a significant logistical challenge.
- **Documentation:** Good tools need good manuals. I want Tank's docs to be the best in class, clear, helpful, and maybe a little fun.
### Where Your Money Goes
Every dollar you contribute buys me time. Time to fix that obscure bug, time to add that requested driver, and time to rethink an API until it feels *just right*.
It keeps the project alive, independent, and focused on code quality rather than corporate interests.
If Tank has saved you time, reduced your boilerplate, or just made your Rust code cleaner, please consider chipping in. It helps more than you know.
*Stand firm. Code strong.*
-- The TankHQ Team