# Encore Updates Encore automates infrastructure from development to production, so developers and agents ship without waiting on Terraform PRs or platform tickets. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Introducing Encore x E2B DevFeed: [Introducing Encore x E2B]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-09-15T00:00:00Z Content type: release Language: en Sources: [Encore Updates]() Topics: [AI-assisted coding](), [Cloud](), [backends](), [SDKs](), [Databases](), [Deployment](), [API](), [Code]() Tags: [agents](), [api](), [backend](), [cloud](), [code](), [coding](), [coding-agents](), [database](), [deployment](), [pull-request](), [sandbox](), [sdk]() ### AI overview Encore and E2B can provide coding agents with isolated sandboxes containing complete local backends. The integration lets agents build and verify end-to-end changes against infrastructure such as databases, queues, and APIs, while supporting deployment in the user's AWS or GCP account. ### Source excerpt Give coding agents an isolated sandbox with a complete backend inside it -- and keep both in your own cloud. ## Encore for Python DevFeed: [Encore for Python]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-09-14T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Python](), [FastAPI](), [AWS IAM](), [Amazon Web Services](), [Cloud](), [PostgreSQL](), [Terraform](), [postgresql clusters]() Tags: [aws](), [cloud](), [coding-agents](), [configuration](), [git](), [iam](), [infrastructure](), [postgresql](), [python](), [terraform]() ### AI overview Encore is introducing Encore.py, an upcoming beta that brings Encore's type-safe infrastructure primitives to Python and works alongside frameworks such as FastAPI. The article describes how application-level resource declarations can drive infrastructure provisioning while platform teams retain control over environment-specific settings in AWS, GCP, Terraform, or existing infrastructure. It also highlights preview environments where coding agents can implement and verify features against infrastructure configured to resemble production. ### Source excerpt An early look at Encore for Python, entering beta soon. ## Introducing Encore x Daytona DevFeed: [Introducing Encore x Daytona]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-09-08T00:00:00Z Content type: release Language: en Sources: [Encore Updates]() Topics: [AI-assisted coding](), [coding](), [Cloud]() Tags: [agents](), [coding-agents](), [infrastructure](), [sandbox](), [tests](), [tools]() ### AI overview Encore and Daytona provide coding agents with isolated, persistent sandboxes for building and verifying complete backends against local infrastructure that mirrors production declarations. ### Source excerpt Let your coding agents build and verify against real infrastructure, inside a sandbox. ## Nuxt co-creator Alexandre Chopin joins Encore DevFeed: [Nuxt co-creator Alexandre Chopin joins Encore]() Original publisher: [Read original article]() Author: Marcus Kohlberg Published: 2026-09-07T00:00:00Z Content type: news Language: en Sources: [Encore Updates]() Topics: [Provisioning](), [Cloud](), [Vue.js](), [Command-line interface](), [GitHub](), [Open Source](), [SDKs](), [AI-assisted coding]() Tags: [agentic-development](), [ai-agents](), [cli](), [developer](), [developer-relations](), [github](), [infrastructure](), [open-source](), [provisioning](), [sdk](), [teams](), [vue]() ### AI overview Encore announces that Alexandre Chopin, co-creator of Nuxt, has joined the company as Head of Developer Relations. He will work with developers and engineering teams and help shape Encore's roadmap around automated infrastructure. ### Source excerpt Alexandre joins as Head of Developer Relations to help bring automated infrastructure to more developers and teams. ## Encore now works with Entire DevFeed: [Encore now works with Entire]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-09-02T00:00:00Z Content type: tutorial Language: en Sources: [Encore Updates]() Topics: [AI-assisted coding](), [codex](), [Claude Code](), [coding](), [Git](), [cursor](), [PostgreSQL]() Tags: [claude-code](), [codex](), [coding](), [coding-agents](), [cursor](), [git](), [object-storage](), [postgresql]() ### AI overview Encore now works with Entire, allowing developers to use Codex, Claude Code, Gemini, and Cursor in Encore projects while recording agent sessions in Git and linking them to commits. The article demonstrates building and testing an image service with local PostgreSQL and object storage, including integration tests and a live upload/download verification. ### Source excerpt Keep the agent session behind every Encore change, directly in Git. ## We rebuilt the Linux microVM stack on Apple Silicon DevFeed: [We rebuilt the Linux microVM stack on Apple Silicon]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-08-18T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Firecracker](), [virtualization](), [macOS](), [Linux](), [Dockerfile](), [Go Language]() Tags: [docker](), [firecracker](), [go](), [linux](), [macos](), [virtualization]() ### AI overview Encore rebuilt its Linux microVM development stack to work on Apple Silicon. The article describes crackling, an API that uses Firecracker on Linux and Apple's hypervisor on macOS, along with the tooling needed to run the same build system on developer laptops and in production. ### Source excerpt Maybe we should have just moved everyone to Linux. ## Your SQS consumer can hang forever by default DevFeed: [Your SQS consumer can hang forever by default]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-07-28T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Amazon Simple Queue Service (SQS)](), [SDK](), [Rust](), [Amazon Web Services]() Tags: [aws](), [health-check](), [queue](), [retry](), [rust](), [sdk](), [sqs](), [tcp](), [timeout]() ### AI overview The article explains that the AWS Rust SDK has no request timeout by default. A failed or silently dropped connection can leave an SQS receive waiting indefinitely, stopping a sequential consumer loop while the process and health check still appear healthy. It describes fixing the issue with a per-attempt timeout. ### Source excerpt The AWS Rust SDK ships no request timeout by default, so one SQS receive on a dead connection can hang a whole consumer with nothing in the logs. ## Sandboxing an agent's code isn't the same as trusting it DevFeed: [Sandboxing an agent's code isn't the same as trusting it]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-07-21T00:00:00Z Content type: opinion Language: en Sources: [Encore Updates]() Topics: [AI Agent](), [Back end](), [Code](), [API](), [Database]() Tags: [agent](), [ai-agent](), [api](), [backend](), [code](), [database]() ### AI overview The article explains that sandboxing AI-generated backend code provides containment but does not establish correctness. It presents a verification loop using stronger feedback, typed interfaces, infrastructure declared in code, and execution before production. ### Source excerpt A sandbox keeps an agent's code contained. It can't tell you the code is correct, which for backend code is the harder problem. ## We compiled our TypeScript parser to WASM DevFeed: [We compiled our TypeScript parser to WASM]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-07-15T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Parser](), [Rust](), [wasm](), [browser](), [TypeScript]() Tags: [browser](), [parsing](), [rust](), [typescript](), [wasm]() ### AI overview Encore describes compiling its Rust parser for TypeScript infrastructure declarations to WebAssembly so it can run in the browser. The browser-based parser supports reproducing parser errors from code snippets and shared links, and powers the tsparser.encore.dev playground. ### Source excerpt How we compiled the Rust parser that reads infrastructure out of Encore code so it runs in the browser, and how we use it to reproduce the parser errors people report. ## Automating cloud infrastructure with Cursor DevFeed: [Automating cloud infrastructure with Cursor]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-07-07T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [cursor](), [cloud-infrastructure](), [Code](), [Cloud](), [IAM](), [Amazon Web Services](), [Google Cloud Platform (GCP)]() Tags: [aws](), [cloud](), [code](), [cursor](), [database](), [gcp](), [github](), [iam](), [infrastructure](), [open-source](), [postgres](), [typescript]() ### AI overview Encore describes how Cursor can provision cloud infrastructure declared alongside application code, allowing teams to deploy services to their own AWS or GCP accounts while retaining platform-team controls and review. ### Source excerpt Now a Cursor agent can provision your cloud infrastructure from the same code it writes, on your own AWS or GCP. ## We put a Redis server inside our runtime DevFeed: [We put a Redis server inside our runtime]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-06-25T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Redis](), [Rust](), [Development](), [Cache]() Tags: [cache](), [development](), [protocol](), [redis](), [rust](), [scripting](), [streams](), [transactions]() ### AI overview Encore describes how its runtime provides an in-memory Redis server for local development and tests, aiming to keep behavior consistent with Redis in production. The Rust runtime embeds a port of miniredis as a library that supports commonly used Redis data types, streams, pub/sub, transactions, Lua scripting, TCP, and the Redis wire protocol. ### Source excerpt How we run an in-memory Redis inside the runtime for local development and tests, and how we keep it behaving the same as the Redis you run in production. ## Why infrastructure changes still take a week DevFeed: [Why infrastructure changes still take a week]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-06-10T00:00:00Z Content type: opinion Language: en Sources: [Encore Updates]() Topics: [Terraform](), [Security](), [Architecture & Design]() Tags: [iam](), [infrastructure](), [security](), [terraform](), [vpc]() ### AI overview The article examines why infrastructure changes often wait days or weeks for review while application code ships faster. It attributes the queue to a small reviewer pool, the high blast radius of infrastructure mistakes, and limited verification before Terraform changes are merged. It also discusses how AI coding tools have affected the queue and how teams can remove the bottleneck. ### Source excerpt Application code ships in hours and the infrastructure it needs waits days for review. Where the queue comes from, what AI coding tools did to it, and how teams remove it. ## Why Type Errors Are Valuable Feedback for AI Coding Agents DevFeed: [Why Type Errors Are Valuable Feedback for AI Coding Agents]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-06-03T00:00:00Z Content type: opinion Language: en Sources: [Encore Updates]() Topics: [ai-coding](), [Code](), [coding](), [Back end]() Tags: [agents](), [ai](), [ai-agents](), [ai-coding](), [backend](), [errors](), [quality]() ### AI overview The article argues that AI coding agents depend heavily on the feedback available during their work loop. Compile-time type errors are especially useful because they are fast, deterministic, and localized, while many backend mistakes appear later or produce no signal the agent can act on. ### Source excerpt An agent only fixes what it can see before it stops, and a compile error is the one signal that always lands in time. ## Are TypeScript backend frameworks ready for AI agents? DevFeed: [Are TypeScript backend frameworks ready for AI agents?]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-05-20T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Benchmark](), [TypeScript](), [Claude Code](), [backends](), [Express](), [Fastify](), [Nest]() Tags: [ai-coding](), [backends](), [benchmark](), [claude-code](), [express](), [other](), [typescript]() ### AI overview The article reports a three-run benchmark of Claude Code building TypeScript backends with Encore, Express, Fastify, Hono, and NestJS. Although all frameworks passed the first-run tests, only Encore's output met the authors' production-readiness rubric at that stage. ### Source excerpt We set out to run one benchmark across five TypeScript backend frameworks. Reading the diffs sent us into two more runs, and the picture changed each time. ## What is distributed tracing? DevFeed: [What is distributed tracing?]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-05-04T00:00:00Z Content type: tutorial Language: en Sources: [Encore Updates]() Topics: [tracing](), [Back end](), [debug](), [telemetry]() Tags: [auth](), [database](), [debugging](), [dependency](), [distributed](), [guide](), [instrumentation](), [latency](), [tracing]() ### AI overview An interactive guide explains how distributed traces help debug backend issues by showing request operations, timings, dependencies, database queries, asynchronous message paths, and user-specific failures. ### Source excerpt An interactive guide to debugging real backend issues ## Sentry + Encore DevFeed: [Sentry + Encore]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-04-29T00:00:00Z Content type: tutorial Language: en Sources: [Encore Updates]() Topics: [error tracking](), [Back end](), [SDKs](), [Secrets Management]() Tags: [backend](), [error-tracking](), [sdk](), [secrets-management](), [sentry](), [tutorial]() ### AI overview A tutorial showing how to integrate Sentry error tracking into an Encore.ts backend. It covers installing and initializing the SDK, using a reusable error-handling wrapper, adding breadcrumbs, and verifying captured errors with a test endpoint. ### Source excerpt Error tracking for your backend services ## Building Durable Order-Processing Workflows with Temporal and Encore DevFeed: [Building Durable Order-Processing Workflows with Temporal and Encore]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-04-29T00:00:00Z Content type: tutorial Language: en Sources: [Encore Updates]() Topics: [Tutorial](), [Development](), [Back end](), [API](), [V8](), [Database](), [Terminal]() Tags: [api](), [backend](), [cloud](), [code](), [database](), [development](), [http](), [packages](), [terminal](), [tutorial](), [v8]() ### AI overview This tutorial builds an order-processing backend with Temporal and Encore. It demonstrates durable workflow execution across inventory checks, payment, shipping, and confirmation, including retries, crash recovery, and compensation when a step fails. ### Source excerpt Durable workflows with automatic infrastructure ## An Interactive Study of Publish/Subscribe Messaging for Event-Driven Backend Systems DevFeed: [An Interactive Study of Publish/Subscribe Messaging for Event-Driven Backend Systems]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-04-24T00:00:00Z Content type: tutorial Language: en Sources: [Encore Updates]() Topics: [Publish-subscribe pattern](), [Messaging](), [Back end](), [distributed-systems](), [event driven]() Tags: [decoupling](), [developers](), [distributed-systems](), [event-driven](), [events](), [flow](), [messaging](), [patterns](), [publisher](), [subscriber]() ### AI overview An interactive tutorial explains publish/subscribe messaging by contrasting it with direct service calls. It shows how topics decouple publishers from subscribers, support fan-out, and let subscribers process messages independently, including when downstream services are unavailable. ### Source excerpt An interactive study of publish/subscribe messaging ## What We Learned Building a Rust Runtime for TypeScript DevFeed: [What We Learned Building a Rust Runtime for TypeScript]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-04-08T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Rust](), [TypeScript](), [Tokio](), [tracing](), [Pingora]() Tags: [building](), [ipc](), [latency](), [performance](), [pingora](), [rust](), [tokio](), [tracing](), [typescript]() ### AI overview Encore describes building a Rust runtime for TypeScript applications. The runtime moves infrastructure work such as HTTP handling, database connectivity, pub/sub, tracing, metrics, storage, caching, and API gateway functions into Rust running on Tokio, while TypeScript handles application business logic. The article also explains why an IPC-based Go sidecar prototype introduced measurable latency overhead. ### Source excerpt 67,000 lines of Rust, two years, and the non-obvious problems of making Node.js and Rust work together in the same process. ## Build an Authenticated Backend with Ory Network, Encore, and PostgreSQL DevFeed: [Build an Authenticated Backend with Ory Network, Encore, and PostgreSQL]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-03-25T00:00:00Z Content type: tutorial Language: en Sources: [Encore Updates]() Topics: [Authentication](), [Back end](), [Open Source](), [Secrets Management](), [PostgreSQL](), [API](), [SDKs]() Tags: [api](), [authentication](), [backend](), [open-source](), [postgresql](), [sdk](), [secrets-management](), [tutorial]() ### AI overview This tutorial shows how to build a backend with Ory Network for user authentication and Encore-managed infrastructure. It covers session verification, protected API endpoints, authenticated user context, secret management, and PostgreSQL data storage. ### Source excerpt Open-source identity with automatic infrastructure ## How AI Agents' Infrastructure Access Affects AWS Risk and Development Speed DevFeed: [How AI Agents' Infrastructure Access Affects AWS Risk and Development Speed]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-03-25T00:00:00Z Content type: opinion Language: en Sources: [Encore Updates]() Topics: [AI Agent](), [Terraform](), [Amazon Web Services](), [AWS IAM]() Tags: [ai](), [ai-agent](), [ai-agents](), [aws](), [security](), [terraform]() ### AI overview The article examines the trade-offs between keeping AI agents away from infrastructure and allowing them to generate Terraform and configure AWS resources. It argues that direct infrastructure access can speed development but increases the security and operational consequences of agent-generated changes. ### Source excerpt The interface you give AI agents determines what they can break. ## Encore, MCP, and AI agents DevFeed: [Encore, MCP, and AI agents]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-03-19T00:00:00Z Content type: tutorial Language: en Sources: [Encore Updates]() Topics: [Model Context Protocol](), [MCP Server](), [Artificial Intelligence](), [Databases](), [Traces]() Tags: [agents](), [ai](), [database](), [mcp](), [mcp-server](), [trace]() ### AI overview The article explains how Encore's MCP server gives AI coding tools structured access to a running application's schemas, service graph, traces, pub/sub topology, cache configuration, infrastructure, documentation, and testing information. It describes how this context can help agents understand existing backend structure and reduce guesswork when implementing or verifying changes. ### Source excerpt How to give your agent full context over your running application. ## What is Infrastructure from Code? DevFeed: [What is Infrastructure from Code?]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-03-17T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Code](), [Cloud](), [Artificial Intelligence](), [Terraform](), [Databases](), [AWS IAM](), [Caching](), [Amazon Simple Queue Service (SQS)]() Tags: [ai](), [ai-agents](), [aws](), [caching](), [cloud](), [code](), [database](), [infrastructure](), [least-privilege](), [message-queue](), [terraform]() ### AI overview The article explains Infrastructure from Code (IFC), an approach that declares infrastructure such as databases, queues, and scheduled jobs in application code. It describes how frameworks derive cloud resources from those declarations and argues that AI-generated application changes have increased the need to keep infrastructure synchronized. ### Source excerpt How it works, why AI made it urgent, and what the trade-offs are. ## Type-Safe Caching in Encore.ts DevFeed: [Type-Safe Caching in Encore.ts]() Original publisher: [Read original article]() Author: Ivan Cernja Published: 2026-03-11T00:00:00Z Content type: article Language: en Sources: [Encore Updates]() Topics: [Caching](), [Cache](), [TypeScript](), [Redis](), [backends]() Tags: [backend](), [cache](), [caching](), [code](), [development](), [redis](), [typescript]() ### AI overview This article explains how string-based Redis caching in TypeScript can lose type safety and allow stale, colliding, or mismatched values. It presents Encore.ts v1.55's typed keyspaces, which preserve value and key constraints through to Redis and catch certain errors at compile time. ### Source excerpt What goes wrong with stringly-typed Redis, and what changes when the cache boundary is typed. [Next page]()