Introduction
Prangana Nexus is the developer control plane for the Prangana platform. It gives engineering teams a single place to create projects, provision services, manage team access, and monitor infrastructure — without writing cloud configuration or infrastructure code.
New to Nexus?
Jump straight to the Quick Start guide to go from sign-in to a running service in under 10 minutes.
Platform architecture
What each layer does
| Layer | Responsibility |
|---|---|
| Landing | Marketing site, sign-in, sign-up, and onboarding flow |
| Azure AD B2C | Authentication and token issuance |
| Nexus | Developer UI — the unified control plane |
| Atlas | Manages projects, organizations, users, environments, and workspace membership |
| Fabric | Orchestrates service provisioning, CI/CD pipelines, and deployments |
| Registry | Hosts versioned golden path templates |
| Control Plane | Issues and validates licenses; publishes releases for self-hosted deployments |
| Depot | Self-hosted customer portal for downloading releases and managing licenses |
| Cloud | The actual infrastructure (AKS, ACI, Azure Functions, etc.) |
Key capabilities
| Capability | Description |
|---|---|
| Dashboard | Live view of projects, active provisioning, failures, and templates across your workspace |
| Projects | Create and manage Atlas-backed project workspaces with deployment strategies |
| Services | Provision real infrastructure from golden path templates through a guided wizard |
| Environments | Define ordered deployment environments (dev → staging → prod) per project |
| Templates | Browse the Prangana Registry catalog of 14 versioned, production-ready service templates |
| CI Pipeline | Live CI pipeline status and stage visualization via GitLab webhook integration |
| Service editor | Browse and edit service configuration files directly in the Git repository |
| Delivery profiles | Configure organization-wide toolchain connections (source, CI, registry, artifact, deployment) |
| Deployment infrastructure | Manage cloud provider credentials, accounts, and deployment targets |
| Production approvals | Gate production deployments behind an explicit approval workflow |
| Settings | Manage account users, invitations, organization members, directory connections, and roles |
| Command palette | Search projects, services, and templates instantly with Cmd K / Ctrl K |
Authentication flow
The Landing site handles authentication and onboarding. Once a user completes sign-up, they are redirected into Nexus with their organization context (orgId, orgName) passed via URL parameters. Nexus persists this workspace context in localStorage and restores it on subsequent visits.
Next steps
- Quick Start — go from zero to a running service in under 10 minutes
- Authentication — how sign-in and workspace handoff work
- Projects — understanding Atlas projects
- Services — understanding Fabric services and statuses
- Templates — the 14 golden path templates available