Skip to content
Gatekeeper
PTEN
GateKeeperGateKeeper

Add authentication and authorization to your Java or Node.js app in minutes.

Install the SDK (Maven or npm), set the Console credentials, protect backend endpoints, and manage users, groups, and permissions in the panel — without building login, JWT, RBAC, or an admin from scratch.

ConsoleDocumentationRegister interest
Java · NodeSDKProtected routesConsole

What you get

  • 1Install the Java or Node.js SDK.
  • 2Set the Console credentials.
  • 3Protect routes in the backend.
  • 4Manage access from the Console.
  • 5Login, JWT, and RBAC are already there.

Login

Ready

Integration

~5 min

SDKs

Java · Node

Console

Included

Why Java teams pick GateKeeper

Less auth code, fewer permission bugs, more time for the product.

Stop building authentication from scratch. Keep permissions in the Console, protect routes with one annotation, and use open standards — OAuth2, OpenID Connect, JWT, and RBAC — without locking the product to a proprietary stack.

Integration in minutes

Java or Node SDK — credentials copied from the Console. Start today.

Login and Google login, ready

End-user authentication without implementing OAuth2 yourself.

RBAC in the backend

@GatekeeperProtected (Java) or authorize (Node). Permissions live in the Console.

Console included

Users, groups, routes, and social login — without internal screens to build.

Less maintenance

Stop evolving auth every release. Spend the time on what the product sells.

Built for Java and Node.js

Official Spring Boot and @gatekeeperid/sdk — the same integration API.

How integration works

Maven SDK → application.yml → @GatekeeperProtected → Console. A typical integration takes about five minutes.

Typical integration time: ~5 minutes
1

Install the Maven SDK

<dependency>
  <groupId>cloud.gatekeeperid</groupId>
  <artifactId>gatekeeper-spring-boot-starter</artifactId>
  <version>0.3.5</version>
</dependency>
2

Configure application.yml

gatekeeper:
  application-name: orders-api
  tenant-id: your-tenant
  client-id: your-client
  hmac:
    secret: your-secret
3

Protect your routes

@GatekeeperProtected(permission = "orders:create")
@PostMapping("/orders")
public Map<String, Object> createOrder() {
  return Map.of("status", "CREATED");
}

The SDK syncs routes with the Console. You set groups and permissions in the panel and keep coding.

Admin console

Manage users, groups, and permissions without code

The Console is ready: create users, define groups, bind permissions to routes, and configure social login — without building an internal back office.

  • Users
  • Groups
  • Permissions
  • Routes
  • Applications
  • Social login

Users and permissions

Invite, block, and decide who can do what — without building screens.

Featured

Protected routes

Register endpoints and attach permissions in a few clicks.

Overview

Watch users, roles, routes, and permissions for your tenant.

Illustrative Console preview — sample data.

Social login, ready to use

Let users sign in with Google — without implementing OAuth2 by hand.

Google
Available
Microsoft
Coming soon
Apple
Coming soon
GitHub
Coming soon

Set up in 3 steps

  1. 1Configure in the Console — Google Cloud client ID and secret.
  2. 2Copy the redirect URI — Shown in the Console, with a copy button.
  3. 3Done. — Your users sign in with Google in your application.

Integrate without reinventing auth

Java (Spring Boot) or Node.js — the same integration API, with open standards underneath.

Maven SDK for Spring Boot

A pom.xml dependency, application.yml, and @GatekeeperProtected on the routes. A typical integration takes about five minutes.

Node.js SDK (TypeScript)

The @gatekeeperid/sdk package — GatekeeperClient, HMAC, authorize, and the integration plan. Parity with the Java SDK.

OAuth2 and OpenID Connect

JWT and standard flows. Your application uses the SDK; you do not stand up auth servers or reinvent protocols.

Social login

Google is available today; Microsoft, Apple, and GitHub are planned. Configure providers in the Console — no OAuth2 redirects in your code.

RBAC authorization

Permissions live in the Console. Declare them on the route; GateKeeper validates the JWT and authorizes.

Open standards

OAuth2, OpenID Connect, JWT, and RBAC — without locking the product to a proprietary stack, even on a managed platform.

What you stop building

Cut weeks of development. Stop maintaining auth every sprint.

Before (on your own)

You had to build and maintain:

  • Login and sign-up screens
  • Password recovery
  • JWT validation
  • RBAC scattered in code
  • Admin panel
  • Social login (Google, and more)
  • Identity infrastructure

With GateKeeper

Four steps to integrate:

  • Java (Maven) or Node (npm) SDK
  • Console credentials
  • Routes protected by the SDK
  • Users and permissions in the Console

Build it yourself vs GateKeeper

Cut weeks of development and drop the ongoing auth maintenance.

What changes in practice

On your own
With GateKeeper
Weeks building login
Login ready
Implement OAuth by hand
Google login in the Console
RBAC scattered in code
Centralized permissions
Build a user admin
Admin console included
Run auth infrastructure
Managed platform
Become an identity specialist
Integrate and focus on the product

Quick example

YAML, an annotation, and a ready API — secrets stay off the browser.

@GatekeeperProtected(permission = "orders:create", description = "Criar pedido")
@PostMapping("/orders")
public Map<String, Object> createOrder() {
  return Map.of("id", 2, "status", "CREATED");
}

@GatekeeperProtected(permission = "admin:reports", description = "Relatórios admin")
@GetMapping("/admin/reports")
public Map<String, String> adminReports() {
  return Map.of("report", "summary");
}

Login, sign-up, refresh, and profile go through the SDK on the backend — endpoints under /sdk/integration/v1/*.

# application.yml (seu backend)
gatekeeper:
  application-name: orders-api
  tenant-id: $${GATEKEEPER_TENANT_ID}
  client-id: $${GATEKEEPER_CLIENT_ID}
  hmac:
    secret: $${GATEKEEPER_HMAC_SECRET}

# A SDK sincroniza rotas protegidas no startup
# e consulta authorize durante as requests

Start integrating today

No hidden SDK fees. Focus on shipping value — we run the identity layer.

Recommended to start

Integration

For developers and teams who want to validate quickly.

  • Java and Node.js SDKs + documentation
  • Admin console included
  • Social login with Google
I want to try GateKeeper

Production and scale

For multi-tenant SaaS and multiple environments.

  • Tenants isolated per customer
  • Centralized, auditable RBAC
  • OAuth2, OpenID Connect, and JWT
Read the docs

Frequently asked questions

Java or Node SDK → protected routes → Console → groups and permissions → a protected application.

What is GateKeeper?
GateKeeper adds authentication and authorization to your Java or Node.js application in minutes. You install the SDK (Maven or npm), set the Console credentials, protect backend endpoints, and manage users, groups, and permissions in the panel — without building login, JWT, RBAC, or an admin from scratch.
Why use GateKeeper instead of building authentication yourself?
Authentication looks simple until you need password recovery, social login, RBAC, JWT validation, user management, and an admin console. GateKeeper ships all of that: cut weeks of development, protect routes with the SDK, and keep permissions in the panel instead of scattered through the code.
How do I integrate with Spring Boot?
Add the Maven dependency to pom.xml, set tenant-id, client-id, and the secret in application.yml, and annotate controllers with @GatekeeperProtected. The SDK validates the token and the permission. A typical integration takes about five minutes.
How do I integrate with Node.js?
Install @gatekeeperid/sdk, configure GatekeeperClient with baseUrl, tenantId, and HMAC, and call authorize in your route middleware. Send the integration plan on boot. Same public API as the Java SDK — 0.3.5 parity.
What do I need in application.yml?
At minimum: application-name, tenant-id, client-id, and the HMAC secret from your integration plan (copied from the Console). With that, the SDK connects to the API, syncs routes, and starts protecting endpoints. On Node, the same values go on GatekeeperClient. You do not configure OAuth URLs by hand for the basic flow.
How does @GatekeeperProtected work?
You declare the required permission on the annotation — for example @GatekeeperProtected(permission = "orders:create"). On each request the SDK validates the JWT and asks GateKeeper to allow or deny access. On Node.js the equivalent is client.authorize(token, { method, path }).
Does GateKeeper manage users and permissions?
Yes. In the Console you create users, groups, and permissions, attach groups to permissions, and bind routes — with no extra code in your application. Login, sign-up, and session refresh stay on the platform; your API only uses the SDK.
Can I use social login?
Yes. Google is available now; other providers are on the roadmap. Set the client ID and secret in the Console, copy the redirect URI, and your users sign in with one click — without implementing OAuth2 in your repository.
Does GateKeeper replace Keycloak?
For most product teams, yes in practice: you do not install, operate, or customize a Keycloak cluster. GateKeeper uses open standards underneath and ships an SDK, an API, and a Console. If you need full control of Keycloak infrastructure, self-hosted still makes sense. If you want to ship auth quickly, GateKeeper is the shorter path.
Does GateKeeper use open standards?
Yes. OAuth2, OpenID Connect, JWT, and RBAC — standards your team already knows, which do not lock the application to a proprietary vendor. You integrate through the SDK or the public REST API and keep conceptual portability on a managed platform.
Can I use it in a multi-tenant SaaS?
Yes. Each customer or environment becomes an isolated tenant: separate users, groups, permissions, and login settings. Add new customers from the Console instead of copying auth code or infrastructure for every contract.

Documentation

SDK guides, the API reference, and examples to integrate in minutes.

Quickstart

Java or Node — credentials, /auth on the BFF, and the first protected route.

Open documentation

API overview

Login, sign-up, social login, password, and integration plan endpoints.

Open documentation

Java SDK (Spring Boot)

Maven install, application.yml, and @GatekeeperProtected.

Open documentation

Node.js SDK (TypeScript)

@gatekeeperid/sdk — login, HMAC, authorize, and the integration plan.

Open documentation

OpenAPI

Interactive specification of the public integration API.

Open documentation
See the full documentationQuick integration guideSee blog postsFAQ

GatekeeperID Research

Identity, authorization, and the security of autonomous agents.

See the research

GatekeeperID Agents

The agent on the company database, inside the person’s limit.

Gatekeeper ID handles application login and permissions. Agents handles the agent that talks to PostgreSQL: a personal token, approval, and an audit trail. The database password does not go to the laptop.

See Agents

Integrate today. Focus on your product.

Java or Node.js SDK, Console, and API — login, JWT, RBAC, groups, and permissions are already there.

ConsoleDocumentationRegister interest