Project Name
5-Day Environment Provisioning Cut to Minutes With Backstage IDP for an Insurance Enterprise
A large North American insurance enterprise with hundreds of developers across multiple product lines filed tickets and waited 3-5 business days for every new environment. The DevOps team processed 50+ provisioning requests per week manually, leaving no capacity for platform work. No golden path for new services existed, no service catalog tracked ownership, and CI/CD pipelines varied wildly across teams. Applying its AI-First approach, Ksolves designed and deployed a self-service Internal Developer Platform on Backstage and Dagger – turning days of waiting into minutes of clicking.
- Provisioning Delays Blocking Developer Velocity: Every new environment request took 3-5 business days, forcing developers to wait idle or work with outdated shared environments that introduced configuration drift and testing conflicts.
- DevOps Team as a Full-Time Ticket Queue: The DevOps team processed over 50 environment provisioning tickets per week manually, consuming the majority of their bandwidth and leaving no capacity for platform improvements or reliability work.
- No Golden Path for New Services: Each team bootstrapped OCI-native services from scratch using ad-hoc scripts - inconsistent infrastructure patterns, missing security controls, and duplicated effort across every product line.
- Zero Service Catalog or Ownership Visibility: No centralised registry existed to track which teams owned which services, their dependencies, documentation, or operational status - making incident response and onboarding slow and error-prone.
- Inconsistent CI/CD Pipelines Across Teams: Build and deployment pipelines varied wildly with bespoke YAML configurations that were untestable locally, fragile, and impossible to standardise or audit across the organisation.
- No Cost or Environment Accountability: Without visibility into environment ownership or lifecycle management, orphaned infrastructure accumulated silently - inflating OCI spend with no attribution mechanism and no accountability.
Ksolves built a self-service Internal Developer Platform on Backstage and Dagger. One governing principle: developers provision production-ready OCI environments in minutes through guided self-service - no ticket required. OCI Resource Manager handled all IaC provisioning, ensuring every environment was reproducible and auditable.
- Backstage Service Catalog: Deployed as the single pane of glass mapping every OCI service - OKE workloads, OCI Functions, Oracle Autonomous Database instances - to its owner, dependencies, documentation, environment status, and cost. The 'who owns this?' problem is eliminated entirely.
- Backstage Scaffolder with Golden Path Templates: Organisational best practices encoded into reusable templates - developers select a service type, fill in form fields, and Backstage triggers the full provisioning pipeline. The 3-5 day ticket workflow was replaced with a minutes-long self-service flow.
- Dagger-Powered CI Pipelines: All CI/CD logic rewritten using Dagger - locally testable, portable, and consistent across every team. Every build, test, image push to OCIR, and deployment to OKE follows the same programmatic pipeline structure with no YAML fragility.
- OCI Resource Manager (Terraform) for Infrastructure Provisioning: All environment provisioning handled through Terraform stacks managed by OCI Resource Manager - reproducible, state-managed, and fully auditable for every infrastructure change triggered by Backstage Scaffolder.
- Environment Ownership and Cost Visibility: Backstage surfaces environment ownership, provisioning status, and cost metadata per service - giving leadership and DevOps teams real-time resource utilisation visibility and enabling cost accountability for the first time.
Technology Stack
| Category | Technology |
|---|---|
| Platform | Backstage + Scaffolder |
| CI/CD | Dagger |
| Infrastructure | OCI Resource Manager (Terraform) |
| Compute | OCI Kubernetes Engine (OKE) |
| Database | Oracle Autonomous Database |
| Registry | OCI Container Registry (OCIR) |
- Provisioning Time Cut From 5 Days to Under 15 Minutes: Developers provision production-ready OCI environments through Backstage self-service templates in under 15 minutes - a 95%+ reduction from the 3-5 business day ticket workflow.
- 50+ Weekly DevOps Tickets Eliminated: Self-service provisioning removes the manual ticket queue entirely, freeing the DevOps team from provisioning overhead and restoring capacity for platform reliability and engineering work.
- CI/CD Standardised Across All Teams: 100% of teams use Dagger-powered pipelines that are locally testable and structurally identical - bespoke YAML fragility and deployment inconsistency eliminated across the entire enterprise.
- First-Time Service Ownership and Dependency Visibility: Backstage service catalog provides real-time ownership, dependency maps, and documentation for every OCI service - incident response and onboarding no longer depend on tribal knowledge.
- Orphaned Infrastructure Eliminated With Cost Accountability: Backstage environment dashboards enable per-service cost attribution and ownership accountability for the first time - unchecked infrastructure sprawl replaced with governed lifecycle tracking.
“For the first time, our developers can go from idea to running environment in minutes instead of days and our DevOps team finally has bandwidth to focus on platform reliability instead of fielding tickets.”
-VP of Platform Engineering
A large insurance enterprise where developers waited 3-5 days for every environment and the DevOps team spent most of its time processing tickets was transformed into a self-service, governed engineering platform through Ksolves DevOps consulting services. Backstage golden path templates and OCI Resource Manager now provision production-ready environments in under 15 minutes. Dagger standardised CI/CD across all teams. The 50+ weekly ticket queue was eliminated, service ownership became visible in real time, and orphaned infrastructure was replaced with governed cost accountability, with the IDP foundation ready to extend into compliance automation and FinOps guardrails.
DevOps Team Spending More Time on Provisioning Tickets Than on Platform Engineering?
