Developer self-service,
without losing control

On most teams, adding a database or a queue means filing a ticket and waiting on the platform team. With Encore, developers declare what a feature needs in application code and get it provisioned automatically, while platform teams keep the cloud accounts, environments, and production approvals under their control.

Start building

See how it could work for your team.

Book a demo

Deploysproduction1v5dr0cb0mgc3je1e9k0

Retrigger

STATUSRunning

ENVIRONMENTproduction

STARTEDMay 25 at 16:06

DURATION1s

Build & testQueued

Provision infrastructure (1 change)Queued

Bucket ("receipts")Amazon S3 · versioning enabled

Pending

SQLDatabase ("orders")Amazon RDS · db.t4g.medium

Pending

Topic ("orders")SNS topic + SQS subscription

Pending

Provision logs6s

+2siam: created policy receipts-writer · least privilege

+4siam: granted s3:PutObject on receipts to orders

+6siam: no other service granted access

Deploy releaseQueued

Developers declare what their features need

Infrastructure is defined alongside the code that uses it. When a feature needs a queue, database, or bucket, the developer adds a declaration and keeps building, without updating Terraform, opening a provisioning ticket, or handing work off to the platform team.

Infrastructure primitives

todo/db.ts

import { SQLDatabase } from "encore.dev/storage/sqldb";

const db = new SQLDatabase("todo", {
  migrations: "./migrations",
});

Amazon RDS

Cloud SQL

Managed PostgreSQL with migrations, pooling and IAM auth

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

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

Code declares it, the platform configures it

Your code says which resources exist and how services use them. Everything environment-specific — instance sizing, connection limits, secret values, which cloud and region — is set in the platform, so the same code runs everywhere without a rebuild.

Infrastructure documentation

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.

Every PR gets its own preview environment

Every pull request gets its own environment with its own databases and queues, provisioned on merge-request and torn down when it closes. Developers stop sharing one contested staging environment.Nobody schedules time on staging, and nobody asks the platform team to reset it.