Noosphere Hub — Control Portal

The administrator and operations view across every tenant — support, configuration and oversight.

• 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

• Control Portal — The administrator and operations view across every tenant — support, configuration and oversight.
• Separated from the tenant portal on purpose: an operations tool and a customer tool have different audiences, different risk and no reason to share a deployment.
• Automated CI/CD via GitHub Actions against separate branches — develop, pre-prod, master — with zero-downtime deployments onto AWS EC2.