Backstage Scaffolder 2026: From Template to Self-Service Platform

The Backstage Scaffolder is the heart of any Developer Portal: It enables developer teams to create new projects, services, and components via self-service – without having to wait for a platform team. With the release of Backstage 1.55 in October 2026 and the increasing maturity of the v1beta3 format, the Scaffolder has made a leap forward, transforming it from a practical tool into a strategic platform component.

From Template to Golden Path

The idea behind the Scaffolder is simple: Instead of each team manually setting up its CI/CD pipeline, repository structure, and Kubernetes manifests, the platform team defines unique Software Templates – coded templates that are run through a standardized workflow. Developers select a template in the Backstage frontend, fill out a form, and the Scaffolder does the rest: create repository, generate code skeleton, configure CI/CD, register in the catalog.

With the v1beta3 format, Backstage has fundamentally revised the template definition. Unlike earlier versions, templates are now more clearly structured: parameters define the input form, steps the actions to be executed, and output the return values for the frontend. The steps are processed sequentially and can build on each other – for example, when a publish:github step passes the repository URL to the subsequent catalog:register step.

A template can include any number of steps: clone code from a Git template, replace variables, inject secrets, run Terraform, provision a database, and make the finished product visible in the Backstage catalog. What used to mean hours of manual work becomes a self-service process lasting just a few seconds.

Custom Actions: The Power of Extensibility

In addition to the built-in actions (such as fetch:template, publish:github, debug:log), platform teams can write their own Custom Actions. These are implemented as a Node.js package and integrated into the Scaffolder. This allows practically any internal process to be automated: creating a Jira ticket, provisioning a cloud resource, or generating a certificate.

The Roadie community now lists over 50 available Scaffolder actions – from interacting with cloud providers to integrating with monitoring tools. Backstage itself has provided the scaffolder.requireScmUserCredentials option since version 1.54, which mandates user credentials for certain actions – an important step toward governance.

Task Recovery: Finally Robust Automation

A long-standing criticism of the Scaffolder was its lack of fault tolerance: if the process crashed during execution, the entire template had to be run from the beginning. A GitHub issue from April 2025 put it succinctly: “It is not only inconvenient but technically problematic to have to restart the entire Scaffolder process.”

Backstage 1.55, released on October 13, 2026, fixes this problem with the new Task Recovery feature. When enabled, an interrupted task can be resumed from the last successfully completed step. The step results remain persistent, and task secrets are only deleted once the task has reached a final state. Configuration is done via the new scaffolder.taskRecovery section in the Backstage configuration.

However, the documentation points out an important limitation: actions in resumed tasks should be idempotent or use checkpoints, since a step could potentially be executed a second time. For production environments, the Backstage team also recommends an external storage backend – such as the GCP module – instead of the built-in database, which is limited to 50 MB.

Performance Leap Through Smart Optimizations

In addition to Task Recovery, Backstage 1.55 shows that even seemingly small changes can have a big impact. Michael Todorovic, Senior SRE at Veepee, optimized the GitLab merge request and push actions: Instead of making a separate API request to GitLab for each file, the code now compares files locally. The number of API requests dropped from around 300 to under ten, and execution time from 5–15 seconds to about three seconds.

Such optimizations may sound unspectacular, but in the daily operation of a Developer Portal with hundreds of template executions, they are a decisive factor for acceptance among the developer team.

Conclusion

The Backstage Scaffolder has evolved from a simple template engine into a full-fledged automation platform. With the v1beta3 format, Task Recovery in 1.55, and the growing number of Custom Actions, it now meets the needs of platform teams that take Developer Experience and Governance equally seriously. Anyone running an Internal Developer Portal should view the Scaffolder not just as a “nice-to-have” but as a strategic tool that scales the productivity of an entire engineering team.

Sources

• Backstage 1.55 Adds Scaffolder Task Recovery and Removes Deprecated Catalog APIs – InfoQ (Oktober 2026)
• Writing Templates – Backstage Software Catalog and Developer Platform (Offizielle Dokumentation)
• Backstage Scaffolder Actions Directory – Roadie
• Backstage Software Templates – Offizielle Dokumentation