Surface Cloudsmith artifact data inside your Roadie developer portal
Roadie is a managed internal developer portal built on Backstage. The official Cloudsmith plugin for Roadie brings your artifact repository data directly into the portal your engineers already use every day, giving teams instant visibility into package stats, quota usage, audit logs, and security scan results without leaving the catalog.
How we support Roadie
Why teams integrate Cloudsmith with Roadie
Frequently asked questions
The plugin adds five cards to your Roadie homepage: repository stats, quota and usage, audit logs, security scan results, and a full package list. Each card pulls live data from your Cloudsmith repositories via a backend proxy, so the information is always current.
You provide a Cloudsmith API key as an environment variable on the Roadie backend. Roadie then uses a backend proxy to forward requests to the Cloudsmith API on behalf of the frontend cards. No credentials are ever exposed to the browser.
Yes. The Cloudsmith Backstage plugin is an official Roadie plugin, maintained by the Roadie team in the roadie-backstage-plugins repository and listed in the Roadie plugin catalog. It is available directly from Roadie without additional configuration beyond installing the package.
Yes. The plugin is distributed as the npm package @roadiehq/backstage-plugin-cloudsmith and works with both self-hosted Backstage instances and the managed Roadie platform. Installation steps differ slightly between the two, so follow the documentation that matches your setup.
You can connect any Cloudsmith repository by providing the owner name and repository slug when rendering each card. Multiple cards can point to different repositories on the same Roadie homepage, giving teams visibility across all the artifact stores their services rely on.
Yes. The CloudsmithRepositorySecurityCard displays packages with known vulnerabilities sourced from Cloudsmith's built-in security scanning. Teams see affected packages alongside their severity directly in the Roadie portal, enabling faster remediation without switching to the Cloudsmith UI.
All API calls are made server-side through the Backstage proxy. The Cloudsmith API key is injected as a request header on the backend, meaning it is never sent to or stored in the browser. You set the key once as an environment variable and the plugin handles the rest.
The CloudsmithQuotaCard in Roadie shows current bandwidth and storage usage alongside your plan limits. When consumption approaches the ceiling, the card makes it visible to any engineer looking at the homepage, giving your team time to act before a limit breach disrupts builds or deployments.
Cloudsmith supports over 30 package formats including Docker, Helm, npm, Maven, PyPI, NuGet, Debian, RPM, and more. Regardless of the language or runtime your services use, Cloudsmith can store and serve the artifacts they depend on, and the Roadie plugin gives you visibility across all of them.
The full setup guide is available at docs.cloudsmith.com under the Roadie integration page. It covers API key configuration, proxy setup, card installation, and how to wire cards to specific repositories. Roadie's own documentation at roadie.io also has a step-by-step guide for configuring the plugin on the managed platform.