0%
Depot
Sign up

AI infrastructure architect · Depot

From code to cloud, in a conversation.

Connect a repo, answer a few plain-English questions, approve one reviewed AWS architecture with a monthly price on it. Depot builds it in your account.

Sign in with GitHub

From repo to running

Repo to live URL in under 15 minutes.

Depot reads the framework, the database, the jobs. You answer 6–8 questions. Nothing is built until you approve the plan and its cost.

See how it works

Your AWS, your control

Never a stored credential.

One revocable IAM role in your account, templated Terraform you can read line by line, and a destroy that always works.

See the patterns

{ depot }

founder note

“The shape of an app's infrastructure is predictable from its code. Read the repo, ask what the code can't tell you, and the right architecture is a choice — not a guess.”

Faizan Anwar

Creator of Depot

Final-year project, 2026

The architecture proposal

One of four reviewed architectures.

Depot scores your repo against four hand-written patterns, picks one, and prices it before a single resource exists.

depot.app/w/flowra/plan
Plan

Static site

S3 · CloudFront

Marketing sites, SPAs and docs behind a CDN.

Estimated $/month$0–1
6
Resources
4 min
Deploy
$0
Idle cost
Plan

Serverless API

Lambda · API Gateway · DynamoDB

Low-traffic APIs and event-driven backends.

Estimated $/month$0–5
11
Resources
7 min
Deploy
<$1
Idle cost
Proposed

Full-stack on ECS

Fargate · ALB · RDS · Secrets

SaaS with a database and file storage.

Estimated $/month$40–60
50
Resources
14 min
Deploy
$40
Idle cost
Plan

ECS with workers

Full-stack · worker · SQS

Apps with background jobs or queues.

Estimated $/month$55–80
58
Resources
15 min
Deploy
$55
Idle cost

Illustrative proposal — the real plan comes from your repo and your answers.

Four reviewed patterns

//01

Hand-written, tested Terraform. The AI chooses and parameterises; it cannot invent a resource.

One revocable role

//02
Your AWS account
depot-deployerAssumeRole · external ID

A CloudFormation stack in your account. Delete it and Depot's access is gone.

Priced before it exists

//03

per month, idle

$47
  • ECS Fargate
  • ALB
  • Secrets Manager

Every plan carries a monthly estimate and the reasoning behind each choice.

One workflow, from repo to running

Analyze. Answer. Approve. Live.

Four steps and a plan you can read, with the reasoning behind every choice and the alternatives it rejected.

  1. We read your repo

    //01
    Ne

    Next.js

    found · web

    Ex

    Express

    found · api

    Su

    Supabase

    found · hosted db

  2. You answer 6–8 questions

    //02

    Expected traffic?

    3/7
    • A handful of users
    • Hundreds a day
    • Thousands, spiky

  3. Approve the plan and its cost

    //03

    Full-stack on ECS

    ecs-fullstack · 50 resources

    Estimated$47/mo
    • Plan
    • Cost
    • Reasoning

  4. Live in your AWS, deploys on push

    //04
    • 1BuildDone
    • 2ProvisionDone
    • 3flowra.appLive

Real repo. Real resources.

Flowra, deployed with Depot: a Next.js + Express + Supabase app on ECS full-stack.

Flowra

//01

Architecture

ecs-fullstackPlan · 50 resources · 2 services
“Depot chose ECS full-stack and skipped RDS because the database is hosted on Supabase — exactly what I would have done by hand.”

m-faizananwar

Flowra · Next.js + Express + Supabase

Case study

Flowra

How Flowra went from a repo to a live URL

Depot detected two services — a Next.js web app and an Express API — and a hosted Supabase database. It proposed ECS full-stack with no RDS, priced it, and provisioned every resource after one approval.

50
resources planned
2
services
0
databases (hosted)
See the repo

Stack detected

  • Next.js
  • Express
  • Supabase
  • Docker
  • GitHub Actions
  • Terraform
  • +2

Built for Infrastructure

Every proposal is scored against a 20-repo benchmark
so the architecture you approve is the one
the code actually needs.

Pattern selection
Across 19 repos

%

The right architecture
every time

Learn More

Configuration
Across 46 parameters

%

Every parameter correct
on the benchmark

Learn More

Repo to live URL
Serverless and ECS

min

From first analysis
to a running app

Learn More

What Depot says.

Every choice ships with plain-English reasoning you can read before you approve — and the alternatives it rejected.

express-api

//01

Express · Node 20

Chose serverless-api because services[0].runtime.framework=express and traffic=hundreds; no long-running work was found.

serverless-api
Pattern
<$1
Idle / month
11
Resources
ReasoningView plan

Flowra

//02

Next.js + Express · Supabase

Chose ecs-fullstack: two services with a Dockerfile each and a hosted database, so RDS is skipped and the connection string goes to Secrets Manager.

ecs-fullstack
Pattern
$47
Idle / month
50
Resources
ReasoningView plan

docs-site

//03

Astro · static export

Chose static-site because build.output=static and there is no server runtime; CloudFront in front of S3 keeps it under a dollar.

static-site
Pattern
$0
Idle / month
6
Resources
ReasoningView plan

video-pipeline

//04

Django + Celery · Redis

Chose ecs-with-workers: a Celery worker and a queue mean background jobs need their own service, so SQS replaces Redis as the broker.

ecs-workers
Pattern
$58
Idle / month
58
Resources
ReasoningView plan
Sign in with GitHub

Free during the FYP. Your AWS bill is the only cost.

Pricing.

Your AWS bill, not ours.

Depot is free for the final-year project. What you pay is what AWS charges for the pattern it builds — these are the idle bands for each.

Static site.

//01

Static site

Marketing sites, SPAs and docs on S3 behind CloudFront.

$0–1/ month idle

S3 storage and CloudFront requests; the free tier covers most of it.

  • S3 bucket + CloudFront CDN
  • HTTPS certificate
  • Deploys on git push
  • One-click destroy
Sign in with GitHub

Serverless API.

//02

Serverless API

Low-traffic APIs and event-driven backends that cost nothing while idle.

$0–5/ month idle

Typically under $1 a month idle; you pay per request.

  • Lambda + API Gateway
  • DynamoDB table
  • CloudWatch logs and alarms
  • Deploys on git push
Sign in with GitHub

Full-stack on ECS.

//03

Full-stack on ECS

SaaS with a database and file storage, always on.

$40–60/ month idle

Fargate, a load balancer and Postgres; RDS is skipped when your database is hosted.

  • ECS Fargate service + ALB
  • RDS Postgres (or your hosted DB)
  • Secrets Manager
  • S3 for uploads
Sign in with GitHub

ECS with workers.

//04

ECS with workers

Everything in full-stack plus a worker service and a queue.

$55–80/ month idle

The full-stack band plus a second Fargate task and SQS.

  • Everything in full-stack
  • Worker service
  • SQS queue
  • Safety-review gate on risky plans
Sign in with GitHub

Your AWS bill, not ours — Depot is free for the FYP. Destroy always works.

Frequently asked questions.

The things people ask before pointing Depot at their AWS account.

Still have questions? Open an issue

FAQ

//01
Do you store my AWS keys?

No. You create one IAM role in your account from a CloudFormation stack Depot gives you; Depot assumes it per job with an external ID and never holds long-lived keys. Delete the stack and access is gone.

Can I see the Terraform?

Yes, all of it. Every pattern is a hand-written module in the open repo; your plan is that module plus a tfvars file of the values Depot chose. The workspace shows both before you approve anything.

What if I change my mind?

Nothing is built until you approve, and you can change answers and re-plan for free. After a build, destroy tears down everything tagged for the workspace — and destroy always works.

Does it write Terraform with AI?

No. The model only emits a JSON document validated against a schema; the Terraform comes from reviewed modules instantiated with those values. It cannot invent a resource that isn't in a pattern, which is what makes it safe to point at your account.

What does destroy do?

It runs terraform destroy against your workspace's state, waits until every resource tagged Project=depot-mvp and Workspace=<id> is gone, and if AWS refuses it tells you what is left — in plain English and in the technical detail.

Which frameworks?

Anything that fits the four patterns: static builds (Astro, Vite, Next export), Node and Python APIs (Express, FastAPI, Django), Dockerised full-stack apps with Postgres or a hosted database, and apps with a worker and a queue. Shapes that don't fit are told, not guessed.

Ready to deploy?

Your repo, live on AWS.

Connect GitHub, answer a few questions, approve a plan with a price on it.

One revocable role

//01

Sign in with GitHub

Depot asks GitHub for read access to the repo you pick and permission to commit a deploy workflow. Your AWS account is connected later, separately, with its own role.

  • Read your repositories
  • Commit a deploy workflow
  • Nothing built until you approve
Sign in with GitHub

No email, no password — GitHub only.

Want to read first? How it works

Every resource is tagged Project=depot-mvp, so nothing hides in your account.