Skip to content
Ahmed Nour Eldin
All work

Multi-tenant enterprise SaaS

Solutions by STC, for the NEOM project, Dec 2023 – Present

One component system and one authentication layer serving many tenants, user roles and white-label configurations.

Tenant
Signed in as

ALPHA OPS

Admin

Tenant A, admin: 4 of 4 actions available.

  • View recordsAllowed
  • Edit recordsAllowed
  • Manage usersAllowed
  • White-label settingsAllowed
Working illustration. Fictional tenants and data, not the product.

Context

A multi-tenant enterprise SaaS platform for the NEOM project, built at Solutions by STC with React.js, Next.js, Material UI and NextAuth.js. I work on it as a Senior Frontend Developer.

Problem

Each tenant brings its own user roles and white-label configuration. Features need to reach all of them without being rebuilt per tenant, and access rules have to hold in every tenant environment.

My responsibilities

  • Designed the multi-tenant component system supporting multiple user roles and white-label configurations.
  • Implemented authentication flows with NextAuth.js, including OAuth, JWT session handling and role-based access control.
  • Built a reusable library of accessible UI components from Figma designs.
  • Integrated complex REST API workflows with Axios and the Fetch API.
  • Managed application state with Redux Toolkit.

Technical approach

  • One component system supports multiple user roles and white-label configurations, to speed up feature delivery across tenants.
  • Authentication and role-based access are handled through NextAuth.js, with OAuth and JWT sessions across tenant environments.
  • SSR, SSG and ISR rendering strategies in Next.js are applied to improve page performance.
  • API workflows use optimistic updates and real-time data synchronization.

Architecture and tools

  • React.js
  • Next.js
  • Material UI
  • NextAuth.js
  • OAuth
  • JWT
  • RBAC
  • Redux Toolkit
  • Axios
  • Fetch API
  • Figma

Challenges

  • Keeping role-based access consistent across tenant environments.
  • Keeping the interface correct during optimistic updates and real-time synchronization.
  • Reducing unnecessary re-renders in component rendering.

Outcome

  • White-label configuration and role support built into the component system, to speed up feature delivery across tenants.
  • A shared library that improved UI consistency and maintainability across teams.
  • Improved page performance through the applied rendering strategies.