How do I deploy a Next.js, Python, Go, or Rust app to AWS with Lander?

Sign in to Lander with Google at lander.host/onboard, install the Lander GitHub App, pick a repo, and push to your default branch. Lander runs CodeBuild to clone, docker build, push to ECR, and roll out to a per-customer Fargate task. Live at .app.lander.host in 4-6 minutes. Step-by-step guides per stack are at lander.host/deploy.

What makes Lander different from Vercel, Netlify, Railway, and Render?

Lander runs your code in a per-customer isolated VPC + Fargate task on real AWS — not shared serverless. AWS WAF + OWASP rules + AI Bug Hunter ship on every plan including Free (Vercel gates WAF at Enterprise; Railway and Render don't include it). The Free plan permits commercial use, unlike Vercel's Hobby tier. The Pro plan adds an in-app Claude Sonnet 4.6 builder with click-to-edit visual editing — no other deploy platform has this.

Does Lander support custom domains?

Yes, on the Hobby plan and above. Point a CNAME at .app.lander.host from your registrar (GoDaddy, Namecheap, Cloudflare, Squarespace, Route53). Lander auto-issues an ACM SSL certificate and adds it to your ALB. No manual cert renewal — ACM rotates automatically.

What languages and frameworks does Lander support?

Anything that runs in a Docker container — Next.js, FastAPI, Flask, Django, Express, Go (net/http, chi, gin, echo, fiber), Rust (Axum, Actix-web, Rocket), and more. Static sites (Astro, 11ty, Hugo, VitePress, plain HTML) skip Fargate and ship to S3 + CloudFront automatically — ~30x cheaper. WebSockets and long-running connections are supported on Pro+.

How much does Lander cost?

Free plan is $0/month — 3 static sites, 100 GB bandwidth, commercial use allowed (unlike Vercel's Hobby). Hobby is $25/month for 1 dynamic Fargate site + unlimited static + custom domains + 50 GB bandwidth. Pro is $75/month for 1 dynamic + unlimited static + 20 Claude builder turns + click-to-edit visual editor + 300 GB bandwidth. Team is $200/month for 2 dynamic + 75 Claude turns + SSO + audit logs + 1 TB bandwidth. All paid plans include a 30-day money-back guarantee.

Can I deploy a Vercel app to AWS via Lander?

Yes. Add a Dockerfile to your Next.js repo (with `output: 'standalone'` in next.config.js), push to GitHub, and connect to Lander. Most Vercel-deployed apps work without modification because they're already containerized via the standalone output. The deploy guide at lander.host/deploy/nextjs walks through it in 5 minutes.

Is Lander self-hosted?

Lander runs your code on its own AWS account by default. On Team and Enterprise tiers we support BYO AWS — Lander deploys into your AWS account, you keep ownership of all infrastructure, AWS bill goes to you directly. The control plane is managed by Lander; the customer infrastructure is in your account.

Does Lander support Claude or AI-driven deploys?

Yes. The Pro plan ($75/mo) includes an in-app Claude Sonnet 4.6 builder. Describe what you want, Claude writes the code, click any element on the live preview to edit. 20 turns per month included on Pro, 75 on Team. Models: Sonnet 4.6 (Anthropic). Generated code lands as a PR in your own GitHub repo so you own it.

Where does Lander deploy to?

AWS us-west-2 (Oregon) by default. Per-customer VPC, Fargate task, ALB, ACM cert, Route53 record, and CloudFront distribution. Multi-region deploys are on the Team tier roadmap.

[deploy · Elixir · Phoenix · LiveView · OTP]

Deploy Elixir / Phoenix LiveView to AWS in 5 minutes.

Push a Phoenix repo to Lander. Phoenix releases compile to a self-contained tarball, deploy to per-customer Fargate, LiveView WebSockets work out-of-the-box on Pro+.

$ deploy now →see pricingfree plan · no credit card · commercial use OK

[walkthrough · 5 minutes]

Generate a Phoenix release

`mix phx.gen.release --docker` creates a working Dockerfile + release config. The release runs without Erlang installed — just the compiled BEAM artifacts.

# in your Phoenix project root
mix phx.gen.release --docker
git add Dockerfile bin/server
git commit -m "Add release Dockerfile"

Set release env vars

Phoenix releases need: SECRET_KEY_BASE, DATABASE_URL, PHX_HOST, PHX_SERVER=true, PORT=80. Generate SECRET_KEY_BASE with `mix phx.gen.secret`.

Provision Postgres

Set LANDER_NEEDS_DB=1; Lander provisions RDS and exposes DATABASE_URL. Update your release migration command to run on each deploy via Lander's `release_command` env var.

Push and deploy

First deploy ~6 minutes (Erlang/OTP compile is slow). Subsequent deploys ~2 minutes thanks to CodeBuild layer caching.

[why · lander vs vercel · railway · render]

→BEAM's per-process isolation + Lander's per-customer VPC = nested isolation. Compelling for compliance.
→ARM64 Graviton2 — Erlang/OTP runs natively, perf is excellent.
→WAF blocks WebSocket-targeted attacks at the ALB before Phoenix sees them.

[gotchas]

·Phoenix LiveView needs sticky sessions on the ALB. Lander auto-enables this for Phoenix apps detected by /lib/_web/endpoint.ex.
·If you use Oban for background jobs, the worker runs in the same Fargate task by default. For high-throughput, request a sidecar worker (Pro+).
·DNS clusters across multiple Fargate tasks need libcluster — single-task deploys (Hobby) skip this.

Concepts: per-customer Fargate→Pricing — Hobby $25→

[other stacks · same flow]

deploy nextjs →deploy python →deploy go →deploy rust →deploy static →deploy bun →deploy ruby →deploy java →deploy dotnet →

5 minutes from clone to live URL.

no credit card · push from GitHub · real AWS underneath$ deploy now → lander.host