Self-service catalogue
Eighteen services in nine categories, from sandboxes and VNets to RBAC, policy exemptions and cost reports, each with live policy checks.
Azure self-service with policy-routed approvals
Unified Service Portal
Everything is self-service. Critical changes still go to the platform team.
One portal for Azure application teams and the platform team that keeps them safe: a self-service catalogue, a routing policy that applies safe changes at once and sends risky ones for approval, and an AI assistant.
Where it is today Pilot-ready (version 0.3)
The problem
Application teams wait; platform teams cannot safely delegate
Every Azure change becomes a ticket, so teams wait days for routine work, while the platform team cannot hand out access without losing control of production, network and cost.
Built for
- Enterprises with an Azure landing zone and a central platform team
- Platform teams drowning in tickets for routine changes
What it does
Capabilities
Routing policy
Every change is checked. Safe changes apply straight away; production, access, network and large cost changes wait for an admin.
Platform admin console
Approval queue with an advisory AI risk summary, policy checks, what-if, cost, blast radius and a topology diff. Keyboard triage and bulk approval of low risk.
AI assistant
Ask mode answers from live data with sources and changes nothing. Do mode drafts a change, which then goes through the same routing rules. It refuses to show secrets.
Build with AI
Describe a workload in plain words and get a pre-approved architecture with a diagram, cost, Bicep, a GitHub workflow and what-if.
How it works
The flow
- Request
- Policy checks
- Routing decision
- Apply or approve
- Change pipeline
- Notify
Try it
Send a change through the routing policy
Choose a change. The simplified policy below follows the portal's rules: what is checked, how risky it is, and whether it applies at once or waits for the platform team.
$ storage account st-orders-prod: public network access → disabled
- Policy checks
- ✓ Change reduces exposure
- ✓ Requester owns the subscription
- Routing
- Risk: low (a security improvement)
- Production, but tightening only
- Change pipeline
- What-if: one property changes
- Applied; the security finding closes
Applied straight away
Security improvements apply at once, even in production.
Simulated walkthrough with sample data. Nothing here connects to a live system.
Built with
Technology
- React 19
- TypeScript
- Vite
- Tailwind
- TanStack Query
- MSAL
- Azure Functions (Python, FastAPI)
- Bicep
- Playwright
- pytest
Stated plainly
Limitations
- Version 0.3 is ready for an internal pilot; the demo build runs on fictional data in the browser.
- Connecting it to your tenant, subscriptions and approval groups is part of the engagement.
See Unified Service Portal on your environment.
Tell us where you are. An engineer replies with a proposal, not a sales script.
All products