encoredev

encoredev/encore

Infrastructure orchestration from local to your cloud

View on GitHub Website / Demo Back to listing

12.7kstars 654forks 100+contributors Go

README.md

<a href="https://encore.dev"><img src="https://user-images.githubusercontent.com/78424526/214602214-52e0483a-b5fc-4d4c-b03e-0b7b23e012df.svg" width="160px" alt="encore icon"></img></a>
 
Encore: Infrastructure orchestration from local to your cloud

[![License](https://img.shields.io/badge/license-MPL--2.0-blue.svg)](LICENSE)
[![Discord](https://img.shields.io/discord/814482502336905216?label=discord)](https://encore.dev/discord)
[![Go SDK](https://img.shields.io/badge/go-encore.dev-00ADD8)](https://pkg.go.dev/encore.dev)
[![TS SDK](https://img.shields.io/npm/v/encore.dev?label=npm)](https://www.npmjs.com/package/encore.dev)

## What is Encore?

Encore helps developers and AI coding agents build and deploy backend applications without having to manually set up and manage infrastructure.

Encore combines an open source SDK, CLI, and cloud platform into one workflow for building and deploying apps.

Import what you need from the SDK directly into your application to define services and infrastructure. Run your app and infrastructure locally with the CLI to test changes end to end. Then push to your repo, and the platform sets up the matching resources in your cloud (AWS or Google Cloud) and deploys your app.

You can also use the SDK on its own for local development, and manage production infrastructure yourself using Terraform or other tools.

### Example: Declaring resources using the SDK

```typescript
import { SQLDatabase } from "encore.dev/storage/sqldb";
import { Topic } from "encore.dev/pubsub";
import { Bucket } from "encore.dev/storage/objects";

// Define a Postgres database
const db = new SQLDatabase("users", { migrations: "./migrations" });
// Define a Pub/Sub topic
const signups = new Topic<SignupEvent>("signups", {
 deliveryGuarantee: "at-least-once"
});
// Define an object storage bucket
const avatars = new Bucket("avatars", { versioned: true });
```

Each declaration becomes a node in Encore's application graph. Encore runs the migrations and stands up local equivalents on `encore run`, and provisions the cloud equivalents on deploy:

| Resource       | Local              | AWS             | Google Cloud             |
| -------------- | ------------------ | --------------- | --------------- |
| SQL Database   | Postgres           | RDS             | Cloud SQL       |
| Pub/Sub        | NSQ                | SNS + SQS       | Cloud Pub/Sub   |
| Object Storage | Local FS           | S3              | GCS             |
| Cache          | Redis              | ElastiCache     | Memorystore     |
| Cron           | Manually triggered | Encore Cloud    | Encore Cloud    |
| Secrets        | Encore vault       | Secrets Manager | Secret Manager  |
| Compute        | Local              | Fargate / EKS   | Cloud Run / GKE |

When you push a change that adds or modifies a resource, Encore diffs the application graph against the environment, provisions whatever is missing in your AWS or Google Cloud account, and rolls out the new code against it.

### Configuration

Encore separates application semantics from environment-specific configuration. In code, you define what resources your app needs, not how each environment should configure them.
That keeps services portable across clouds, regions, accounts, scale profiles, and local development.

Encore provisions every resource with sane production defaults, then helps you manage configuration separately from your application code:

- **Encore platform dashboard:** easy to use knobs for all common settings like process allocation, instance sizes, replicas, etc. [See more in docs](https://encore.dev/docs/platform/infrastructure/configuration).
- **Your AWS or GCP console:** tweak anything directly in your cloud provider console. Encore picks up the changes on the next deploy.
- **IaC:** manage config for Encore-provisioned resources alongside the rest of your infrastructure via the [Terraform provider](https://encore.dev/docs/platform/integrations/terraform).

### Language SDKs

| Language   | Docs                                             |
| ---------- | ------------------------------------------------ |
| TypeScript | [encore.dev/docs/ts](https://encore.dev/docs/ts) |
| Go         | [encore.dev/docs/go](https://encore.dev/docs/go) |
| Python     | Coming soon. [Sign up for early access](https://encore.dev/py)                                      |
| Rust       | Coming soon. [Sign up for early access](https://encore.dev/rs)                                      |

## The Development Workflow

The same infrastructure model runs locally, in per-PR preview environments, and in production:

1. **Local:** `encore run` starts the whole system locally: real Postgres, real Pub/Sub semantics, type-safe service-to-service calls, plus a local dashboard with distributed tracing. [Infrastructure namespaces](https://encore.dev/docs/ts/cli/infra-namespaces) let multiple branches or agents work in parallel with isolated state. This lets you validate changes with real infrastructure semantics before pushing code.
2. **Per-PR preview environments:** Open a pull request and Encore sets up an ephemeral environment and (optionally) [branches databases from a seed environment](https://encore.dev/docs/platform/infrastructure/neon). This Lets you do end-to-end validation against before merging to a shared staging environment.
4. **Production:** Push to deploy. Encore diffs the application graph against the environment, provisions what is missing in your AWS or GCP account, wires up least-privilege IAM based on the application's code paths, and rolls out the new code.

With this workflow, the fail-loop moves from "push, wait, fix" to "run locally, see it work, push." This tight loop makes Encore particularly effective with AI coding agents, since every change can be validated with real infrastructure immediately after each code change. See the [Development Workflow](https://encore.dev/docs/platform/workflow) docs for more.

## Adopting Encore

You don't need a rewrite, and you don't need to use Encore for every part of your system.

- **Use any infrastructure as normal:** Encore doesn't try to own every resource. Import the AWS SDK, GCP client libraries, or any third-party API and provision the resource yourself, or wire it up alongside Encore-managed resources via the [Terraform provider](https://encore.dev/docs/platform/integrations/terraform).
- **Migrate service-by-service:** Build new services in Encore and run them next to your existing system, integrated over APIs.
- **Deploy where your stack already lives:** Encore can deploy into your existing Kubernetes cluster or into your VPC in AWS or GCP.

Start with a low-risk, frequently-changed service. See the [migration guide](https://encore.dev/docs/platform/migration/migrate-to-encore) for the full playbook.

### Migrating Away

Encore is designed to make leaving easy. 99% of your code is regular Go or TypeScript, so there's not much to rewrite.
See the [migrate-away guide](https://encore.dev/docs/ts/migration/migrate-away) for more.

## Limitations

Encore integrates at the application layer, which means a few constraints to be clear about up front:

- **Language:** Your services need to be written in a supported language in order to use the infrastructure SDK. TypeScript (Node.js) and Go is currently supported, and Python is coming soon.
- **Infrastructure scope:** Encore is designed to solve the 99% use case, making it easier to work with the resources you use over and over again; services, databases, Pub/Sub, object storage, caches, cron jobs, and secrets. For the remaining 1% that is specific to your domain, you can still integrate any other service as you normally would. Encore doesn't prevent it or make it harder.
- **Cloud providers:** Encore's fully-automated provisioning currently supports AWS and GCP. Azure is on the roadmap. Self-hosting via `encore build docker` works on any provider.

## How Encore Compares

| Tool                                   | What it does                                            | How Encore differs                                                                                                                         |
| -------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Pulumi / CDK / Terraform / SST**     | Infrastructure-as-Code for provisioning cloud resources | Infrastructure is generated from your application code, so the same code runs locally and deploys to AWS or GCP. |
| **Convex / Supabase / Firebase**       | Managed backend-as-a-service platforms                  | Runs in your own AWS or GCP account. No vendor lock-in.                                                                                    |
| **Render / Fly.io / Railway / Vercel** | PaaS-style deployment platforms                         | Deploys to your own cloud account, not a managed runtime.                                                                                  |

## Quick Start

```bash
encore app create     # scaffold a project
cd myapp
encore run            # run locally with provisioned infra + dev dashboard
```

Install Encore:

- **macOS:** `brew install encoredev/tap/encore`
- **Linux:** `curl -L https://encore.dev/install.sh | bash`
- **Windows:** `iwr https://encore.dev/install.ps1 | iex`

Full walkthrough in the [Quickstart guide](https://encore.dev/docs/ts/quick-start).

## AI Integration

Encore is built for AI-assisted development. When you run `encore app create`, you can pick your AI tool (Cursor, Claude Code, etc.) and Encore generates the right rules files for it, plus configures an [MCP server](https://encore.dev/docs/ts/cli/mcp) that lets agents introspect your app: services, APIs, databases, traces. Combined with the fast local-to-preview-env iteration loop above, agents can validate their own changes end-to-end against real infrastructure instead of guessing.

See the [AI integration docs](https://encore.dev/docs/ts/ai-integration) for more details.

## Local Dev Dashboard

The Encore CLI ships a local dashboard for inspecting services, APIs, traces, databases, Pub/Sub messages, and architecture diagrams in real time. Run `encore run` and it is there at `localhost:9400`.

https://github.com/user-attachments/assets/461b902f-8fd3-46f1-a73c-0ebbfa789ce3

## Deployment Platform

Encore's optional [managed platform](https://encore.dev/docs/platform) connects to your AWS or GCP account and provisions the resources your code declares in your own VPC. Other features:

- Preview environments for each PR
- Self-serve infrastructure provisioning, with least-privilege IAM and firewall rules derived from real code paths
- Distributed tracing, metrics, and logs across services
- Cost analytics and infrastructure approval workflows
- Auto-generated service catalog and architecture diagrams from your code

See [pricing](https://encore.dev/pricing) for details.

You can also skip the platform entirely. Run `encore build docker` to produce a standalone image and supply your own infra config (provisioned via Terraform, Pulumi, or any other tool). See the [self-hosting guide](https://encore.dev/docs/ts/self-host/build).

## Who's Using Encore

200+ Teams are already shipping production apps with Encore, including: Groupon, Echo.xyz (a Coinbase company), Bookshop.org, Gradient Labs, Ashby, Later.com, Pallet, Pave Bank, and Playwire.
Use cases span AI, fintech, logistics, commerce, web3, and more. See [case studies](https://encore.dev/customers) to learn more.

## Resources

- [Encore website](https://encore.dev)
- [Documentation](https://encore.dev/docs)
- [Migration guide](https://encore.dev/docs/platform/migration/migrate-to-encore)
- [Example apps](https://github.com/encoredev/examples/)
- [Discord](https://encore.dev/discord)
- [Book a 1:1 demo](https://encore.dev/book)
- [Public Roadmap](https://encore.dev/roadmap)
- [Contributing](CONTRIBUTING.md)

## License

Encore is licensed under the [Mozilla Public License 2.0](LICENSE).

The framework, parser, compiler, runtime, CLI, and everything needed to develop, build, and self-host an Encore application is Open Source. Encore's optional managed deployment platform is a commercial service.

See [CONTRIBUTING.md](CONTRIBUTING.md) for additional details.

Repository info

Default branch: main
Latest version: v1.58.8
Created: 17/02/2021
Last activity: 06/11/2026
License: MPL-2.0
Open issues: 149
Watchers: 65

Topics

aws backend cloud cloud-native database devops devops-automation distributed-systems encore gcp go golang infrastructure-as-code infrastructure-automation microservices serverless typescript

Contributors

eandre

929 contributions

fredr

329 contributions

marcuskohlberg

274 contributions

ekerfelt

225 contributions

DomBlack

148 contributions