Open J Proxy
Open J Proxy is an open-source database control plane for Java applications. It centralizes connection management, applies backpressure, isolates slow queries, and helps keep relational databases stable under pressure.
OJP is currently in beta. Use it for evaluation, testing, benchmarks, architecture reviews and early feedback before the 1.0.0 LTS release.
A proxy layer between your applications and database unlocks significant operational advantages
A database proxy centralises connection pooling and traffic management, giving you a single governance point for all database access. It also acts as a resilience layer — isolating application instances from database failures and preventing cascading outages, so your application stays stable under pressure.
OJP does not make your database infinite. It helps enforce safe limits, apply backpressure, and prevent application-side scaling from overwhelming a finite database connection budget.
OJP supports every database that provides a standard JDBC driver — PostgreSQL, MySQL, Oracle, SQL Server, MariaDB, DB2, H2, CockroachDB, and beyond. If a JDBC driver exists for your database, OJP works with it.
A hands-on community guide with runnable Spring Boot examples, from first connection to observability and production hardening.
Open the GuideOJP goes further than traditional database proxies — delivering unique capabilities no other open source solution provides
Scale your applications freely without overwhelming your database. OJP's intelligent connection pooling prevents connection storms.
Circuit breakers, backpressure, and slow query segregation ensure your database stays healthy under any load.
Simply swap your JDBC driver and update your connection URL. No application code changes required.
Built on HikariCP with centralized server-side connection pooling. One control point for connection governance across all your application instances.
Works with every database that offers a JDBC driver — PostgreSQL, MySQL, Oracle, SQL Server, MariaDB, DB2, H2, CockroachDB, and more. One proxy for your entire database estate.
Integrated monitoring and query tracking. Know what's happening in your database layer.
Full support for distributed transactions. Build reliable, scalable enterprise systems.
Works across any cloud provider. Not locked into vendor-specific solutions. True freedom.
OJP delivers the first open source Type 3 JDBC driver with native client-side load balancing and automatic failover. Traditional database proxies require an additional external load balancer; OJP handles it natively — reducing infrastructure complexity and cost.
gRPC + Protocol Buffers API means services in any language can use OJP's benefits.
Built for freedom — no vendor lock-in, no proprietary dependencies
Three simple steps to protect your database
Deploy the OJP server using Docker or standalone JAR
docker run --rm -d --network host \
rrobetti/ojp:0.5.2-beta
Include the OJP JDBC driver in your project
<dependency>
<groupId>org.openjproxy</groupId>
<artifactId>ojp-jdbc-driver</artifactId>
<version>0.5.2-beta</version>
</dependency>
Prefix your existing JDBC URL with OJP
jdbc:ojp[localhost:1059]_
postgresql://user@host/db
OJP Helm Charts are available for deploying the OJP Server in Kubernetes
Add the OJP Helm repository and deploy the OJP Server to your cluster with a single command.
helm repo add ojp https://Open-J-Proxy.github.io/ojp-helm
OJP is currently in beta. The best way to help before 1.0.0 is to:
We are preparing public benchmark results comparing OJP with traditional application-local connection pooling and database proxy approaches under mixed OLTP/OLAP load, connection pressure and overload scenarios.
Join the early adopters list to receive the full report when published.
Notify Me When Results Are PublishedAnswer 9 quick questions and get an instant recommendation based on your database architecture challenges.
Take the Free AssessmentJoin the teams building cloud-independent, database-agnostic Java systems with Open J Proxy