A NodeJS Backend for frontend.

Backend For Frontend

Standalone REST BFF (Backend-For-Frontend) that lets a trusted third-party UI call a Forest agent from a browser without learning MCP or JSON:API.

An OIDC client for masks: a session against a backend-for-frontend, or the code flow in the browser.

Simple Backend-For-Frontend server

Backend-for-Frontend for SPAs using Authagonal. Runs the OIDC auth-code + PKCE flow server-side, holds tokens in a server-side session, and exposes the browser only an httpOnly cookie. Express + Next.js adapters.

An isomorphic client for the catalog backend

Embed react-devtools within a website

Types and validators that help describe the model of a Backstage Catalog

A lightweight, NestJS-inspired BFF (Backend-for-Frontend) framework for Node.js

Server-side OIDC session for a NestJS backend-for-frontend: the browser holds one httpOnly cookie and never a Xema token. Performs the authorization-code exchange, keeps the token set in a session store the application owns, refreshes it under a lease so

Internal package for shared objects between the Studio backend and frontend

Common functionalities for the catalog plugin

A frontend library that helps other Backstage plugins interact with the catalog

Responsible for translating stack outputs and metadata (read via the [deployed-backend-client](../deployed-backend-client/README.md)) into client config that can be consumed by the Amplify frontend libraries.

Keymaster OIDC Backend-For-Frontend for Waukesha Makerspace services: discovery, PKCE, code exchange, id_token verification, and the signed session cookie. The SPA never sees a token.

Run several commands concurrently. Show output for one command at a time. Kill all at once.

Use react-devtools outside of the browser

Multi Backend system compatible with DnD Core / React DnD

A Backstage backend plugin that integrates towards Kubernetes