Encore

Introducing Encore Cloud 2.0: The development platform for the AI era We believe infrastructure and operations need to keep pace with code generation. Over the past few years, 100+ engineering teams have adopted Encore in production and ship more efficiently because infrastructure isn't a bottleneck anymore. Databases, queues, IAM roles, networking, gateways, tracing - all automatic, in their AWS or GCP accounts, with production guardrails built in. Encore Cloud 2.0 takes this foundation further - with enhanced visibility, service catalogs, and MCP integration so both teams and AI agents have the context they need. Everything deploys as standard cloud resources in your cloud account with just a few lines of Encore code to declare what you need - without infrastructure lock-in. Read more in our announcement post below.

Introducing our AI backend benchmark - we tested how ready the top TypeScript frameworks are for AI agents. We ran the same agent across five frameworks to see which ones hand agents production-grade backends, and which leave the hard parts undone. Read the full benchmark → encore.dev/blog/ai-benchm…

@chirorojr OpenAPI spec generation is built in and it's automatically generated from your code.

@encoredotdev Does encore support OpenAPI or have a plugin of some sort for it? Looks like an interesting product.

Introducing the Database Explorer - now in the cloud. Browse your schema and run queries against your deployed databases right from the dashboard, with read or write access scoped to each environment. Give it a go → encore.dev

Temporal for durable workflows, Encore for the infrastructure around them, and it’s quietly becoming a default pairing for teams that need both. We wrote up how the two fit together with the @temporalio team. temporal.io/blog/why-teams…

By popular request, we put together an Encore vs Terraform comparison. tl;dr: same control, less boilerplate - Encore infers your infra from your code with production defaults you can override, instead of hand-writing HCL for every resource. encore.dev/comparison/ter…

Our customer stories got a fresh coat of paint. encore.dev/customers

You can copy any trace from the Encore dashboard and paste it into your AI agent to investigate and fix it. You can automate it too.

Cursor can now safely provision your cloud infrastructure. Ask a @cursor_ai agent for a feature and it writes the service, declares the infrastructure it needs in the code, and Encore provisions it into your own AWS or GCP without a line of Terraform. Your platform team sets the limits up front, so the agent only creates what they’ve allowed. Read more about it: encore.dev/blog/automatin…

What’s your favorite coding agent?

Every pull request comes with a preview environment, like a Vercel preview but running your entire backend and its infrastructure, so you (or your agents) can test the change end to end before it merges.

@illothy Not yet, but stay tuned 😎

@encoredotdev Is this on crates.io? I will use tf out of this, currently stuck with testcontainers which is great but makes ci take forever

We ported miniredis (an in-memory Redis) to Rust, ~25k lines, and put it inside our runtime, so local dev and tests get a real cache with zero infra. Here’s how we built it, and how we keep it byte-for-byte compatible with the reference by running its own test suite against our port. encore.dev/blog/redis-run…

We just published a case study on how @latermedia built a new AI matching engine on their own AWS with zero DevOps - using Encore as the infrastructure layer. Read the full case study: encore.dev/customers/later

You probably don’t need a dedicated vector database. The code below is all it takes on Encore to run semantic search on real Postgres with pgvector. Embeddings live next to your data and search is a SQL query. No need to run a separate vector database and a sync pipeline just to keep it in step with Postgres.

@Cloudflare More info: encore.dev/docs/platform/…

Provision a @Cloudflare R2 bucket directly from your backend code, into your own CF account. Your data and your bill stay between you and Cloudflare.

In case you missed it, we have a merch shop. The DevOps Hamster Wheel™ is sold out, but we’re giving away something else from it. We’re open source and we love rewarding people who build in the open, so drop a GitHub link and our favorite gets to pick anything from the store. shop.encore.dev

what’s the one piece of infra you wish you never had to set up by hand

if kubernetes was a person