Backstage Scaffolder 2026: Golden Paths with Software Templates

The Backstage Scaffolder is the heart of any Internal Developer Platform (IDP) based on Backstage. While the Software Catalog answers the question “What exists?”, the Scaffolder provides the answer to “How do I get a new service into the system quickly and correctly?”. With the stable v1beta3 API format and a growing ecosystem of built-in and custom actions, the Scaffolder has become the central tool for platform teams to define so-called Golden Paths.

What is the Backstage Scaffolder?

The Scaffolder is a template system integrated into Backstage. Platform engineers define in YAML files which steps should be executed when creating a new component. Developers select a template in the Backstage portal under /create, fill out a form, and after a few seconds receive a fully configured repository – with CI/CD pipeline, Kubernetes manifests, Dockerfile, and automatic registration in the Software Catalog.

The official Backstage documentation describes the Scaffolder as “a tool that helps you create components in Backstage”. By default, it can load code skeletons, insert variables, and publish the result on GitHub or GitLab.

Template Format: v1beta3

Since the introduction of v1beta3, the template format has stabilized and evolved significantly. A template consists of three main parts:

Metadata – Name, title, description, and tags that make the template discoverable in the portal.

Parameters – A JSON schema that defines the input forms in the frontend. Here, platform engineers specify which information a developer must provide (e.g., service name, owner, repository URL). The parameters can be distributed across multiple steps, keeping complex forms manageable.

Steps – The actions to be executed in series. Each step invokes an action – whether it’s cloning a template repository (fetch:template), publishing on GitHub (publish:github), or registering in the Catalog (catalog:register).

A concrete example from the official documentation shows how a template for a microservice is structured: after cloning a template and inserting variables, a new GitHub repository is created, the code is pushed there, and the service is automatically registered in the Backstage Catalog.

Golden Paths as a Platform Strategy

The greatest value of the Scaffolder lies not in the technology but in the strategy: Golden Paths. Platform teams define “the one, supported way” to build a new service. Each template embodies the company’s current best practices – from the choice of programming language to monitoring and security configuration.

A tutorial on the platform engineering platform from 2026 describes the scenario: a developer fills out a form, clicks “Create”, and receives a new GitHub repository that is already equipped with CI/CD, monitoring, and Kubernetes deployment – in under two minutes. Without the Scaffolder, this process would often take days because the developer would have to read wikis, copy YAML configurations, and ask for cluster access in Slack.

Custom Actions and Extensibility

The Scaffolder comes with a set of built-in actions (fetch:template, publish:github, catalog:register, debug:log, etc.). In addition, platform teams can write their own actions in TypeScript. The official documentation gives a clear recommendation: action IDs should be assigned in camelCase instead of kebab-case, otherwise JavaScript expressions in template variables may fail.

The Roadie documentation highlights that custom actions enable teams to encode governance rules directly into templates, ensuring that every new service complies with company policies from the start.

Template Editor and Dry Runs

An often overlooked but valuable feature is the built-in template editor that Backstage provides in the development environment. It allows templates to be edited in the browser and tested in dry-run mode before they go into production. The dry-run result shows the complete file system changes as well as the logs of each executed step. This significantly speeds up the development of new templates.

Conclusion

The Backstage Scaffolder has become an indispensable tool for platform teams that take Developer Self-Service seriously. With v1beta3, custom actions, and the integrated template editor, it offers everything needed to implement Golden Paths. Anyone building an Internal Developer Platform should pay special attention to the Scaffolder – it is where platform strategy meets developer daily work.

Sources

• Backstage Software Templates (Offizielle Dokumentation) – Übersicht und Konzepte
• Writing Templates (Backstage Docs) – v1beta3-Format und Template-Editor
• Plattform Engineering with Backstage 2026 (Tutorials Technology) – Praktischer Aufbau einer IDP mit Scaffolder
• Build Your First Internal Developer Portal with Backstage 2026 (Tutorials Technology) – Umfassender Leitfaden
• Build your first Software Template for Backstage (Red Hat Developer, August 2025) – Schritt-für-Schritt-Anleitung
• 10 tips for better Backstage Software Templates (Red Hat Developer, März 2025) – Best Practices