No. You write application code and Encore sets up the cloud resources it needs, including networking, IAM and secrets. Everything is created in your own account, so you can inspect it in your cloud console at any time.

Instead of writing separate config files, you declare infrastructure directly in your application code. Encore provisions everything automatically in each environment, so there are no Terraform configs or Pulumi stacks to maintain.

No. Encore works alongside what you have. Teams usually start with new services and leave existing infrastructure, and the Terraform that manages it, where it is. Encore can also deploy into an existing Kubernetes cluster.

Encore supports TypeScript and Go, both with the full feature set. Python and Rust support is coming soon. You deploy to AWS or GCP in your own account. On the frontend, use any framework and generate a typed API client for your backend.

Yes. Agents define infrastructure in the same code they already write, and run and validate the full app locally or in a preview environment. Encore's MCP server gives them context about your services, APIs and traces.

Yes. Adopt Encore incrementally by converting individual services to the Encore SDK, one by one. You can also connect existing databases, buckets and topics instead of recreating them.

Use it directly. Your application runs in your own cloud account, so you can call any AWS or GCP service from your code alongside the resources Encore manages. Nothing is walled off.

Yes. Encore provisions standard managed services like RDS, Cloud SQL, ECS on Fargate, Cloud Run and GKE in your own cloud account. Your application runs there, with no runtime dependency on Encore's platform, so production traffic never passes through Encore and there's nothing to migrate as you grow. Teams like Groupon and Coinbase run production workloads on Encore.

Agents never get cloud credentials. They declare infrastructure in code, and Encore provisions it deterministically, following best practices for security and reliability. Environment-specific configuration, like instance sizes and secrets, is applied in Encore's control plane, separate from the code agents write. Every pull request gets its own isolated preview environment, and changes are recorded in the audit trail.

An IAM role (AWS) or service account (GCP) that you grant in your own account and can revoke at any time. Encore uses it to create and update the resources your services declare, and never deletes infrastructure without your approval. On the Enterprise plan, we support just-in-time permissions that are granted only when you approve a specific change.

The Starter plan is free for local development and small projects. The Pro plan is $49 per team member per month, plus per-environment and per-resource fees. Your cloud resources are billed by AWS or GCP directly in your own account.

Yes. Your infrastructure runs in your own cloud account, so your cloud bill, and any credits on it, work as usual. Credits cover what you pay AWS or GCP, not the Encore plan fee.

Encore is designed to avoid vendor lock-in. You deploy to your own cloud account (AWS or GCP), so you own and control your infrastructure.

If you decide to stop using the Encore platform for infrastructure automation, you can keep using your existing infrastructure and set up your own CI/CD pipeline using Encore's Open Source tools.