milliehartnt123
533bbe21fe
* Update architecture-overview.md Updated the architectural overview. Rewrote sections and created new graphics. Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Add files via upload Architectural diagram of the Backstage frontend and backend. Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Add files via upload Added new graphics to illustrate simplified standalone plugin architecture, service-based-plugin-architecture, and third-party-plugin architecture. Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Add files via upload Cleaned up graphic Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Cleaned up service-based plugin graphic Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Update architecture-overview.md Updated graphics and added note to plugin architecture graphics. Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Updated plugin-architecture heading links in architecture-overview.md Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Update architecture-overview.md fix formatting Fixed formatting that occurred during copy-paste. Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Update architecture-overview.md Rearranged some of the sections. Added additional text and links. Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Update architecture-overview.md fixed link for02-backends Fixed link to backend-system/architecture/02-backends.md. Forgot the "architecture" in the path. Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Update architecture-overview.md updated database section Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Update architecture-overview.md added links for core frontend plugins Added links and descriptions of the core frontend plugins. The links are back to the overview pages under features for each of the plugins Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Updated diagram to show Kubernetes as core plugin Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Updated graphics to remove the work Container Changed "Frontend Container" to "Frontend". Changed "Backend Container" to "Backend" Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Update architecture-overview.md Changed "Frontend Container" to "Frontend" everywhere in the doc. Changed "Backend Container" to "Backend" everywhere in the doc. Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Update architecture-overview.md fixed backend spelling errors Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Update architecture-overview.md try to fix prettier errors Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> * Update architecture-overview.md fix spelling error Changed backed to backend Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com> --------- Signed-off-by: milliehartnt123 <108491788+milliehartnt123@users.noreply.github.com>
Backstage
English | 한국어 | 中文版 | Français
What is Backstage?
Backstage is an open source framework for building developer portals. Powered by a centralized software catalog, Backstage restores order to your microservices and infrastructure and enables your product teams to ship high-quality code quickly without compromising autonomy.
Backstage unifies all your infrastructure tooling, services, and documentation to create a streamlined development environment from end to end.
Out of the box, Backstage includes:
- Backstage Software Catalog for managing all your software such as microservices, libraries, data pipelines, websites, and ML models
- Backstage Software Templates for quickly spinning up new projects and standardizing your tooling with your organization’s best practices
- Backstage TechDocs for making it easy to create, maintain, find, and use technical documentation, using a "docs like code" approach
- Plus, a growing ecosystem of open source plugins that further expand Backstage’s customizability and functionality
Backstage was created by Spotify but is now hosted by the Cloud Native Computing Foundation (CNCF) as an Incubation level project. For more information, see the announcement.
Project roadmap
For information about the detailed project roadmap including delivered milestones, see the Roadmap.
Getting Started
To start using Backstage, see the Getting Started documentation.
Documentation
The documentation of Backstage includes:
- Main documentation
- Software Catalog
- Architecture (Decisions)
- Designing for Backstage
- Storybook - UI components
Community
To engage with our community, you can use the following resources:
- Discord chatroom - Get support or discuss the project
- Contributing to Backstage - Start here if you want to contribute
- RFCs - Help shape the technical direction
- FAQ - Frequently Asked Questions
- Code of Conduct - This is how we roll
- Adopters - Companies already using Backstage
- Blog - Announcements and updates
- Newsletter - Subscribe to our email newsletter
- Backstage Community Sessions - Join monthly meetups and explore Backstage community
- Give us a star ⭐️ - If you are using Backstage or think it is an interesting project, we would love a star ❤️
Governance
See the GOVERNANCE.md document in the backstage/community repository.
License
Copyright 2020-2025 © The Backstage Authors. All rights reserved. The Linux Foundation has registered trademarks and uses trademarks. For a list of trademarks of The Linux Foundation, please see our Trademark Usage page: https://www.linuxfoundation.org/trademark-usage
Licensed under the Apache License, Version 2.0: http://www.apache.org/licenses/LICENSE-2.0
Security
Please report sensitive security issues using Spotify's bug-bounty program rather than GitHub.
For further details, see our complete security release process.