~/4xplee.com $ gateway --status
Put a gateway in front of everything — and never touch a control plane again.
4xplee sits between your clients and your services, handling routing, rate limits, auth and tracing as plain config you keep in git. No dashboard clicks, no sidecar mesh, no 3 a.m. paging because a YAML drifted.
# pull the binary and point it at your routes file
$ curl -fsSL https://4xplee.com/install.sh | sh
$ 4xplee up --config gateway.toml
✓ listening on :8080 — 12 routes, 3 upstreams (edge: fra1)
$ 4xplee reload --graceful
→ config swapped · 0 dropped conns · 6msA gateway that behaves like the rest of your stack
01Config you can diff
Routes, limits and policies live in one declarative file. Open a pull request, review the change, ship it on merge — the gateway picks it up on reload.
02Auth at the edge
Drop in JWT, API-key or mTLS checks per route. Tokens are verified before a request ever reaches your service, so upstreams stay simple.
03Traces, not guesswork
Every hop emits OpenTelemetry spans with upstream timing baked in. Wire it to your collector and watch latency by route in real time.
04Limits that actually hold
Token-bucket throttling shared across nodes via a tiny gossip layer. Burst rules, per-key quotas and instant 429s with zero shared database.
Drive the gateway from your pipeline
| Method | Endpoint | Description |
|---|---|---|
| PUT | /v2/routes | Push a new route table to the cluster |
| GET | /v2/upstreams/:id/health | Read live health of one upstream pool |
| POST | /v2/limits | Set or adjust a rate-limit policy |
| GET | /v2/metrics | Stream per-route latency & error rates |
| POST | /v2/reload | Trigger a zero-downtime config swap |
Priced by throughput, not by node count
solo
$0 /mo
- up to 1M requests / month
- single edge node
- community Discord
growth
$59 /mo
- up to 50M requests / month
- multi-region edge
- OTel export & alerts
- support replies under a day
enterprise
Let's chat
- committed throughput & SLA
- dedicated edge cluster
- SAML SSO & audit trail