Aadhib

Enterprise Platform · Active

Enterprise application hub

An internal application hub for an industrial organisation — one authenticated entry point to the systems employees actually use.

Role
Architecture and delivery
Category
Enterprise Platform
Status
Active
01

The problem

Internal tooling accumulates. Each system arrives with its own URL, its own login and its own idea of who the user is. Employees end up with a folder of bookmarks and several passwords, and IT ends up supporting the seams between systems rather than the systems themselves.

02

Approach

Give the internal estate one front door. A hub that authenticates once, presents the applications a given employee actually has access to, and uses a consistent directory and subdomain structure underneath so new tools join the pattern instead of inventing their own.

03

What it does

01
One authenticated entry point
Employees sign in once and see the applications relevant to them, rather than navigating a list of unrelated systems.
02
Consistent directory and subdomain architecture
A predictable structure for where internal applications live, so adding one is a routine act rather than an architectural decision each time.
03
Integration with existing internal tools
The hub sits in front of systems that already exist, rather than requiring them to be rebuilt to participate.
04

The hard parts

01
You inherit every prior decision
An internal hub has no greenfield. It has to accommodate systems built at different times by different people with incompatible assumptions about identity.
02
A front door is a single point of failure
Consolidating access means an outage stops everything at once. That changes the reliability requirements of what is, on the surface, a simple launcher.

Detail

Client confidentiality

I'm not naming the organisation. I describe it here as an industrial manufacturing organisation in Saudi Arabia, which is accurate and sufficient to understand the engineering.

Why a hub rather than a portal

A portal implies content. What I built is a router: it establishes who you are, decides what you can reach, and gets out of the way. My measure of success is that nobody thinks about it.

Stack

Access
AuthenticationEmployee directory
Architecture
Subdomain routingInternal integrations

Case study

The decisions behind the build

All work