Meerkat - Is it an API gateway? An IAM? No, it's an app gateway!
by•
Meerkat puts one door in front of your internal apps: sign-in pages, SSO, passkeys and 2FA, roles, tenants, routing, rate limits and audit. Your services get requests already authenticated, with a signed JWT. One image, 70 MB, no dependencies.

Replies
Hi Product Hunt 👋 I'm François, the maker of Meerkat.
Every internal app I've worked on ended up with the same stack around its API gateway: an IAM, an auth proxy, config files everywhere, a tunnel for developers, a telemetry pipeline, and admin screens we wrote ourselves. Around eight products to deploy, secure and keep in step, before a single line of the actual business.
So: is it an API gateway? An IAM? No, it's an app gateway 🦸
Meerkat sits in front of your applications and handles:
→ Who's calling: sign-in pages, SSO with your existing identity provider, passkeys, TOTP
→ Who may pass: roles, groups, tenants, per-route rules
→ How requests travel: routing, rewriting, rate limits, TLS
→ What's happening: traffic, audit trail, metrics, traces
Your services receive requests that are already authenticated, with a signed JWT (or plain headers) carrying the user, the roles and the tenant. No login page, no user table, no role model in each service.
It's pure Go, one image (70 MB), no database to run beside it.
The Community edition is free, production included. Each release becomes Apache 2.0 two years later. To try everything, Enterprise included, the evaluation image has no time limit:
docker run -p 8080:8080 -p 9090:9090 -e MEERKAT_ADMIN_PASSWORD=choose-one softwarity/meerkat
I'd love your honest feedback: have you built this kind of stack around an API gateway? Would an all-in-one app gateway tempt you, or do you prefer separate building blocks?