Transparent mode
Observe and measure application traffic while result-cache lookups and storage are disabled. Use it to understand a workload before enabling cache reuse.
CacheDB product overview
A native database proxy with a controlled cache fast path.
CacheDB sits between applications and databases. It speaks each database’s own wire protocol, observes traffic in transparent mode, and can reuse eligible reads under an explicit cache policy.
Five native proxies
Keep your database driver and SQL.
Each CacheDB proxy speaks the database’s native protocol to both the application and backend. Applications keep their existing driver and SQL while changing the address they connect to.
- PostgreSQL
- MySQL
- SQL Server
- IBM Db2
- Oracle
Product capabilities
Put operators in control of the fast path.
CacheDB combines protocol-aware traffic handling with explicit policy, visible outcomes and tools for operating multiple proxy targets.
Distributed query cache
Serve eligible reads from Redis Community, Valkey or Redis Enterprise under reviewed TTL and bypass rules. Cache misses go to the source database.
Scripts and invalidation
Use scripts and hooks to prepare SQL, decide cache eligibility, and invalidate related results after writes.
Multi-tenant console
Manage multiple proxy fleets from one console with tenant-scoped views, metrics and operational controls.
Encrypted database paths
Terminate TLS from the client and open a separate backend TLS connection, verifying backend certificates by default.
Operational visibility
Investigate queries in the console, track alerts, and export fleet and cache metrics to Prometheus for Grafana dashboards.
Policy assistance
Use the optional AI assistant to analyze proxy context and propose cache-rule changes for validation and operator review.
Proxy high availability
Distribute connections across multiple shared-nothing proxy instances with health-aware load balancing.
Offline licensing
Verify licenses locally for deployments that operate in restricted or isolated environments.
Designed for real environments
Understand the boundaries with the capabilities.
Native proxies support TLS 1.2 or later on both database legs. Cache connections do not support transport TLS and should stay on a trusted network or use network-level encryption. The web console is designed to sit behind a TLS-terminating reverse proxy or WAF.
Cache reuse is policy-controlled and can be eventually consistent. Validate the client driver, database version, session behavior, workload and freshness requirements before enabling it.
Review security and deployment requirementsSee how CacheDB worksProduct guides
Explore the details that shape an evaluation.
These guides explain the product and its operating model. Contact us if you need deployment-specific details or a deeper technical review.
Getting startedRequest flow, transparent operation, and evaluation approach.Compatibility & securityDatabase paths, TLS, network boundaries, and consistency.Deploy CacheDBTopology, configuration, distributed cache, and staged rollout.Console operationsQuery views, fleet monitoring, alerts, OIDC and Grafana integration.Cache policyFrom observed queries to reviewed rules, freshness, and invalidation.AI AssistantAnalyze workload context and review policy candidates.
More information
Discuss the details of your deployment.
Tell us about your database, workload, cache environment and operational requirements. We can provide the relevant technical detail for an evaluation.