Open J Proxy
Open J Proxy
Open J Proxy 1.0.0 GA LTS is production-ready and designed for fast adoption: swap your JDBC driver, update your URL, and gain centralized connection control without changing application code.
Open J Proxy 1.0.0 is production-ready and available now. Start with the docs, run it locally, and join the list to receive the free adoption ebook and rollout guidance.
A practical path to safer scaling with minimal change to existing Java applications
Adopt a single control point for connection pooling and traffic management without rebuilding your services. OJP adds a resilience layer that helps isolate failures and prevent cascading outages.
OJP 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 GuideBuilt for real-world adoption: free, open source, and ready for production with OJP 1.0.0
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 so teams with advanced consistency needs can still adopt OJP.
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:1.0.0
Include the OJP JDBC driver in your project
<dependency>
<groupId>org.openjproxy</groupId>
<artifactId>ojp-jdbc-driver</artifactId>
<version>1.0.0</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
Use this simple adoption path for your first rollout:
We are publishing 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 our updates list to receive the full report, release follow-ups, and future product announcements.
Get Benchmark UpdatesAnswer 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