Noosphere Hub — Tenant Portal

The per-organisation workspace: each tenant’s own data, users and settings, isolated from every other.

• React
• Node.js
• AWS EC2
• GitHub Actions

The problem

Noosphere Hub is a multi-portal platform: three distinct frontends over one backend, each serving a different audience — clients, tenant organisations, and the operations team.

Building them as one application would have meant every deployment risking all three audiences at once. They are three, and they ship separately.

What I built

• Tenant Portal — The per-organisation workspace: each tenant’s own data, users and settings, isolated from every other.
• Deployed on its own branch and pipeline, which keeps a tenant-facing change off the same release train as the client site.
• Automated CI/CD via GitHub Actions against separate branches — develop, pre-prod, master — with zero-downtime deployments onto AWS EC2.