Test · Monitor · Log

Put a simple load balancer in front of any API

Create one in seconds and get a unique endpoint. Hit it from your app, a script, or curl — we route the request to your targets and give you the tools to test, monitor, and log every call.

Create a load balancer Login
  • ✓ Unique endpoint per load balancer
  • ✓ Works with any HTTP method
  • ✓ No changes to your API
Hit your endpoint 
$ curl https://simpleloadbalancer.com/lb/3f2a9c1e-…/users
< 200 OK · 84 ms · via api.example.com/v1
Recent Requests Active
Source IP Method Status Time Target
203.0.113.24 GET 200 84 ms api.example.com/v1
198.51.100.7 POST 201 132 ms api.example.com/v2
203.0.113.24 GET 304 41 ms api.example.com/v1
192.0.2.61 DELETE 500 310 ms api.example.com/v1

Hit one endpoint. See everything.

Every load balancer you create is a URL you can send real traffic to — and a place to understand what that traffic is doing.

Test

Send requests from the built-in Test Console. They run through the same target selection and transformations as live traffic, and you can save the ones you reuse.

Monitor

Watch status codes and response times as requests arrive, and see which target answered each one. Spot a failing or slow upstream at a glance.

Log

Each request through your endpoint is recorded with its source IP, method, target, status, and latency — so you know who is calling and what they hit.

What happens to a request

Your callers only ever see one URL. You decide what sits behind it.

1 · Caller

Your app, script, or teammate

Sends any HTTP request to your endpoint.

2 · Your load balancer

/lb/<your-uuid>

  • Checks the rate limit
  • Applies your transformations
  • Picks a target by weight
  • Logs the result

3 · Target A · weight 2

api.example.com/v1

3 · Target B · weight 1

api.example.com/v2

Simple, with the controls you need

Weighted targets

Spread traffic across several upstreams with weighted round-robin.

Keep API keys private

Attach a key as a header on the way out. Callers use your endpoint and never see it.

Request & response transforms

Add, remove, or rewrite headers, wrap or find-and-replace bodies, and append query params.

Per-endpoint rate limits

Cap requests per minute on each load balancer so a runaway client can’t flood your API.

Approved domains only

Targets must be on an admin-approved domain, and requests to internal networks are blocked.

Off in one click

Deactivate a load balancer to stop its endpoint from forwarding traffic. Turn it back on anytime.

Up and running in three steps

  1. 1

    Create a load balancer

    Name it and you get a unique endpoint URL straight away.

  2. 2

    Add targets and transforms

    Point it at your API, then try it in the Test Console before anyone else uses it.

  3. 3

    Send traffic and watch it

    Share the URL with your app or team and follow each request in the log.

Create your first load balancer