Project: Backstage (App Definition and Development / Application Definition & Image Build)
File: ADOPTERS.md

If you're using Backstage in your organization, please try to add your company name to this list. It really helps the project to gain momentum and credibility. It's a small contribution back to the project with a big impact. You can do this by using the or by editing this file after following the . | Organization | Contact | Description of Use | |--||| | | | Main interface towards all of Spotify's infrastructure and technical documentation. | | | , | Initial work being done to unify platform tooling. | | | | V2 self-service platform. | | | | Hosted, managed Backstage with easy set-up | | | , | Central place for developing and sharing services in our insurance ecosystem. | | | | Initial work on Engineering Portal service platform. | | | | Central place for developers to develop and maintain applications | | | | Replacing the frontend of , their service registry. | | | | Developer portal, main gateway to our infrastructure, documentation and internal tooling. | | | | Engineering Portal with all of our apps and services, overview about our deployment regions and scaffolding new services. | | | | Developer portal, service catalog, documentation and tooling | | | | Initial work as a unified interface for all of Grab's internal tooling | | | | Building a developer portal for scaffolding projects towards our unified build environment and microservice stacks | | | | Unifying separate tools that developers are using today (i.e. monitoring, dead letter queues management, etc.) into a single platform. | | | | Building V2 of the Internal Development Portal. | | | | Developer portal - hub for all engineering projects and metadata. | | | | EG Developer Portal | | | | Developer portal (Tech Docs, Service Catalog, Internal Tooling), we use vanilla Backstage FE and custom BE implementation in Go | | | | Developer portal with tech docs, service catalog and a bunch of other internal tooling | | | | Internal developer portal for service overview and insights, API documentation, technical guides, onboarding guides and RFC's. | | | , | The Developer Portal has been called `Pandora`. Provides an overview of Trendyol tech ecosystem. TechDocs, Catalog, Custom Plugins and Theme. | | | | Creating our first developer portal and tech-docs. Exploring Service Catalog, Tech Insights and Cost Insights as well. | | | | A centralized UI to understand how a service fits in the whole Brex architecture and manage a teams engineering dependencies. | | | | Internal developer portal for services, single page apps and packages overview, API documentation, technical guides, tech-radar and more. | | | | Developer portal for a full-stack software development ecosystem that accelerates consistent and repeatable Modern Software Development practices for internal innovation and investments. | | | | Foundation for our engineering portal and cloud insights. | | | | Developer portal, initially focused on software templates and

| | | | Developer portal - helps us keep track of our customer projects, onboard new developers & improve our development process | | | | Developer Portal - A place for us to keep track of our projects and documentation for all services and processes | | | , , | Ingesting all of DAZN's repos for the catalog, migrating our internal platform apps (pull request boards, release information, inner source marketplace etc) to Backstage plugins (where applicable). | | | , , | Our developer portal at HelloFresh - Spread across an organisation of 500+ engineers globally. | | | | Developer portal to provide discoverability to all internal components, APIs, documentation, and scaffold templates with integrations to our internal infrastructure tools. | | | | Developer portal, main gateway to our infrastructure, documentation and internal tooling. | | | | Developer portal that brings everything an engineer needs to provide value into a single pane of glass. | | | | Developer portal focused on standardizing practices, centralizing documentation and streamlining developer practices. | | | | Developer portal, services catalog and centralization of service metrics. | | | | Developer portal for tech docs, service catalog, plugin discovery and much more. | | | | Centralization of all services, standards, documentation, etc. We started the deployment process. | | / | | Internal developer portal - Documentation, scaffolding, software catalog, TechRadar, Gitlab org data integration | | | | Developer portal for documentation of core libraries and repositories. | | | , | Development team home-base, promoting service discoverability, resource dependencies, and tech radar | | | | Developer's portal with software catalog at it's core. Hosts API Specs, Tech Docs, Tech Radar and some custom plugins. | | | | Developer portal with service catalog, API docs, Event docs, service templating, and cost insights. | | | | Improve services visibility and operations for service owners and developers. | | | , | Developer portal showing metadata and docs for over 2000 microservices. We have built a number of plugins such as a UI for our system to measure , and a UI to show deployment and config change events. | | | | Developer Portal for our developers at Vaimo, currently docs and self-service towards our internal PaaS based on k8s. Plans to extend the catalog into Projects, Environments etc | | | , , | Developer portal for service catalog, technical documentation, and APIs. | | | | Developer Portal for internal dev team across the globe | | | | Developer Portal for internal dev team across the globe | | | | Developer portal, gateway to our infrastructure, documentation, service catalog and internal tooling. | | | | Developer portal for all internal engineers to access documentation and tooling. | | | | Developer portal: documentation, service templates, org structure, service catalog, plugins for integration with internal and third-party systems. | | | | Developer portal: documentation, service templates, org structure, service catalog, plugins for integration with internal systems. | | | , , , , | Developer portal for service catalog, integration with internal systems, new service onboarding. | | | | Developer portal for service catalog and scaffolds, publishing Github docs and API documentation, visualising our internal tech radar and our product engineering org structure. | | | | A multi-cloud control plane to create, manage and deploy any kind of resource easily and centrally via a Developer Portal that centralizes via a self-service catalog the templating and ownership of services, the available documentation, the overview of the components that compose an entire domain and all the data of the service lifecycle. | | | | Showcase shared services to our internal customers. | | | | Developer portal as a centralized place to find people, services, documentation, escalation policies and give

This portal is also being used as a centralized search engine for engineering specific documentation. | | | | Developer portal as a for the organization: catalog of people, services, documentation, feature toggles, escalation policies, etc. | | | | Developer portal enabling engineers to manage and explore software and documentation. | | | , , | Developer portal, service catalog, documentation and tooling | | | | Developer Portal, documentation, monitoring, service catalog for our insurance ecosystem | | | | Developer Portal: documentation, monitoring, service templates, service catalog for our micro services | | | | A centralized service catalog with documentation for our service engineers. | | | , , | Developer portal for building services through templates, service catalog with ownership of services, documentation and metrics providing autonomy and visibility for all. | | | , | Developer Portal: Service Catalog, Documentation, Software Templates and more making our internal teams' lives easier! | | | , , , , | Reduce the friction of accessing the information engineers need about Globo's digital services through a coherent and centralized experience. | | | , | Developer portal allowing our global teams to explore and create applications, documentation and cloud infrastructure easily and quickly | | | | Improve onboarding experience of new developers. Discover faster and painlessly developer documentation, API definitions and team information. Provide useful dev metrics in a central place. Provide easy-to-use templates for new services. | | | , | Primary usage: software catalog and templates<br/> Emerging usage : TechDocs, Explore Ecosystem, TechRadar, etc | | | , | A centralized service catalog of our documentation for our service engineers. | | | | "Single pane of glass" developer portal for providing a best-in-class developer experience to our product teams and making Mox the best tech environment in Hongkong | | | | Future-motive Developer Portal to help our teams create technology to make everything about buying and owning a car better. | | | , , , | Central developer portal to access everything a developer needs such as docs, internal service catalog, and the ability to quickly create a new service from a template. Internally developed Backstage plugins allow us to customise the experience to how we work. | | | | Dev portal - software catalog, tech-docs, scaffolding | | | | The main Developers Portal to centralize docs, applications and technical metrics. | | | , | Our developer portal - primarily used for cataloging and scaffolding with the ambition to expand with more feature adoptions over time | | | | Developer portal to our internal services, build on open-source software (including Kubernetes) in our own datacenters. Our Portal allows our team members to navigate inherant complexity and standardise. | | | | Developer portal, service catalog, tech docs, API docs and plugins | | | | Our developer portal which centralises applications, reduces cognitive load and provides teams insights. | | | , | Developer portal to streamline the development practices. Integrated with service catalog, software templates, application monitoring, tech docs and plugins. | | | , , , | Developer portal hosting service catalog and API documentation, as well as cloud infrastructure details, operational visibility tools, and a custom plugin for browsing notable platform change events, such as deployments and configuration updates. | | & | , | Self-Service Platform | | | | DevEx engagement hub (dev portal: docs, standards, Q&A) and extensive assets catalog (APIs, services, code, data,

for the pan-HP internal developer community. | | | , , | Part of offering; internal developer portal | | | | Initial work being done to centralize documentation for all our microservices and APIs, as well as scaffolding new services and tracking code quality | | | , | Supporting engineers at scale with self serve access and connecting the dots of our engineering platform and services, enabling product teams to move faster and go further, and unleashing innovation, reuse and co-creation across the organisation. | | | , | Centralized Developer Experience portal, putting all of our tooling behind a single pane of glass and creating a living service catalog. | | | , , | A central portal containing information about our applications, services, processes and other software assets to be used by Fortum software engineering community. | | | , | Developer portal - centralized software catalog and templates to enable self serve and reduce cognitive load. | | | | Centralized developer portal with software catalog, software templates, techdocs and some plugins from community and by our own. | | | | Software catalog and documentation platform | | | , , , , , | Centralized developer portal with catalog, documentation, and software templates to build a ready to go application, including pipelines (CI/CD) and cloud services provisioning | | | | Developer portal for software discovery, API documentation and templating | | | , | Developer portal, services catalog and centralization of metrics from Grafana, Sentry and GCP. Furthermore, centralization of documentation and infra details like DNS, Network services, SSL and so on. | | | , | Developer portal for all engineer to provide discoverability to all internal components, APIs, documentation and to scaffold templates with integrations to our internal tools extended by plugins from our community. | | | , , | Developer portal - software catalog, technical documentation, software templates, tech radar and exploration of used tools/services | | | | Centralized Developer Experience portal - Software catalog and documentation platform, software templates, techdocs, scaffolding, self-service infrastructure | | | | Developer portal for software catalog, discovery and a view of the technologies we are using across the organisation, we are looking to explore how we can enrich our entities in Backstage by integrating a software bill of materials. | | | | Centralized developer portal with software catalog, tech docs, templates, and more. | | | | Developer portal with software catalog, scaffolding, tech docs, templates, and infra. | | | | Developer portal with software catalog, documentation, monitoring, runbooks, tech radar and more. | | | , | Internal Developer Portal, service catalog, tech docs and more | | | , | Internal DevOps portal hosting our software and dataset catalog, as well as custom plugins for observability, service virtualization, deployments, incident managment and quality metrics. | | | | From developers for developers: software catalog, techdocs and heavy use of scaffolder to drive reuse on engineering level forward. Part of inner source initiative. Multi national setup coming. | | | , | Internal Developer Portal, an overview of all running software, architecture documentation and more; replacing and unifying a variety of internal tools. | | | , , , , | Developer portal, scaffolding, services catalog. We are looking to centralize automations and information for the whole engineering team

| | | , | Internal developer portal, service catalog, tech docs, api doc | | | | Internal Developer Portal, a catalog of all microservices, architecture documentation, and templates to generate developer resources. | | | | Developer portal for developer tooling and technical documentation. | | | | Centralised discovery, adoption and devops automation hub for Engineering & Architecture. | | | | Internal Developer Platform for developer gated CI/CD templates, technical documentation, cloud automation service catalog, etc. | | | | Centralize our multiple UI in a single portal. Simplify onbording, new features and harmonize how people search information. | | | | Centralized documentation of service ownership, APIs, and documentation, and new service creation with a custom scaffolder - . | | | | Internal Developer Portal featuring catalog, tech-radar, ownership management, component creation (scaffolder) and centralized infrastructure management -- probably more to come. | | | , | Innersource, software analytics, knowledge base for 360 software assessments, collaborative applications, hub for tracking and sharing IP assets. | | | | Single point of entry for all our engineers (Developer portal), Tech radar, catalog, templates (paved roads) and tech documentation. | | | | It's early days for us, we're trying to start small with catalog, tech docs and unified search. Future ambitious vision includes scaffolder for one-click component addition, building out integrations with CI/CD tooling, kubernetes clusters, monitoring/alerting tooling etc. and aiming for a frictionless "golden path" for engineers! | | | | We are moving from a monolith to microservices-based architecture. We are developing a developer portal based on Backstage to create a service catalog for our new services. All the services created are onboarded Backstage and engineering teams are using a cookie-cutter-based template from backstage to initiate a new service. | | | | We use it within our X-Series division (https://vendhq.com) to catalog ~100+ systems and ~350 components! | | | | We are using Backstage as our Developer portal | | | | Backstage enables us to bootstrap our middleware environment of new services for our Dev teams in a matter of seconds. CI, CD, testing, logging, deployments are all taken care of to get them up and running in less than 60 seconds. | | | , , | Internal developer portal which provides templates for creating new Java or Go microservices seamlessly. Also includes a tech radar and a visualization of our CD pipeline. | | | | Our primary focus is on the service catalog. Backstage is replacing our homemade service catalog. The switch was quite simple due to the catalog processor API. | | | | Backstage is the heart of Laybuys new centralised Development Platform, bringing disparate development tools and experiences into a single easy-to-use portal. It simplifies software and API discovery, project scaffolding, and technical documentation, enabling us to embrace golden path development and automate software standards. | | | | Helps us drive the change at scale. Puts light on services, resources, and dependencies. One tool that rules them all through plugins we created for that purpose. We are aiming to put Backstage at the center of every developer's work (Actionable items, Debugging, Monitoring, Provisioning, etc...) to improve their happiness | | | , , | Internal developer portal to provide a centralized place for engineers to see an overview of their team's services and information related to the service from other systems. Initially focused on the software catalog, techdocs and

| | | | API Catalog, Tools Management & Control Hub | | | | Software Project Catalog | | | | We are importing our catalog into it to keep it under control. The next step is start using templates | | | | We want to kick ass at speed, so we're currently building up a catalog of our existing software, and looking into how Backstage can support us in our journey towards autonomous product teams. Both to improve speed to market and operational awareness. | | | | Catalog, tech docs and automation | | | | Developer Portal to track our projects, documentation, observability tools and more | | | | As a support tool for developers, following the principles of "Developer Experience". In order to make the developer's day to day more practical, efficient and, why not, happy. | | | | Centralize services used internally with many plugins | | | | Cataloging and documenting our service offerings to offer our internal developers a better operational journey | | | | Easy to find out Project details, ownership, dependent services, Documentation, it is very useful for developer. | | | | Services exploration, documentation and project generator | | | | Internal tool management and docs | | | | Is part of our IDP | | | | We're working with multiple F100 clients for digital transformation and Backstage is a key part of our landing and acceleration strategy. | | | | Software catalog, product dependency visualization | | | | We use backstage as a Service Catalog and rely on the TechDocs feature | | | | Single pane of glass for organisational and operational information for all services across our systems. | | | | Developer portal for all development needs - security, AWS, k8s, build and deployment pipelines and more | | | | Software Project Catalog | | | | Service catalog, Software templates to enforce best practices and tech insights to track mandates & migrations. | | | , | Improving developer experience by centralizing documentation and internal APIs. Goal: Foster InnerSource collaboration and speed up onboarding time in our 500+ people Product & Engineering org. | | | | Rails modularization effort awareness, tech organization discoverability. Improving the daily workflows and collaboration processes of our engineers. | | | | Developer portal, universal software catalog, and centralized taxonomy platform. | | | , , | We're providing Backstage to our collaborators to ease their daily jobs, and let them extends it using plugins. | | | , | P&G leverages Backstage to build internal developer portal to ensure developers' happiness. This developer portal shall act as single source of information needed by development teams to seamlessly create, find and maintain their software components/resources/documentation. | | | | Developer portal for centralized visibility, reporting, and tooling across multiple organizations. | | | | Service catalog, developer portal, and technical documentation | | | | To provide an automated golden path to developers, with a focus on discovery and documentation | | | | We are building a platform for internal web tools | | | | Still in a experimental phase/assessing the organisational fit. We will be using it mostly a developer portal -- pretty standard use case. | | | | We're starting to use Backstage as the central hub for service discovery, documentation, and develop experience. | | | | Initial Work Developer Portal with TechRadar, Service Catalogue, TechDocs, anything about platform & infrastructure

| | | | We are building our developer portal. Software catalog, Tech Radar and Scaffolding are among the initial features. | | | | Central developer platform for creating new apps via templates, getting an overview via software catalog, etc | | | | Currently using Backstage as an internal documentation portal. | | | | We are building the internal developer portal using Backstage and bringing up all integrations and service information at one place. | | | | An active community member and contributor, Frontside offers both custom development as well as enterprise support services to help teams get the most out of Backstage for the long-run. | | | | StepStone is using Backstage to solve problems around ownership and visibility of our applications. We have thousands of repos, multiple legacy systems and a growing platform that is hard to maintain. Backstage is forming the centre of our push to embrace the chaos. | | | | Developer Portal for internal engineers to access service catalog, documentation, observability, infrastructure and internal tooling. | | | | Users can request a Gitlab user, which creates a commit with the Terraform code. | | | | Developer Portal to improve our Developer Experience, identify ownership and track metadata for our services and tools. It's our Service Catalog. In addition to that, we use it for Service Creation, and much more. | | | | We are in early stages, but using it to get overview of our repositories and ownership of these. We want among many things to use it for compliance and easier access to key metrics for our repos. | | | | Backstage is our developer portal. We use it as service catalog and for technical documentation. | | | | We are using Backstage as our Developer portal as well as for hosting our DevOps portal for software catalog. | | | | We are using the Software Catalog, Software Templates, API documentation, and Techdocs to try and centralize service information. | | | | At Mercedes-Benz we use it as a developer portal with software catalog, TechDocs, Scaffolding and custom plugins. It provides an overview of our tech ecosystem to our product development teams. The portal also serves as a way to foster collaboration among the numerous companies of the Mercedes-Benz Group. | | | | We are building the internal developer portal using Backstage project and centralizing all services information at one place. The portal helps us track down repositories ownership as well as direct access to key information on every component. | | | | We are building our Developer Portal using Backstage to have a better control over our software ecosystem, integrate SDLC tools and promote best practices | | | | Internal developer portal, service catalog with CI/CD tools. | | | , , and | William Hill are leveraging Backstage to build our Engineering Portal. Our mission is to centralize the software catalog inventory to enable service discoverability, reduce the onboarding time for new Engineers, provide a single pane of glass to accelerate Developer Productivity and Save Engineers time. Our aspiration is to create an InnerSource community focussed on organization-wide patterns that are re-usable and can be self-served with the Scaffolder. | | | , | Vodafone NZ are leveraging Backstage to build centralised and self service Engineering

Our mission is to standardised Pipeline templates across the Engineering teams, One shop stop to create the pipelines and repository with a template approach which reduces creation part from days to minutes and no wait time for developers. A unified view for Azure DevOps pipeline, Azure Repo pull requests, Deployment status from Azure RedHat Openshift-ArgoCD and SonarQube Security and code quality scans report on a single pan to provide a streamlined view for all microservices across the app stack. | | | , | We're starting to use it as the main tool of a DevOps platform. Our goal is to provide software templates, centralize our software catalog enabling efficient service discovery, and make it easy to manage the entire software ecosystem in one place. | | | | Developer portal, service catalog and documentation | | | | Using it as a Software Catalog to get an overview of our systems, for ourselves and our customers. | | | | | | | In PoC stage, planning to land it for cloud platform dev team. | | | | Developer Portal: Software Catalog, Software Templates and Techdocs. | | | | Developer portal, service catalog, documentation and self-service platform | | | | We are a consultancy helping teams implement and customize Backstage. | | | | To catalog components and teams | | | | Central Hub for all the company modules, enabling the track of ownership of components and resources and how they relate to each other. | | | | Our engineers use the Backstage to solve problems around ownership and visibility of our applications, access service catalog, documentation, observability and infrastructure. | | | | We are creating a developer portal powered by Backstage, with software catalog, documentation, templates and integrations to our infrastructure and internal tools. | | | | Centralized portal with our internal services, infrastructures, relationships between systems, technical documentation, templates, monitoring and custom integrations with our own DX tools. | | | | Internal developers portal for technical documentations, components ownership and relationship, software templates and integrations with internal tools | | | , , | Simplifying the developer experience through centralized team member portals. Our current focus includes the adoption of Tech Docs, Software Catalog, Software Templates, the plethora of plugins, and contributing features back to Backstage. | | | | Getting started with the adoption for Monorepo projects | | | , | Developer portal to quickly create and deploy microservices. | | | | Internal developer portal for discovery of applications, projects and teams. Using several plugins like the Software Catalog and Tech Insights for promoting best practices and supporting our SDLC toolchain | | | | Internal Portal consolidating documentation, making it easier to manage applications, internal developer community platform, and self-service cloud infrastructure + pipelines. | | | | Internal software catalog, tech radar, documentation portal to disambiguate software and domain ownership, foster exploration of available developer platform services and tools, improve communication, democratize documentation and knowledge sharing, and coordinate the software lifecycle; all in service of a best-in-class developer experience. | | | , | We're using Backstage as our Internal Developer Portal and main microservices catalog for mapping ownership, health and metrics for each one. | | | | Internal software catalog, documentation and ownership, improve communication, democratize documentation and knowledge sharing, and coordinate the software lifecycle; all in service of a best-in-class developer experience. | | | | We're using Backstage as our Credit Team Developer Portal and microservices catalog for mapping

We are also using mkdocs for microservices documentation. | | | | Developer portal focused on an enterprise-wide app catalog to track ownership and surface APIs. | | | , , | We are building our Internal Developer Portal using Backstage to improve developer's experience by centralizing our services catalog and identifing microservices' ownership. Also we are going to improve Technical Documentation and speed up development using software templates to help squads in creation and deployment of new microservices. | | | | Vipps use backstage for our service catalog, documentation, and developer portal. Using templates we are able to simplify the developer experience when deploying new services to our platform. | | | | Backstage is helping us to improve and acelerate dev experience helping teams to quickly find technical documentation, infrastructure templates, pipelines, software components and quickstarters that have been developed by our squads in a inner source friendly environment. | | | , , | We're using Backstage as our internal Developer Portal to catalog and collect repositories and microservices pieces of information like ownership, deployment time, and documentation. | | | , , and | Harnessing the power of central catalog inventory and self-serving software templates | | | | Backstage is the developer portal for our 'software delivery platform'. Consolidating developer tools to one place, and providing automation to make it easy for developers to create and deploy applications to Kubernetes | | | | We're using Backstage to give visibility and promote ownership of all our applications, resources and tools. Now moving to use it as a Developer Portal to create applications, AWS resources etc. | | | and | Backstage helps us to organize and make available, in a simple and direct way, all the infrastructure for new projects. In addition, it has become a great support tool for our developers. | | | | We're using Backstage as part of our dataplatform product. It integrates with the infrastructure components and is the developer portal for all the platform users. | | | | Developer portal, service catalog, documentation and tooling | | | , and | Backstage is our one stop shop to find everything related to all our services, such as ownership, dependencies, production status, tech health and much more. | | | , | We use backstage as our developer portal to provide visibility of our software, ownership, strategy, and the state of maturity across disciplines. | | | , | Backstage provides us with a public service catalog and serves as a gateway to our community cloud. Our instance is publicly available to everyone () | | | | We are hitting a critical point in our scale (100+ engineers) and need to get a handle on discoverability and ownership. The Service Catalog, TechDocs and Search are essential to us to achieve that. | | | | We are using Backstage focusing on improving experience of developers, minimizing friction from idea to production. We call our portal as "Hyperspace" and very excited for our community (2000+ engineers) that finally we have a platform to boost our productivity! | | | We are adopting Backstage as the new reliability platform inside the company. We are migrating UIs of our internal developer tools to Backstage for a better user experience. | | | Integrating Backstage as the visualization layer & tactical overview of our services and teams. | | | Developer Portal Catalog (components, APIs, resources, users, groups) and organization

| | , , | Developer Experience Tool with an aim to to improve processes, boost productivity, finding of information/docs and building tech engagement throughout the business. | | , | We are starting to use Backstage as a developer portal to share API specifications and documentation, to quickly onboard new projects with the software templates, and to help developers discover software through the catalog. | | , | We're assessing Backstage as our developer platform at Cazoo with a focus on reducing cognitive load for our engineers. We're currently aiming for 3 outcomes: creating visibility into service ownership across teams, improving the discoverability of event schemas and relationships, and improving the discoverability of technical documentation and best practices. | | | | We are starting to use it as a single place to find all component information in a distributed architecture. | | | | We use Backstage for our service catalog and are actively looking into adopting other plugins like TechDocs, TechInsights and Software Templates. | | | | We are building our internal develper portal on top of Backstage. | | | | Developer Portal for our Projects we develop for our Customers and Hosting them On Kubernetes. | | | | Developer portal enabling discovery of products, services, and documentation throughout the enterprise to ultimately reduce friction and improve time-to-market. | | | | Backstage is used as a optional UI for the , a framework for building platforms. | | | We are assessing Backstage as our internal developer portal @Bankdata. Goal is to reduce cognitive load and friction for developers and thereby improving developer experience, onboarding and productivity. Expect use of Software Catalog for discoverability and ownership, Tech Docs and Software Templates to integrate tooling and best practices. | | | B3 (Brazilian Stock Exchange) will implement a self-service platform focused on software development based on Backstage. The tool will primarily focus on product development and software engineering teams, as well as professionals from other areas who are also involved in software delivery. The new platform will function as a portal where teams can access tools, codes, and templates that have already been tested and are available, serving as building blocks for the development of new solutions. | | | | Porto (Brazilian insurance company) Centralized developer portal with software catalog, application templates, maturity radar, component taxonomy standardization, and automation in the integration with DevSecOps processes. | | | | We use Backstage to create a great developer experience across Einride's entire software stack - from autonomous and electric vehicles to cloud systems - and we've developed a for interfacing with Backstage from our Go tooling. | | , | We are building our internal develper portal on top of Backstage.| | | | Backstage is used within our Developer Experience Platform (DXP) in order to increase self-service, standardization and discoverability across our Engineering teams. | | | | We use Backstage as our go-to platform for managing our internal tools and services. With Backstage, we can easily discover and access all the services we need to do our work, whether it's deploying code, managing infrastructure, or accessing documentation. We appreciate the standardized, consistent interface and the ability to easily create custom plugins to integrate with our existing workflows. Overall, Backstage is streamlining our internal operations and helps us work more efficiently as a

| | | | Internal developer portal with intent to unify infrastructure tooling, services, and developer documentation under a single, easy-to-use interface. | | | , , | Developer portal: documentation, service templates, org structure, service catalog, plugins for integration with internal systems. | | | , , | Internal platform that aims to reduce the teams' cognitive load through self-service, abstracting processes that are now part of the teams' daily lives, enabling a centralized management of documentation, catalog, metrics and knowledge. | | | | We are proud to be an adopter of Backstage. Our goal is to make our Backstage installation the go-to location for every developer. To achieve this, we developed a custom plugin to populate Backstage's catalog with information from our internal deployment tool. As a result, we now have full visibility of all Worten systems, components, APIs, messaging topics, and documentation. We also migrated the internal deployment tool's Web UI to Backstage. Currently, we are working on Backstage's Software Templates feature. | | | , | We use Backstage at Inventa to share knowledge between squads, in the form of technical documentation, API contracts, and service status/ownership info, fomenting a self-service and scalable engineering culture. We also developed a plugin that allows us to have a centralized view of all the engineering tools we have for each environment, making it easy to access each one of our tools and increasing productivity. | | | | The internal developer portal seeks to combine infrastructure tooling, services, and developer documentation into a single, user-friendly interface. By streamlining these components, the portal enhances productivity and simplifies the development process for the internal team. | | | | We are adopting backstage to use as our Internal Developer Portal. Our goal is to improve Developer Experience by reducing cognitive load through backstage as a single point for developer information, documentation, tools, software insights and developer metrics. To enable golden paths using the scaffolder and improve developer self service through automation of infrastructure provisioning and configuration. | | | | We're basing our internal developer hub we call Nucleus on Backstage. We're starting with the software catalog, then will gather feedback from our developers on what features they want next...integrations, templates, expanded catalog info, etc. | | | , , , | Internal developer and product portal implementation. | | | , , | At Rabobank, our mission is to make life better for engineers. After exploring various options in the market, we've discovered that Backstage provides the perfect foundation for creating a platform that meets our engineers' needs and helps us achieve our goals. We want to make our engineers happy by offering standardized services, freeing them up to focus on delivering value. Our vision is to create a one-stop platform where engineers can find everything related to software and services. In practice, we're excited about using all the cool features in Backstage, and we're even planning to build our own plugins. | | | | We use Backstage as a central place for all of our components/apis across multiple teams. It helps us to quickly identify the ownership of a component/api, find the related links and have a quick access to CI/CD pipelines. | | | , | Developer portal, services catalog and centralization of metrics from Grafana Stack and AWS. Furthermore, centralization of documentation and infra details like Tools, Network services and so on. | | | , | Backstage allow our developers to get easily engaged with all the internal components, technical documentations and software

All new developers reduce its onboarding time via Backstage, and after a couple of integrations it allowed us to create new components with in a couple of clicks. | | | , , | Backstage is our Internal developer portal. Along with other plugins, We use the software catalog, TechDocs and explore plugins to manage, discover and document our software components and platform products. | | | , , , | We're excited to announce our adoption of Backstage as our Internal Developer Portal! Our mission is to elevate the Developer Experience by streaming information access. Backstage will serve as the ultimate hub for developer resources, including documentation, tools, software insights, and metrics. Through Backstage, we're simplifying processes, offering software templates to empowered and efficient development journey, enhancing self-service capabilities with the embedded all best practices. | | | | We will be using it to be a corporate dashboard plus our software catalog. | | | | Internal Developer Portal, a catalog of all company resources, custom providers and processors, scaffolder for generating new resources. | | | We are building an internal developer portal to get an overview of all our software components. | | | | We are using as our Internal Developer Portal, it provides developers with the resources, information, and tools they need to build high-quality applications and adhere to organizational standards and security practices. | | | | At Giant Swarm we are using Backstage as our internal developer portal. Heavily using the service catalog and the TechDocs plugin. Further looking into adopting functionalities of our Web UI into Backstage to have a single pane of glass for our core business, managing all our components, and helping developers to be more productive. | | | | We are using Backstage as our main internal developer portal for our Programmers and Studio Partners. It's really proven its worth at our studio with on-boarding new programmers! | | | | At Anuclei, we are using Backstage as our internal portal for developers, providing all the tools and guidance needed for full-stack software projects. It simplifies our development methods, making innovation and investment in new ideas consistent and easy to repeat. | | | With Backstage we consolidate our internal tools into a single pane of glass and let the catalog drive our user interface. Our software templates onboard our services and teams onto Backstage, and with Techdocs we are letting our developers get back in control of their own documentation. | | | | Internal developer portal to consolidate all developers dashboards, company inventory with compliance reports, team management and self-service portal for IT/Team operations. | | | | Heavy usage of scaffolder, techdocs, homepage, k8s plugin and homegrown plugins to track migration paths and so on within a developer portal. It acts as a starting point for new and old developers to find all of our internal tooling in one place. | | |We are using Backstage as our internal developer portal to provide a single pane of glass for our developers to access all the tools and services they need to build and maintain our software. | | | , | We are using Backstage as a gateway into our internal development platform offering to simplify complexity. | | | | We are implementing backstage at Scania to consolidate operational information from Gitlab, Jira, Confluence, Artifactory, Servicenow and other tools into one place. | | | | We are using Backstage as a service catalog for our costumers. |