What is Developer Self-Service?

​

About Developer Self-Service

Developer self-service enables engineering teams to independently access, provision, and manage the resources they need to build and ship software. Instead of submitting tickets and waiting for platform teams to handle requests, developers can directly access infrastructure, environments, and tools through automated workflows with built-in guardrails.

Traditional approaches require developers to wait on platform or operations teams for common tasks - provisioning development environments, deploying to production, or getting access to new services. These manual processes create bottlenecks that slow development and burden platform teams with repetitive work.

A self-service approach removes these bottlenecks by:

1. Automating Common Workflows: Frequently requested tasks are turned into automated, self-service workflows that developers can trigger independently.

2. Implementing Guardrails: Security policies and best practices are built into the automated workflows, ensuring compliance without manual reviews.

​

Key Self-Service Workflows

Common tasks that benefit from self-service automation include:

• Creating new services and applications
• Provisioning development environments
• Deploying code to production
• Managing access and permissions
• Configuring monitoring and alerts
• Handling production operations
• Managing infrastructure resources

​

Tempest Self-Service

Tempest lets you create recipes that automate these workflows while enforcing your organization’s standards. Developers get a single interface where they can trigger pre-approved workflows, while the underlying work happens automatically in your existing tools.