Proxies for your stack
PostgreSQL, MySQL, SQL Server, IBM Db2 and Oracle.
CacheDB by houdata.
CacheDB sits between your application and database, accelerating repeated reads while keeping invalidation controlled and visible.
A short product walkthrough hosted on YouTube.
Works with critical data systems
Measurable improvement
CacheDB is designed for teams that need a credible performance path without a rewrite of the systems they already trust.
PostgreSQL, MySQL, SQL Server, IBM Db2 and Oracle.
Separate client and backend TLS sessions with backend verification.
Scope operational views and controls to the selected proxy target.
Inspect query patterns, rates, cache outcomes, latency and invalidations.
Architecture
Each CacheDB proxy speaks its database protocol on both sides. Run in transparent mode to observe traffic without result reuse, or enable cache behavior under an explicit policy.
Proxy instances share no local state. Balance connections across healthy instances and use Redis Community, Valkey or Redis Enterprise for their distributed cache.
Explore product capabilitiesTraffic-aware cache policy
CacheDB combines programmable scripts and hooks with an AI assistant that studies the operational context visible at the proxy.
Analyze cache metrics, query patterns, invalidation relationships and runtime signals to find inefficient behavior.
Suggest a focused script or trigger for cache eligibility, freshness, or selective invalidation, based on the workload.
Validate candidates with the production engine without deploying them. Operators remain responsible for review and activation.
Multi-tenant console
CacheDB makes performance policy an operational system: observable, attributable, integrated with identity, and designed for resilient deployments.
Review fleet metrics, alerts, configuration and license status in the selected tenant context.
Record protected actions and policy deployments in an append-only audit history with export support.
Balance database connections across multiple shared-nothing proxy instances, with health checks to avoid unavailable instances.
Use standards-based OIDC and role mappings for console access.
Evidence for operators
CacheDB exposes the operational context needed to review cache outcomes and tune explicit policy with confidence.





A controlled evaluation
Start with the workload you already operate. Validate the result with evidence before broadening the deployment.
Identify repeated reads, load patterns and current constraints.
Model cache policy, TTLs and invalidation boundaries.
Introduce CacheDB into a controlled path without rewriting application logic.
Compare latency, hit ratio and database load against the baseline.
Technical overview
Technical conversation
Tell us about the database, workload and performance constraint you are working with. We will start with a focused, evidence-led discussion.