Appearance
Gatelin
Gatelin is a Backend for Frontend (BFF): your application's API layer. It sits behind an edge reverse proxy (Traefik, nginx, Envoy), which stays the public gateway for TLS, host routing and load balancing. Gatelin handles what is specific to your application: who the caller is, what they are allowed to do, and where their request goes.
Full documentation
gatelin.fr has the integration guide, the API reference, configuration and deployment.
What it is used for
Use Gatelin when your front end talks to several microservices and you want a single place to:
- Sign users in and keep their sessions
- Decide, per route and per operation, what each role may do
- Forward authorized requests to the right service without each service reimplementing authentication
Gatelin is not a cluster ingress, a service mesh or a multi-tenant traffic gateway.
What it does
| Capability | Details |
|---|---|
| Proxy | Dynamic route matching and forwarding to target microservices, with streamed request and response bodies, multipart and binary payloads |
| Realtime | Server-Sent Events and authenticated WebSocket upgrades. GraphQL passes through as ordinary HTTP |
| Authentication | JWT access and refresh tokens, consumer session management, and mid-login challenges (2FA, expired password) delegated to a password service |
| Authorization | Role-based access control (RBAC/ACL) per route, per property and per condition |
| Route management | Applications, services, resources, routes, methods and operations |
| Role and permission management | Define roles, then grant operations per route, with optional field, scope and condition restrictions |
| CORS management | Control allowed origins without a restart |
| Admin UI | Angular front end to manage sessions, routes, roles and ACL |
Key concepts
| Concept | Meaning |
|---|---|
| Route | Maps an incoming URL pattern to a target service and resource, with the HTTP operations it allows |
| Consumer | An authenticated user session, identified by an access and refresh token pair and carrying the user's role IDs |
| Role | A named group of permissions, scoped to an application |
| Permission | The grant that links a role to a route and an operation, optionally restricted by fields, scopes and conditions |
When a request arrives and no permission covers its route and method, Gatelin rejects it with a 403.
Where it fits
Gatelin is the entry point of the stack. It resolves users through Megadex and verifies passwords through Foxnox, then issues the JWT session. See the reference architecture.
Run it
| Image | Registry |
|---|---|
BFF, including the Admin UI under /admin | ghcr.io/alten-group/gatelin |
| Migration | ghcr.io/alten-group/gatelin-migration |