plan_infrastructure
Plan an infrastructure stack — read-only
inetGeek's /plan/ planner: one suggested starting provider per layer — the cheapest with a documented free tier or a clean USD starting price, ranked by the provider's own facts, never a quality score — with its editorial reason and a floor total. THE TOTAL IS A FLOOR, NOT A PROJECTION: it sums documented entry points ($0 for a real free tier), and a layer whose pricing is usage-based with no flat minimum is listed as excluded, never counted as free; traffic, storage and usage move every number upward (use estimate_monthly_cost for a volume). Pick a stage or name layers explicitly; each stage is a superset of the one before it, and scale is most layers rather than all of them. Security requirements re-pick every layer whose providers document those criteria, and say so when no candidate satisfies every requirement rather than picking one anyway. PASS THE PROJECT'S CONTEXT: read its config and dependencies first (wrangler.jsonc, vercel.json, package.json, env var names, Dockerfile) and give already_using (providers it runs today), platform (the vendor it deploys on) and exclude. Without them most layers are TIES — every provider documents a free tier and the pick is only the alphabetically first — and the tool says so layer by layer rather than presenting it as a recommendation. With them, a layer you already cover is left alone, and a tie is broken toward providers on your own platform.
This tool is read-only.
Arguments
| Argument | Type | Required | What it does |
|---|---|---|---|
stage | string | no | One of "idea", "mvp", "growth", "scale", "enterprise". Each stage is a superset of the one before it; enterprise selects the same layers as scale and differs by requirement, not by layer. Ignored when layers is given. |
layers | array of string | no | Layer keys to plan: hosting, database, storage, auth, email, observability, queues, cdn, caching, vector-db, secrets, ci-cd, llm, gpu, data-api, federation, analytics, payments, search, dns-hosting, kubernetes, iac, backup, api-gateway, load-balancing, realtime, waf, data-warehouse, etl, media, sms, streaming, feature-flags, incident-management, finops, docs, ztna, model-hosting |
security | array of string | no | Requirements every pick must document as satisfied: ssoSaml, scimProvisioning, mfa, auditLogs, soc2, iso27001, hipaaEligible, gdprDataResidency, pciDss |
framework | string | no | Optional application or runtime — "nextjs", "astro", "django", "laravel", "wordpress", "nodejs", "nuxt", "sveltekit", "ghost", "n8n". Appends the hosts that document real support for it, so one call answers "what does a Next.js project at MVP stage need, and who runs it". |
already_using | array of string | no | Providers the project ALREADY uses, by id or name — "cloudflare-pages", "stripe", "Neon". A layer one of them covers is reported as covered and left out of the floor; the rest of the plan is built around them. Find the id with search_infrastructure or list_providers. |
platform | string | no | The platform the project runs on, as a vendor name: "cloudflare", "aws", "google", "microsoft", "vercel", "digitalocean". Where that vendor sells a provider in a layer it is preferred, because one platform is one bill, one login and one network. Matched on the registrable domain of each provider's homepage. |
exclude | array of string | no | Providers the project cannot or will not use (ids or names), e.g. for a licensing, residency or vendor-lock-in reason. Never picked. |
Example
Arguments:
{
"layers": [
"hosting",
"database",
"analytics",
"payments"
],
"framework": "astro",
"platform": "cloudflare",
"already_using": [
"stripe"
]
}The server's answer on 2026-10-25 (first 1,400 characters):
Hosting: Cloudflare Pages — Free tier — https://inetgeek.com/hosting/cloudflare-pages/
basis: on your platform (cloudflare) — chosen over the cheapest provider in this layer
every hosting provider: https://inetgeek.com/hosting/
Database: Aiven — Free tier — https://inetgeek.com/databases/aiven/
why: Teams who want more than one open-source data service from one vendor and one bill — Postgres beside Kafka, ClickHouse or OpenSearch — with the availability tier chosen per service rather than fixed.
TIE, NOT A RECOMMENDATION: 9 providers document the same starting price here, and Aiven is only the first alphabetically. Others: Firebase, Neo4j, Neon, Nile, Prisma Postgres, Supabase, TigerData, Turso. Choose on what the project needs (compare_providers, filter_providers), or pass already_using / platform / exclude.
every database provider: https://inetgeek.com/databases/
Web analytics: GoatCounter — Free tier — https://inetgeek.com/analytics/goatcounter/
why: A personal site or a small business that wants real analytics and no bill. The hosted service is free for what GoatCounter calls reasonable public usage, the script is around 3.5 KB, and there is a JavaScript-free tracking-pixel option.
TIE, NOT A RECOMMENDATION: 4 providers document the same starting price here, and GoatCounter is only the first alphabetically. Others: Simple Analytics, Traks, Umami. Choose on w
…