Get started

How the Enjab backbones fit together and the fastest path to a working tool - login, on-brand UI, and the engineering standards every tool must meet.

An Enjab tool is a web app built on three Enjab backbones:

Sign in with Enjab Auth handles who the user is and whether they may use your tool. You never build a login screen or touch a password.
Enjab UI gives you the look - a themed component registry and a dashboard shell, so every Enjab tool feels like one product.
Engineering Standards are the rules - infrastructure and process guidelines (security, deployment, pipeline) so every tool ships production-ready and consistent.

You build the part in the middle: your tool's actual features. Everything else is provided.

The shape of an Enjab tool

It lives on an enjab.ae domain (e.g. yourtool.enjab.ae). Auth refuses any other domain.
The instant a signed-out visitor touches any page, they are redirected to Enjab to sign in. No login button, no login page of your own.
Once signed in, you key all your own data by the user's stable Enjab id (sub).
Your dashboard uses the Enjab UI shell, so the sidebar, account block, and the "an Enjab product" byline are consistent with every other tool.
It meets the Engineering Standards before it ships: the security, deployment, and pipeline rules every Enjab tool must follow.

Fastest path

Register the tool (one time)

An Enjab admin adds your tool in auth.enjab.ae/admin and hands you a ENJAB_CLIENT_ID + ENJAB_CLIENT_SECRET. See Sign in with Enjab Auth → register for the exact steps.

Drop in the four reference files (lib/enjab-auth.ts, the callback route, the logout route, and proxy.ts). Set your four environment variables. That is the whole integration - copy them from Sign in with Enjab Auth.

Add the UI

Install the Enjab UI chrome and theme, then build your screens with the registry components so your tool matches the rest of Enjab. See Enjab UI.

Meet the Engineering Standards

Before it goes to production, bring your tool in line with the Engineering Standards: the security, deployment, and pipeline rules every Enjab tool must follow. These are not optional. A tool is not "done" until it meets them.

The standards are mandatory

Login and UI make a tool work and look right. The Engineering Standards make it safe to run in production, and they are strict: they apply to every Enjab tool, no exceptions, and are a hard gate before shipping. Read them early, not after you are "done".

Handing this to an agent

Give your coding agent this site's /llms.txt (or the specific page's raw markdown) and the task. The pages are written so the agent can do each step end to end, including meeting the Engineering Standards before it ships.