Encore

Why it's ranked here

What earns this a spot is not the provisioning pitch, which most infrastructure tools also make, but how plainly the project admits its own edges. It states outright that only TypeScript and Go are supported today, that a third language is still coming, and that automatic cloud provisioning reaches only two providers, with a third still on the roadmap. Alongside that honesty sit real exits: ordinary Go or TypeScript code underneath, a documented plain container build, and cloud resources that live in the team's own account instead of a vendor's. Named production users across fintech, logistics, and commerce back the claim that this runs real systems, not demos.

What's good

The strongest design choice is treating local development as a first-class target rather than an afterthought: running the app locally starts a real relational database and real message-queue semantics instead of stubs, so bugs tied to actual infrastructure behavior surface before code reaches a shared environment. Adoption is deliberately incremental: teams can wrap one service at a time, keep using whatever cloud SDKs or third-party APIs they already rely on, and the project documents a specific path for migrating a service back out again if the fit turns out to be wrong.

Tradeoffs

Committing to the full workflow means adopting more than the open source pieces: scheduled jobs run locally only when triggered by hand, and conveniences like preview environments, cost dashboards, and auto-generated architecture diagrams sit behind the optional managed platform rather than the SDK alone. Cloud coverage is narrow by the project's own admission, limited to two providers with a third still unbuilt, and the language surface is two mature options with a third still unreleased. Teams whose infrastructure needs fall outside the common set of databases, queues, storage, caches, jobs, and secrets are told plainly to keep wiring those up themselves.

How to use it well

This fits teams building new backend services in Go or TypeScript who want infrastructure decisions to live next to the code that uses them, especially ones already deploying into their own cloud account and tired of hand-wiring the same resources on every project. The natural entry point is a single new service, not a wholesale rewrite, since old and new systems can run side by side over ordinary APIs. It is the wrong fit if the target stack is outside its two supported languages, needs an unsupported cloud provider, or depends heavily on infrastructure outside its common-resource focus.

Observed

License

License is MPL-2.0, per the README badge.

Language support

Ships two officially supported infrastructure SDK languages, TypeScript and Go, with a third language explicitly marked as not yet available in the README's language table.

Interfaces

Interfaces span a CLI (the encore command), an open source infrastructure SDK usable as a library, an optional managed cloud platform, and an MCP server for agent introspection.

Repository structure

Repository is a polyglot monorepo: a Go module (go.mod) for the CLI and compiler plus a separate Rust workspace (Cargo.toml) for the core runtime, JS runtime, TypeScript parser, a supervisor process, and a Redis-compatible test double.

Self-hosting

A self-hosting path exists independent of the managed platform: a documented CLI command produces a standalone container image.

Cloud provider coverage

Automatic cloud provisioning is scoped to two providers per the README's stated limitations, with a third listed as roadmap-only.

CLI framework

CLI is built on the Cobra command framework, with subcommands registered via package-level blank imports.