Skip to content

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 ​

CapabilityDetails
ProxyDynamic route matching and forwarding to target microservices, with streamed request and response bodies, multipart and binary payloads
RealtimeServer-Sent Events and authenticated WebSocket upgrades. GraphQL passes through as ordinary HTTP
AuthenticationJWT access and refresh tokens, consumer session management, and mid-login challenges (2FA, expired password) delegated to a password service
AuthorizationRole-based access control (RBAC/ACL) per route, per property and per condition
Route managementApplications, services, resources, routes, methods and operations
Role and permission managementDefine roles, then grant operations per route, with optional field, scope and condition restrictions
CORS managementControl allowed origins without a restart
Admin UIAngular front end to manage sessions, routes, roles and ACL

Key concepts ​

ConceptMeaning
RouteMaps an incoming URL pattern to a target service and resource, with the HTTP operations it allows
ConsumerAn authenticated user session, identified by an access and refresh token pair and carrying the user's role IDs
RoleA named group of permissions, scoped to an application
PermissionThe 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 ​

ImageRegistry
BFF, including the Admin UI under /adminghcr.io/alten-group/gatelin
Migrationghcr.io/alten-group/gatelin-migration

Published and maintained by ALTEN