Encore

Encore turns infrastructure into something you declare in application code. A database, a Pub/Sub topic or a storage bucket exists because you constructed the object in Go or TypeScript, which removes the standing gap between what the code expects and what the environment was manually given.

There are two parts. The open source infrastructure SDK covers databases, Pub/Sub, object storage, caches, cron jobs and secrets, and one run command starts the whole system locally with real Postgres, real Pub/Sub semantics and distributed tracing. The managed platform that orchestrates cloud infrastructure is optional, and you can provision with Terraform instead.

Each declaration becomes a node in an application graph that maps to concrete services per environment.

• SQL databases: Postgres locally, RDS on AWS, Cloud SQL on GCP.
• Pub/Sub: NSQ locally, SNS with SQS on AWS, Cloud Pub/Sub on GCP.
• Object storage: the local filesystem, S3, or Google Cloud Storage.
• Preview environments: an ephemeral environment per pull request, optionally with a branched database.
• Deploys: the graph is diffed against the environment, missing resources are provisioned, and IAM is scoped from the code paths.

Adoption does not require a rewrite. New services can run beside an existing system and integrate over APIs, and Encore deploys into a Kubernetes cluster or VPC you already have.

The limits are stated up front. Services must be TypeScript or Go, with Python still to come, and automated provisioning covers AWS and GCP only, though a Docker build works on any provider.