Noosphere Hub — Client Portal

The customer-facing half: sign-up, self-service and the day-to-day tasks a client comes back for.

• 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

• Client Portal — The customer-facing half: sign-up, self-service and the day-to-day tasks a client comes back for.
• Independently deployed, so a release here cannot take the operations side down with it.
• Automated CI/CD via GitHub Actions against separate branches — develop, pre-prod, master — with zero-downtime deployments onto AWS EC2.