Engineering workflows are spread across many independent systems. To launch a new microservice or prepare an environment, engineers may switch between GitLab, VMware, Jenkins, Jira, Zabbix, and other tools. This creates context switching, manual errors, slow delivery, and no single source of truth for services and ownership.

Banks need faster product delivery without sacrificing control, auditability, and operational reliability. Platform engineering and internal developer portals are becoming a practical way to reduce friction while keeping governance centralized.

An Internal Developer Portal MVP that acts as an orchestration layer over existing tools. The portal should provide self-service provisioning, service inventory, build and monitoring visibility, incident/ticket linking, SSO-ready access control, and an audit trail of actions performed through the portal.

• Create a service catalog showing service, repository, build status, monitoring status, owner, and related tickets.
• Build a self-service form that creates a repository, CI/CD pipeline, and virtual environment through APIs or mocked integrations.
• Link monitoring alerts and Jira tickets to specific services in the catalog.
• Add operational metrics showing how much time is saved by automated workflows.
• Position the product as a Backstage-like portal adapted for regulated enterprises and banks.

• DevOps, platform engineering, or infrastructure automation team
• Experience with GitLab, Jenkins, VMware, Jira, Zabbix, Kubernetes, Terraform, or service catalogs
• Strong backend integration and workflow automation skills
• Ability to design developer-friendly UX with enterprise governance

• Service inventory/catalog
• One self-service provisioning workflow
• Mock or real integrations with GitLab, Jenkins, VMware, Jira, and monitoring data
• Build, monitoring, ticket, and owner visibility per service
• Unified login/role model concept
• Audit trail for portal-triggered changes
• Operational metric comparing manual vs automated workflow time

• One portal action can trigger a realistic end-to-end workflow across multiple systems.
• Engineers can see service ownership, repository, build status, monitoring, and tickets in one place.
• The prototype demonstrates fewer manual steps and lower provisioning time.
• All actions are logged for governance and troubleshooting.
• The portal feels like the first application an engineer would open at the start of the workday.

• The portal should orchestrate existing tools rather than replace them.
• Auditability and access control are mandatory for enterprise adoption.
• For hackathon or MVP purposes, simulated integrations are acceptable if interfaces and workflow logic are clear.