AuthGate
One sign-in for every workspace on the platform
A unified front door for your product. Users sign in once with Google or a social provider, and every other microservice recognises them instantly — no duplicate accounts, no re-login friction, no scattered user tables.
- 1 click From zero to authenticated
- 0 Passwords stored on the platform
- All Microservices share the same session
AuthGate is the gatekeeper that every other microservice leans on. The very first thing a new visitor sees is a single large sign-in button — and from that moment onward their session carries them across every part of the platform without ever asking for a password again.
Behind that button sits a full identity pipeline. A provider flow (Google and the most common social logins out of the box) hands AuthGate a verified identity; AuthGate creates a personal user record automatically, pulling the name, email, and avatar straight from the provider. When the same person returns later, their record is refreshed in place — there are no forms to re-fill, no avatars to re-upload, no blank fields to rediscover.
Email is treated as the canonical identity, so one human cannot end up with three different accounts through three different sign-in methods. AuthGate watches presence too — it knows who is online right now and who has been away for a while, and surfaces that in a lightweight administrative panel.
The admin surface is deliberately minimal. It lists every user, shows their avatar and last visit, and offers one-click actions with clear confirmations for anything destructive. The interface is dark-themed, responsive from phone to widescreen, and fully multilingual — AIM ships every screen in every language we support, with RTL and LTR layouts handled natively.
Sign-out is equally clean: the session is invalidated, cookies are dropped, and the user lands back on the welcome screen. Because passwords never touch the platform, there is no password database to leak — the security boundary is pushed out to the upstream provider, where credential hygiene is a full-time job.
Every other microservice on the platform — billing, the chat builder, the agent builder, the calendar, the CRM — treats AuthGate as the single source of identity. Users authenticate once and move across the whole product line without seeing a second login screen. This is what makes the platform feel like one product instead of a bundle of tools.
AuthGate is intentionally autonomous. It has no runtime dependencies on other microservices, so an outage elsewhere never prevents people from logging in. It is built to scale horizontally with user growth, carries a full audit log of sign-ins and administrative actions, and assumes from day one that security reviews will look closely at every entry point.
Everything AuthGate handles for you
-
Single sign-on
Google and the most common social providers, wired up out of the box. No password fields anywhere in the product.
-
Auto-provisioning
A user record is created on first sign-in and refreshed on every return, straight from the identity provider.
-
Duplicate protection
Email is the canonical key — one person, one record, regardless of which provider they use next time.
-
Presence signal
A live online / offline indicator for every user, surfaced to admins in the user list.
-
Admin console
A compact panel to search, inspect, and remove user accounts — with a confirm step on every destructive action.
-
Clean session model
Sign-out invalidates the session end-to-end. No ghost tokens, no half-authenticated states.
-
Multilingual UI
Every language AIM supports, from one codebase, with RTL and LTR layouts handled natively.
How AuthGate plugs into the rest of the platform
AuthGate is the single source of identity for every other microservice. Once a user signs in, the account manager, billing, chat builder, agent builder, CRM, calendar, forms, and all future services recognise them automatically — no re-authentication, no duplicate profiles, no custom glue code.
- AccountManager reads the signed-in identity to load the right workspace, projects, and business profile.
- Billing attaches subscriptions, invoices, and payment methods to the AuthGate user id.
- ChatBuilder scopes chats and drafts to the user and their workspace, with no separate login.
- AgentBuilder persists agent recipes under the same identity used everywhere else.
- AIM CRM uses AuthGate to distinguish operators from visitors and lock permissions accordingly.
- UserProfile hydrates its extended profile card from the base record that AuthGate created.
Wire AuthGate into your product today
Book a consultation with our founders and we'll walk you through the whole microservice stack — not just this one — live on your domain.