Self-service for DevOps teams

Sharing practical experience

At the Dutch Azure Meetup hosted by Wigo4it, Pascal van der Horst and Yorick Bolster, both DevOps engineers at Wigo4it, presented a technical session on a self-service release portal. The platform helped teams independently deliver software on Kubernetes. Topics included the frontend, API, Durable Functions, YAML and component-based development and deployment.

Perspective from Horst IT Consultancy

From request to release

A release portal can make recurring tasks accessible to development teams. Its value lies in a predictable process: consistent inputs, clear checks and a result with visible status. Without useful error messages or a recovery path, a portal simply moves manual work to another screen.

What needs to be clear

Start with one frequent release task. Establish who can initiate it, which checks are required and what happens if execution fails. Expand to more teams and environments once that path is clear.

• Ownership. Separate platform operation from responsibility for the application.
• Controlled access. Grant only the permissions needed for the task. Keep changes traceable.
• Recovery. Make failed releases visible and define a recovery or rollback procedure.

Self-service works when independent action and operational control reinforce each other. That requires technology that supports the agreed process and documentation that remains useful during an incident.