Encore

Most teams think the tradeoff is speed vs. quality. In practice, the real tradeoff is often different: Speed now vs. slow later. This story on how Echo went from zero → $375M Coinbase acquisition, in under two years, is a great example of how a strong team managed that trade-off very well. I'm super proud to have followed along as they've built their entire backend on Encore Cloud from day one. Staying productive as things scaled, without drowning in infra glue and “platform debt”. If you’re building microservices on AWS/GCP, this one’s worth a read 👇 https://lnkd.in/dWyFEZjG

Most teams think the tradeoff is speed vs. quality. In practice, the real tradeoff is often different: Speed now vs. slow later. This story on how Echo went from zero → $375M Coinbase acquisition, in under two years, is a great example of how a strong team managed that trade-off very well. I'm super proud to have followed along as they've built their entire backend on Encore Cloud from day one. Staying productive as things scaled, without drowning in infra glue and “platform debt”. If you’re building microservices on AWS/GCP, this one’s worth a read 👇 https://lnkd.in/dWyFEZjG

Encore provisions cloud infrastructure from your TypeScript/Go code. Declare a database, it creates RDS in your AWS account or Cloud SQL in GCP. The instance runs in your account with networking and IAM configured. "But I need control over the configuration." You get it. Encore sets production-grade defaults, but you can customize instance sizes, regions, networking. You have full AWS console access to everything it creates. "What about AI coding tools?" They work great with this. Cursor or Anthropic's Claude Code can provision databases and infrastructure using Encore's primitives. The type system provides guardrails so AI-generated infra code is safe to deploy. "Sounds like vendor lock-in." Your infrastructure runs in your cloud account. If you leave Encore, the RDS instance is still there. Code changes are minimal as well (10-20 lines of code). See below for a breakdown.

DORA Research has found that in 2025 developer productivity is way up with AI (+21% task completion, +98% PR volume). No surprises there. Yet, delivery metrics are flat (deploy frequency + lead times barely moved). Why? The bottleneck just moved from writing code, to delivering code. A 30 min CI/CD pipeline used to be fine: 1 day coding + 30 min CI = ~6% overhead It’s a very different picture with AI coding: 30 min coding + 30 min CI = 100% overhead Same pipeline. Very different perspective. Platform tooling is going to become a key priority in 2026 as organizations are adopting AI for coding, and will want to cut down this overhead. DORA agrees in their 2025 State of AI-assisted development report: "Our data shows a direct correlation between a high-quality internal platform and an organization’s ability to unlock the value of AI." BUT, not every organization needs to build their own. If you're looking for the fastest way to get a developer platform in place, that matches AI coding speed, we’ve built Encore for exactly this use case: - Framework level integration to optimize AI coding with strong guardrails - Automated local infrastructure + MCP for faster iteration - Preview Environments per PR for end-to-end testing - Automated AWS/GCP provisioning built into a high-performance CI/CD system - Built-in observability: distributed tracing, service catalog, more You don’t just reduce CI/CD overhead. You shrink iteration time inside the coding loop too. In our benchmarks vs. frameworks like NestJS and Express, we’ve proven Encore has 70% faster task completion times, with 50% less token usage. DM if you want a demo.

Introducing 'npx add-skill encoredev/skills' - 18 skills for building backends in your own AWS/GCP cloud faster than ever before. One command. Works with Cursor, Claude Code, Codex, OpenCode, and more. Everything you need: databases, APIs, auth, pub/sub, cron - in TypeScript and Go.

You can now configure which pull request branches create preview environments. Either all branches, or only those matching specific patterns (e.g. feature/*, backend/*, release-*). Comes in handy for mono-repos or any setup where you don't want a preview env spinning up for every single PR.

"I think of you as product founders, not sales founders" Great observation from one of our investors in our latest catch-up. No disagreements here..! Since we started Encore, we've been squarely focused on our users and how we can best build a great product to help them: - Get a mega productive dev workflow - Avoid the distraction/cost of platform engineering - And lately... how to safely go further and faster with AI coding tools Sales and marketing has always been a sideshow for us, and so far we've relied mostly on organic growth. Example: Until this week we didn't even have dedicated feature pages on our website..! The downside is we've probably left growth on the table. The upside is there's lots of untapped potential. So, we're now hiring for a Founding GTM role to help us go after it. If you’re interested in leading the charge in driving awareness and building demand for the development platform for the AI era, this is for you. You’re probably someone who: - Enjoys working in a small senior team, being close to founders and close to users - Wants to get in early and help shape the direction of a fast-growing company - Has marketed to engineers before at a startup - Is happy owning the whole funnel, not just one box on an org chart (we don't have an org chart) - Can turn customer and market insights into clear positioning and messaging that lands - Has built and operated a sales pipeline - Doesn’t mind rolling up your sleeves: user interviews, content, launches, experiments, pipeline support If that sounds like you (or someone you know), DM me.