LLM.coPrivate, self-hosted LLM deployments
Legal AI infrastructure for firms
AI RFP discovery and response drafting
Automatic.coBusiness process automation
Secure AI virtual data roomsencore
Encore is an open-source infrastructure platform that lets developers declare cloud resources (databases, Pub/Sub, storage, caches) directly in TypeScript or Go code. It provides local development with real infrastructure semantics, per-PR preview environments, and automated provisioning to AWS or GCP.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | encoredev/encore |
| Owner | encoredev |
| Primary language | Go |
| License | MPL-2.0 — OSI-approved |
| Stars | 12.1k |
| Forks | 596 |
| Open issues | 114 |
| Latest release | v1.57.9 (2026-06-26) |
| Last updated | 2026-07-07 |
| Source | https://github.com/encoredev/encore |
What encore is
Encore comprises an MPL-2.0 SDK for TypeScript and Go that generates an application dependency graph and provisions local equivalents (Postgres, NSQ, Redis) via `encore run`, plus an optional managed platform that diffs and deploys to AWS/GCP Fargate/EKS or Cloud Run/GKE. It separates application semantics from environment configuration and supports incremental adoption alongside existing infrastructure.
Get the encore source
Clone the repository and explore it locally.
git clone https://github.com/encoredev/encore.gitcd encore# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Language commitment: TypeScript/Node.js or Go required; no polyglot per-service unless you use separate infrastructure tools.
- Resource graph coupling: Infrastructure is declared in application code; major refactoring of resource topology requires code changes, not just config tweaks.
- Local parity: `encore run` must support all declared resources; unsupported resource types fall back to manual integration.
- Team training: Developers must learn infrastructure-as-application-code model; not a drop-in replacement for existing Terraform/CDK teams.
- Migration scope: No rewrite required, but service-by-service adoption works best; full benefits realized when new services are Encore-native.
When to avoid it — and what to weigh
- Require Python or other languages — Currently TypeScript and Go only; Python listed as 'coming soon' but not available. Language lock-in applies if you need polyglot services.
- Heavy reliance on specialized/niche cloud services — Encore covers 99% use case (databases, Pub/Sub, storage, caches, cron, secrets). Domain-specific services require manual integration outside the SDK.
- Strict vendor lock-in requirements or air-gapped deployment — Designed for AWS/GCP; Azure on roadmap. Self-hosting via Docker possible but full Encore Cloud orchestration requires cloud connectivity.
- Existing terraform/CDK investment with no retraining budget — Encore replaces IaC pattern; switching from established Terraform/CDK workflows requires adopting declarative resource patterns in application code instead.
License & commercial use
MPL-2.0 (Mozilla Public License 2.0) is a weak copyleft license that permits commercial use, modification, and distribution. Derivative works of Encore itself must be licensed under MPL-2.0; proprietary application code using the SDK is not affected.
MPL-2.0 explicitly permits commercial use of the software. However, if you modify the Encore SDK or platform code itself, those modifications must be shared under MPL-2.0. Using Encore to build proprietary applications is permitted without restriction. Encore Cloud is a separate commercial offering; the open-source SDK can be used standalone.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Strong |
| Assessment confidence | High |
Encryption in transit/at-rest depends on underlying cloud provider (AWS RDS/EKS/S3, GCP Cloud SQL/GKE/GCS). Least-privilege IAM is generated from application code paths, reducing manual misconfiguration risk. Secrets managed via Encore vault (local), AWS Secrets Manager, or GCP Secret Manager. No third-party security audit data provided. Network isolation, RBAC, and audit logging inherit from AWS/GCP; review those controls for compliance requirements.
Alternatives to consider
Pulumi / AWS CDK
General-purpose IaC; requires separate application and infrastructure code; no built-in local equivalents. Steeper learning curve but more flexible for non-standard architectures.
Firebase / Supabase / Convex
Managed BaaS with built-in local emulators. Simpler for small teams but vendor-locked and less control over deployment. No multi-cloud option.
SST (Serverless Stack)
AWS-focused IaC with local testing. Lighter-weight than Encore but AWS-only; no GCP support or per-PR preview environment orchestration.
Build on encore with DEV.co software developers
Review the security posture, cloud provider integrations, and team training requirements specific to your environment. Pilot with a single new microservice before committing to broader adoption.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
encore FAQ
Can I use Encore with my existing Kubernetes cluster?
Do I have to use Encore Cloud, or can I use just the SDK?
What happens if I want to leave Encore later?
Does Encore support Python or other languages?
Software development & web development with DEV.co
Considering encore for production? DEV.co is a software development company that builds, integrates, and maintains open-source devops software — and takes ownership of the parts your team would rather not run.
Ready to evaluate Encore for your infrastructure stack?
Review the security posture, cloud provider integrations, and team training requirements specific to your environment. Pilot with a single new microservice before committing to broader adoption.