Skip to content
Raahi
A request passing through a route and its policies to two healthy upstream targets.

A fast reverse proxy and API gateway.

Route HTTP, HTTPS, WebSocket, and TCP traffic. Add TLS, load balancing, authentication, rate limits, caching, and traffic controls from a web UI or API.
Get startedSee what it can doAPI reference
Self-hosted and ready for live traffic

Raahi sits in front of your applications and sends each request to the right upstream. It handles certificates, health checks, policy, and traffic distribution in one service.

Route and policy changes take effect without restarting the proxy.

What Raahi handles

Section titled “What Raahi handles”

HTTP, WebSocket, and TCP routing

Route by hostname, path, method, or header. Proxy WebSockets over HTTP and raw TCP services through dedicated listeners.

TLS without certificate chores

Serve the right certificate for each hostname. Issue and renew certificates through Let’s Encrypt, ZeroSSL, or another ACME provider.

Traffic policy at the proxy

Add API keys, Basic auth, JWT verification, ACLs, IP rules, rate limits, CORS, redirects, caching, compression, and request transforms.

Load balancing and safe rollouts

Remove unhealthy targets, balance requests across backends, and shift a percentage of traffic to a canary service.

Why run Raahi

Section titled “Why run Raahi”
  • Changes do not interrupt traffic. Route, target, plugin, and certificate updates apply while the proxy keeps serving requests.
  • The common controls are built in. TLS, authentication, rate limiting, caching, health checks, and metrics do not require a separate plugin marketplace.
  • You can operate it without editing config files. Use the web UI for daily work and the REST API for automation, backups, and GitOps.
  • One service handles L7 and L4 traffic. Use host and path routing for web applications, plus raw TCP listeners for databases and other protocols.
  • The state is easy to back up. Raahi stores its configuration in one SQLite database and supports explicit export and restore endpoints.

How requests move

Section titled “How requests move”

A service describes an upstream application. Targets are the servers behind it. A route decides which requests reach the service. Plugins add authentication, limits, caching, transforms, and other policy.

request -> route -> policy -> load balancer -> healthy target

Start with a task

Section titled “Start with a task”
Run it locallyStart Raahi, add two upstreams, and send a request through the proxy.
Publish an applicationCreate an upstream, domain route, HTTPS redirect, and access rules together.
Understand route matchingSee how hostnames, paths, methods, headers, and priorities select a route.
Configure productionSet listener addresses, worker threads, logging, backups, and restart boundaries.