Roadie

Roadie supports native plugins for Backstage from Spotify, including those you develop yourself. But how? This video demonstrates how to create an example plugin from scratch, deploy it into Roadie, and add it to the interface. On top of the flexible Backstage plugin architecture, Roadie supports: 1. CLIs for developing, packaging and deploying custom plugins straight into the Roadie interface. 2. The ability to run multiple versions of a plugin simultaneously, so you can develop version 2 of your plugin while existing users continue to use version 1. 3. A scaffolder template for bootstrapping a custom plugins monorepo.

Here’s 4 areas we see AI being a win for internal developer portals… • 𝗚𝗲𝗻𝗲𝗿𝗮𝘁𝗶𝗻𝗴 𝘁𝗵𝗲 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗰𝗮𝘁𝗮𝗹𝗼𝗴. It’s clear that completing the catalog is a priority and a difficult task for many orgs. Can we analyze a GitHub repo and automatically collect metadata from it? • 𝗔𝗻𝘀𝘄𝗲𝗿𝗶𝗻𝗴 𝗾𝘂𝗲𝘀𝘁𝗶𝗼𝗻𝘀. The IDP is in a unique position because it’s connected to so many DevTools. Can we use this data to answer questions that require data from multiple tools. Something like “which production services have the longest MTTR?” • 𝗗𝗲𝗯𝘂𝗴𝗴𝗶𝗻𝗴. Software templates can sometimes produce obscure errors. Can we use AI to point the user to the correct solution? • 𝗦𝗰𝗼𝗿𝗶𝗻𝗴 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻. We see customers want to write checks like “Ensure all production software has a useful README”. This is difficult to do with programatic checks, but could be done by an AI that scores documentation. What else should we be thinking about as we build out AI capabilities in Roadie? #ai #backstage #devtools

Your engineering organization has it's own culture, terminology, tools and standards. It's incredibly important that this uniqueness is reflected in your Internal Developer Portal. It may be SaaS, but Roadie is heavily customizable so you can make it your own. Check out these 7 types of customization that Roadie supports. #developertools #backstage #softwareengineering

Ioannis Georgoulas and his team ran Backstage from Spotify for 3+ years before realizing they had to make a tough choice.... "Backstage in theory is good, but in practice it’s challenging. You need to have people following up, implementing, making sure it’s up to date" Over a short period, Ioannis and is team at Paddle migrated their Backstage implementation to Roadie. The migration happened quickly, and unlocked extra value. As Ioannis says... "Now we have the tools, we can think about bigger initiatives - how we manage and provision resources in general, how people deploy their code, further standardisation and improvements of the developer experience, lessening context switching. This is years of work." Want to learn what was involved? The full case study is linked in the top comment. #backstage #devtools #softwareengineering

Dynatrace have released their own officially supported plugin for Backstage from Spotify and it's already supported on Roadie. Here's what you get: 🔸 Kubernetes insights as default with context-rich deep linking 🔸 Multi-environment support 🔸 DQL-based approach to fetch any observability and security data 🔸 Table representation of query results Every Roadie customer gets a full Backstage stack under the hood, so it's easy for us to add new plugins, and you can even write your own if you like.

Here's a sneak peek at something the team is cooking up at Roadie 🤫 Expect big announcements on this soon....

Here's a simple but valuable example of how we continually listen to customer feedback and iterate at Roadie. Everything we do is enabled by the wonderful customers we work with.

During an audit, it's important to be able to quickly and easily export technical documentation so you can hand it over to people who are not users of your IDP. Today we added PDF printing of TechDocs to support this use case.