Ship at startup speed,
inside a large org.

Replace week-long infrastructure tickets with code that deploys itself. Groupon adopted Encore and cut project lead times by 90%.

Start building

See how it could work for your team.

orders3 environments
EnvironmentsSettings
Infrastructure ResourcesAmazon Web ServicesAWSprod-us-east-1 · us-east-1
1Fargate Service(3 services)
ECS Fargate ServiceAWS ComputeReady
AWSus-east-1
CONFIGURATIONEDIT
vCPUs2
Memory (MiB)4096
API GATEWAYS(1)
api-gateway
SERVICES(3)
1AWS RDS Instance(1 database)
4SNS Topics(3 subscriptions)
2S3 Buckets(versioning on)
0Unused Resources

Boring infrastructure, perfected.
So you can ship the interesting parts.

Standardize without slowing teams down

Every team provisions infrastructure the same way, inside guardrails the platform team sets once. Onboard engineers in a day.

Security and governance, automatic

Scoped service-to-service auth, encrypted secrets, and structured logs across every service. Pass review without screenshots.

Observability your platform team approves

Distributed tracing, structured logs, and request-level metrics in every service. No agents to deploy, no SDKs to wire up.

Platform teams control how infrastructure runs

Platform teams configure cloud accounts, regions, networking, scaling, resource sizes, and approval requirements for each environment. Developers can then provision what their features need within those controls, while security and production oversight remain centralized.

  • Configure scaling and resource sizes per environment
  • Control cloud accounts, regions, networking, and domains
  • Require approval for production infrastructure changes
  • Apply least-privilege IAM automatically
  • Trace every change back to its commit
In your code
Committed, reviewed, same everywhere
Which resources existnew SQLDatabase("orders")
How services use themqueries, publishes, reads
Migrations./migrations
In the platform
Set per environment, no redeploy
Instance sizingdb.t3.medium → db.m5.large
Connection limits500 → 1000
Secret valuesper environment type
Cloud + regionAWS us-east-1 / GCP eu-west1

Encore reads the first and applies the second — so nothing environment-specific ends up hardcoded.

Your cloud account, your compliance boundary

Encore provisions and operates the infrastructure inside your own AWS or GCP account. Your data never leaves it, and your team keeps full console access to every resource.

  • Workloads run in your cloud account
  • Least-privilege IAM applied automatically
  • Full console access to every resource
  • No proprietary runtime to migrate off
prod-us-east-1Prod environment
Settings
1AWS RDS Instance(1 database)
orders-prod-aws-rds-4f80bff
us-east-1
CONFIGURATIONEDIT
Instance classdb.t3.medium
Max connections500
Allocated storage20 GiB
Postgres version17.6
DATABASES(1)
orders
No pending changes
Audit trail

Everything enterprise teams need to ship

Encore automates the infrastructure, security, and observability groundwork normally cobbled together from eight different services and maintained by hand. One workflow, provisioned into your own cloud account.

Infrastructure from code

Databases, queues, buckets, and secrets declared in your code and provisioned automatically. No Terraform to write or maintain.

Least-privilege IAM

Per-service IAM policies generated from what the code actually accesses, updated as the application changes.

Secrets management

Encrypted, environment-scoped secrets, backed by AWS Secrets Manager or GCP Secret Manager in production.

Environments on demand

Preview environments per pull request, each with its own databases and queues, cleaned up on merge.

Distributed tracing

Every request, service call, and query traced and inspectable, locally and in production. Built in.

Your cloud, your data

Provisioned in your own AWS or GCP account, with full console access. Your data never leaves it.

Least-privilege access, without writing IAM

Encore knows which services touch each database, queue, bucket, and secret, and generates per-service IAM policies with only those permissions. Secrets are referenced by name and stay encrypted and environment-scoped, so credentials never enter the repository.

  • Per-service IAM generated from the code
  • Policies updated as the application changes
  • Encrypted, environment-scoped secrets
  • Every infrastructure change tied to a commit
Granted access0/20 cells
orders dbusers dbreceiptsorders topicstripe keyorderspaymentsusersnotify

Every other combination stays denied — you never write the policy.

“What used to take days or weeks of back-and-forth between developers and infra teams is now automated and completed in minutes.”
Josef Sima, Engineering Director at Groupon
2–3xfaster development speed
90%shorter time to market
// POWERING DEVELOPMENT AT
GrouponPave BankBookshop.orgCoinbasePalletGradient Labs

Move like a startup. Pass review like an enterprise.

30 minutes with an Encore engineer. We'll look at your service landscape and show you what changes.

Get started
brew install encoredev/tap/encore &&
encore app create
Copy

Run in your terminal to get started locally.