Ranked portals and platforms that provision and run your backend, with a clear line between catalog tools and deploy systems.

The best Backstage alternative depends on the problem. For a managed catalog and scorecards, pick Port, Cortex, OpsLevel or Roadie. For a system that provisions and runs backends in your own cloud, Encore ranks first, with Humanitec as the orchestrator over infrastructure you already operate. Backstage itself remains the open source portal framework when you have a platform team ready to build and own it.
This guide opens with a ranked table, separates portals from platforms that provision, covers each option accurately, and ends with when to pick which.
Portals surface a stack you already operate, while platforms provision and run it, and the Category column above marks which is which.
Two categories of Backstage alternative: developer portals that sit on top of existing infrastructure, and platforms that provision and run the backend themselves.
Spotify open-sourced Backstage in March 2020 and later moved it to the CNCF. It became the default answer for an internal developer portal. Backstage is a framework for building a portal, not a portal you turn on: you stand up Postgres, wire authentication, then install or write a plugin for every capability you want.
The Backstage getting started guide is explicit that the local install is not production-ready: production needs its own database, authentication setup, plugins and a deployment, someone has to own upgrades and plugin quality, and the portal sits on top of Terraform, Kubernetes and CI. That fits a large org that already has that toolchain. For a team that has not built the toolchain yet, a portal adds a layer without fixing deploy friction.
These compete with Backstage directly. They give you a catalog, scorecards and self-service workflows, usually as SaaS, and like Backstage they sit on infrastructure you already run.
Port makes Backstage's build-your-own idea configurable instead of code-driven. You define a data model of services, environments, resources and teams, connect integrations, and build scorecards and self-service actions in a UI. Setup is faster than a from-scratch Backstage, and you drop hosting and plugin upkeep. Self-service actions still trigger automations in GitHub Actions, Terraform or Argo CD underneath.
Cortex centers on engineering standards and service maturity. You define scorecards for runbooks, SLOs, approved languages and security scans. Cortex reports compliance and drives initiatives. Scope is narrower than Port or Backstage.
OpsLevel focuses on ownership and health. It maps ownership and dependencies, runs maturity scorecards, and can gate deployments on checks tied to CI. It organizes and measures services without managing infrastructure.
Roadie is managed Backstage. You get the same UI and plugin ecosystem without running hosting, upgrades or plugin compatibility. You stay inside the Backstage model, where the portal still sits on infrastructure you run elsewhere.
Encore is a code-first backend platform for TypeScript and Go. You declare infrastructure as typed objects in application code: Postgres, Pub/Sub, cron jobs, object storage and secrets. Encore provisions those resources into your own AWS or GCP account, deploys the services, and gives you environments, preview environments per pull request, tracing, a service catalog and an architecture diagram. Those views are generated from the code the platform already runs, instead of from a separate catalog project.
Encore is not a Backstage-style portal over an arbitrary existing stack: it runs the backend, and the catalog comes from that.
Simon Vans-Colina, CTO at Pave Bank, said on the customers page: "My challenge was to find a way to skip building a platform as good as Monzo's. The Encore platform fit that description perfectly." Pave Bank built a licensed bank on Encore and holds banking license No. 305 from the National Bank of Georgia.
import { api } from "encore.dev/api";
import { SQLDatabase } from "encore.dev/storage/sqldb";
import { Topic } from "encore.dev/pubsub";
import { CronJob } from "encore.dev/cron";
const db = new SQLDatabase("orders", { migrations: "./migrations" });
interface OrderPlaced {
orderId: string;
}
export const orderPlaced = new Topic<OrderPlaced>("order-placed", {
deliveryGuarantee: "at-least-once",
});
export const create = api(
{ method: "POST", path: "/orders", expose: true },
async (p: { total: number }): Promise<{ id: string }> => {
const row = await db.queryRow<{ id: string }>`
INSERT INTO orders (total) VALUES (${p.total})
RETURNING id::text AS id`;
await orderPlaced.publish({ orderId: row!.id });
return { id: row!.id };
},
);
export const cleanup = api({}, async () => {
await db.exec`
DELETE FROM orders
WHERE completed = true
AND created_at < NOW() - INTERVAL '30 days'`;
});
const _ = new CronJob("cleanup-orders", {
title: "Clean up old orders",
every: "24h",
endpoint: cleanup,
});
Run in your terminal to get started locally.
Encore works with NestJS and Express and runs on AWS and GCP, not Azure. Existing Terraform can stay for shared infra through the Terraform provider.
Humanitec is a platform orchestrator: you describe what an application needs in a workload spec, and Humanitec resolves that against environments and drives underlying infrastructure through tooling you already have. It targets platform teams that want to codify golden paths across teams. You bring and connect that infrastructure rather than replacing it.
The verdict: use a portal when you already run the stack and need a better view. Use Encore when you want the stack provisioned and deployed from application code, with the catalog as a byproduct.
If you need a managed developer portal, Port, Cortex, OpsLevel and Roadie are the closest alternatives. If the real goal is to provision and run backends without standing up a separate portal project, Encore ranks first among platforms that deploy into your own AWS or GCP account, with Humanitec as the orchestrator option over infrastructure you already operate.
Backstage is a framework for building a portal, not a finished product. Getting to production means configuring a database, authentication and plugins yourself, someone owns upgrades, and the portal still sits on top of Terraform, Kubernetes and CI you already run. Teams without Spotify-scale platform capacity often choose a SaaS portal or a platform that generates a catalog from the system that already deploys.
A portal catalogs services and offers self-service actions on infrastructure you already operate. Backstage, Port, Cortex, OpsLevel and Roadie sit there. A platform provisions and runs the backend, so the catalog comes from the deploy system. Orchestrators such as Humanitec drive existing infrastructure from a workload spec, and code-first platforms have the application declare infrastructure and provision it in your own cloud.
No. Backstage reads information from your tools and can trigger pipelines you already built. It does not provision infrastructure, run deployments or manage environments on its own.
Usually not at first. It assumes a mature toolchain and someone to operate the instance. Small teams that want visibility without that load tend to pick a SaaS portal or a platform that produces a catalog as a side effect of deploying.
Deploy to your cloud on AWS and Google Cloud
without managing infrastructure
Encore lets developers and agents define application infrastructure directly in code, then automatically provisions it from local development to production in your AWS or GCP account.