Compare the base price, the billing term and the resources you actually need. Free, Pro and Team share one platform. Paid plans add capacity and teammates without a per-seat fee.
Monthly base prices in USD. Multi-year savings below. Usage and add-ons are separate.
Every plan includes the AI website builder, 5,000+ themes, GitHub and MCP deployment. Choose your term to see the upfront charge and renewal total.
Start building. Put something real on the web.
No base plan charge
Free to start. No upfront plan charge.
Commercial projects welcome.
More room for production apps and a small team.
Save $336 · regular 48-month total $672
$336 paid upfront for 48 months.
Renews at $336 / 48 months.
Shared projects. More resources. Unlimited members.
Save $600 · regular 48-month total $1,200
$600 paid upfront for 48 months.
Renews at $600 / 48 months.
USD, before tax. Resource allowances reset monthly. Monthly equivalents are rounded for display; the upfront total is exact. Term discounts apply at every renewal. The 48-month term includes 24 free months.
Paid-plan usage budgets cover on-demand usage beyond included resources and add-ons; they exclude the base plan charge. Pro defaults to $50; Team to $100. Budget controls are not an instant hard-stop guarantee. Free has a $0 hard stop. These plans include edge and build allowances. Container compute and database services are metered separately.
| Your plan, in detail | Free | Pro | Team |
|---|---|---|---|
| Monthly equivalent | $0 | $7 | $12.50 |
| Upfront plan total | $0 | $336 | $600 |
| Renewal total | $0 / 48 months | $336 / 48 months | $600 / 48 months |
| Requests | 1M | 10M | 25M |
| Bandwidth | 100 GB | 1 TB | 2.5 TB |
| Edge CPU time | 10M ms | 100M ms | 250M ms |
| Build minutes | 100 | 500 | 1,250 |
| Team members | Solo | Up to 3 | Unlimited |
| Default usage budget | $0 · hard stop | $50 | $100 |
| Commercial use | Included | Included | Included |
| No per-seat charges | Included | Included | Included |
| AI website builder | Included | Included | Included |
| 5,000+ themes | Included | Included | Included |
| GitHub integration | Included | Included | Included |
| MCP integration | Included | Included | Included |
| Global CDN | Included | Included | Included |
| DDoS protection | Included | Included | Included |
A longer commitment reduces the base price. The same term discount applies when you renew for that term. Resource allowances still reset monthly; they do not become one shared multi-year pool.
USD, before tax. Base subscription only; usage and separately metered services are not included in this calculation.
These are three different numbers. Read them together before selecting a plan, especially if your application needs a database or a full container service.
Your plan and billing term determine the upfront subscription charge. Pro includes up to three members; Team includes unlimited members. Neither adds a fee for each included member.
Requests, bandwidth, Edge CPU time and build minutes reset each month. Edge CPU is measured in milliseconds of execution time; build minutes cover building the application rather than serving visits.
Paid usage budgets cover on-demand usage and add-ons, excluding the base subscription. Container compute and database services are separately metered. Review those costs alongside the base plan.
Free has a $0 hard stop. Pro defaults to a $50 usage budget and Team to $100. The current paid-plan budget is not an instant hard-stop guarantee. This page does not promise a fixed all-in bill.
For a solo builder starting a commercial app or testing a deployment workflow. Check the 1M requests, 100 GB bandwidth and 100 build minutes against your expected activity.
For up to three members sharing a production project. Compare 10M requests, 1 TB bandwidth and 500 build minutes with the work you actually run each month.
For unlimited members and higher monthly allowances: 25M requests, 2.5 TB bandwidth and 1,250 build minutes. Choose it for the capacity and collaboration you need.
COUNT THE WORK
The best estimate starts with the work your application performs. A page view, a cache miss, a model call and an import job can create very different usage. Build a resource picture before deciding that a base subscription price is the whole operating cost.
Requests and bandwidth grow with visits, API calls and asset size. A large image can consume more transfer than many small HTML responses. Include bot activity and client polling in the workload you measure.
Edge CPU measures execution work; it is different from build minutes and visitor wait time. Full container services have their own compute metering. Long-running workers and background tasks belong in the estimate even when nobody is visiting a page.
Managed databases and persistent resources are separate considerations. Size Postgres for the records and queries you need, and review Valkey for the cache or session workload. External model APIs can add another provider’s charges.
Planning model · no usage forecast or all-in invoice guarantee
THREE WORKLOADS, THREE COST SHAPES
Two applications on the same base plan can have different totals. Use representative traffic and actual resource settings to compare options. These examples describe what to account for, without inventing a benchmark, a guaranteed visitor capacity or a fixed monthly quote.
Start with requests, asset transfer and build frequency. Image optimization can reduce bandwidth; frequent rebuilds can increase build minutes. A static site may not need a database or a continuously running container at all.
Add authenticated request work, database queries and persistent records. Review connection pooling and indexes before increasing database size. If the framework needs a full server container, include its compute alongside the base plan and database usage.
Add file processing, worker concurrency, queue activity, database growth and provider inference. A few large jobs can cost more than many lightweight visits. Put limits around input size, output size and repeated work as part of the application design.
CAPACITY WITHOUT SURPRISE ASSUMPTIONS
Capacity changes and long-term commitments answer different questions. A longer subscription term changes the base payment; it does not make a database free, erase usage limits or turn a monthly allowance into a lifetime pool. Compare the selected resource settings as well as the plan name.
Choose a monthly workload and purchase term. See the included capacity, team seats and modeled delivery costs together.
Static delivery + builds. Commercial use. Zero server compute in this example.
Explore all plans ↗
Let.com Team$12.50/mo$600 paid upfront for 48 months. Same-term renewal: $600.
$4,008–$4,800 over 48 months, billed monthly. Constant usage and today’s rates.
USD before tax. Monthly requests are CDN asset requests, not unique people or page views; GB uses decimal units. Vercel is modeled with Flat Rate CDN enabled for an eligible web application and Basic 2-vCPU builds at $0.007 per minute. Build times are equal in the example, not a performance benchmark. Viewer seats are free on Vercel; the count above is deploying members.
The range reflects unclear credit eligibility for the fixed CDN tier: the lower estimate lets the $20 credit offset CDN plus builds; the upper applies it to builds only. Savings use the lower estimate. Actual invoices depend on configuration. This is a selected Flat Rate CDN configuration, not a claim that it is Vercel’s cheapest possible setup.
Excluded on both sides: server/edge execution, database and container compute, image processing, storage, model/API fees, add-ons and taxes. Let.com’s Edge CPU allowance cannot be equated directly to Vercel’s Fluid Compute CPU and memory billing. Workloads beyond Let.com inclusions are deliberately unpriced here. Multi-year totals assume constant usage and current prices; Vercel is billed monthly, not sold as a four-year commitment.
Rates reviewed October 20, 2026: Vercel Pro + seats · Flat Rate CDN · Basic build rates. Let.com rates come from the plans on this page.
Brand portfolio · planned deployments
Architecture examples for brands in our portfolio. These are planned deployments, not completed migrations or measured case studies.
Realty.com brings home listings, saved searches and agent discovery together. The proposed Let.com stack pairs a search API with managed PostgreSQL, Valkey caching and queued listing updates.
Document.com
Document.com combines guided templates, document storage and e-signatures. A planned Let.com backend would keep workflow records in managed PostgreSQL and send document generation to a queue, with files in asset storage.
Sue.com offers demand-letter workflows and small-claims preparation. The planned architecture uses a Let.com backend, managed PostgreSQL for case progress and a queue for document jobs and delivery updates.
Message.com
Message.com brings chat, email and phone conversations into one team workspace. A proposed Let.com deployment would pair conversation records in managed PostgreSQL with Valkey for transient state and queued channel events.
Rx.com offers online care and prescription services across several treatment categories. The proposed Let.com scope covers its public treatment catalog: a content backend, managed PostgreSQL, Valkey caching and public image assets.
Create.com provides web hosting, WordPress hosting, reseller plans and domains. A planned Let.com operations backend would track provisioning in managed PostgreSQL and process setup tasks through a queue, with Valkey for short-lived status.
Audit.com
Audit.com offers security assessments, readiness services and remediation engineering. The proposed Let.com workspace would use managed PostgreSQL for engagement tracking, queued report jobs and asset storage for project files.
Public billing reports are reasons to understand your meters. They are not a prediction of your bill.
A Next.js developer described a jump from $120 to $855, with bandwidth the largest charge and image delivery a major contributor. The discussion also covers caching and image sizing.
Read the original discussion ↗The author attributed the invoice to media scraping and disputed the spend controls. A Vercel employee replied that automatic pausing requires opting in and offered to investigate.
Read the report and response ↗Free has a $0 hard stop. Pro and Team default to $50 and $100 usage budgets, separate from the base plan. Paid budgets are not an instant hard-stop guarantee. Watch request volume, transfer, builds and separately metered services.
Understand the resource meters ↗These are unverified individual reports, not audited case studies or typical bills. Vercel’s pricing has changed, including Flat Rate CDN in 2026. Historical charges are not inputs to our current-price calculator.
Free is $0, Pro is $14 per month and Team is $25 per month for the base subscription. Monthly billing has no term discount. Taxes, additional usage and separately metered services are excluded.
One year includes 2 free months; two years include 6; three years include 15; four years include 24. The four-year term is 50% off the equivalent base subscription at the monthly rate. The full term is paid upfront.
No. It is a purchase-term discount. Renewing for the same term uses the same discount structure. If you choose a different term, the discount for that term applies.
No. Team includes unlimited members without per-seat charges. Pro includes up to three members. Member inclusion does not remove resource limits or separately metered usage.
Yes. Commercial use is allowed. Free still has monthly resource allowances and a $0 hard stop, so choose a paid plan if the workload needs more capacity.
No. Requests, bandwidth, Edge CPU and build minutes reset monthly. The longer purchase changes the base subscription price, not the resource-reset period.
No. It calculates the base plan charge, term savings and same-term renewal. It excludes taxes, on-demand usage, containers, database services and other add-ons.
Repository-driven releases or an AI-connected workflow.
