Assess target operations: Vercel migration maps the application, data and deployments to a target model. Arrange a consultation.
Vercel costs become understandable once the base fee, capacity model and services actually used are recorded separately. This breakdown is for teams reviewing their invoice and assessing a possible move.
Date and methodology
Pricing as of October 2026. All vendor amounts are US dollars excluding taxes, not WZ-IT euro offers. Currency and taxes.
The tables use the linked vendor sources and the stated region, product configuration and billing unit. Separately listed extras and operational services must be recorded separately for comparison; equal resource counts do not establish equal performance.
You may reuse the tables and calculation methodology in this article with attribution and a link to this article.
Contents
- Date and methodology
- Which Vercel costs apply to Pro?
- Separate CDN and data transfer by model
- Attribute image optimization and function execution
- Reduce Vercel costs and verify the effect
- Decide on migration using total costs
- Our approach at WZ-IT
- Further guides
Which Vercel costs apply to Pro?
The table separates fixed fees from metered charges. Actual billing depends on the team and its configuration. Individual Enterprise contracts and older billing models require a separate review.
| Item | Current Pro model | Primary source |
|---|---|---|
| Platform | USD 20/month, one deploying seat included | Pro |
| Additional deploying seats | USD 20 per seat/month; viewers free | Team seats |
| Usage credit | USD 20 per team/month; no additional credit per extra seat | Credit model |
| CDN requests and Fast Data Transfer | Covered by the capacity tier when Flat Rate CDN is enabled | Flat Rate CDN |
| Image optimization | Transformations, cache reads and writes | Image pricing |
| Function execution with Fluid compute | CPU time, provisioned memory and invocations | Functions |
Our recommended review framework is: fixed fees plus paid CDN tier plus infrastructure usage not covered by credit plus other services. Attribute each invoice item exactly once. For add-ons, check whether the fee applies per project or per team rather than multiplying it by seat count indiscriminately.
Usage credit expires monthly; additional seats do not increase it. Credit and billing. Hobby is intended for personal, non-commercial use and is therefore not a general free replacement for a business project. Plan boundaries.
Separate CDN and data transfer by model
Flat Rate CDN is a capacity model. The included Pro tier provides one million CDN requests and 1 TB monthly. Further tiers cost USD 20, 100 or 300 monthly for 10, 50 or 150 million requests; each of these three tiers includes 50 TB. Check activation, exclusions and fair use. Exceeding capacity in a billing cycle can trigger a higher tier in the following cycle. Bulk file and media distribution is not covered indiscriminately. Capacity and eligibility.
Without Flat Rate CDN, billing is per unit and region. Fast Data Transfer describes the path between the CDN and the end device; Fast Origin Transfer describes the path between the CDN and functions. The latter is not among the resources expressly covered by Flat Rate CDN. Transfer metrics.
For cost analysis, we recommend three columns: visitor region, request count and data volume. The function region does not substitute for the visitor region. Also record which projects use which CDN model. A global average without this mapping is a poor basis for checking a specific invoice.
Attribute image optimization and function execution
As of 19 October 2026: regional on-demand ranges or the explicitly identified compute region.
| Metric | Price | Primary source |
|---|---|---|
| Image transformations | USD 0.05 to 0.0812 per 1,000 | Image optimization |
| Image cache read units | USD 0.40 to 0.64 per million | Image optimization |
| Image cache write units | USD 4.00 to 6.40 per million | Image optimization |
Active CPU, Frankfurt fra1 |
USD 0.184 per CPU-hour | Fluid compute |
Provisioned memory, Frankfurt fra1 |
USD 0.0152 per GB-hour | Fluid compute |
| Function invocations | USD 0.60 per million | Function billing |
Image cache units measure 8 KB each, not images. Transformations are billed on MISS and STALE; not every HIT causes a global cache read. Measurement. Image delivery also involves CDN and transfer. Image optimization flow.
Pro applies usage credit instead of Hobby allowances. Pro billing. With Fluid compute, CPU billing pauses during I/O, while memory billing continues during in-flight requests. Billing logic. Recommendations should therefore examine CPU, memory and invocation count separately.
Reduce Vercel costs and verify the effect
Our recommended process starts with the largest documented item, rather than a predetermined migration:
- Align invoices and usage to the same period. Record projects, regions, seats and additional services. Identify usage not yet invoiced separately.
- Investigate repeated requests. Trace polling, refetching and image requests in the browser. Vercel identifies excessive polling and frequent remounting as review points. Optimize CDN usage.
- Examine image variants deliberately. Document required sizes and cache behaviour. Assess changes against image quality, delivered bytes and all affected invoice items. Lower image usage alone does not establish lower total costs.
- Measure function paths. Attribute computation, memory and waiting time. Only then change caching, data access or runtime configuration.
- Configure cost controls. Review notifications and, where appropriate, automatic actions in Spend Management. A threshold alone does not stop usage; automatic actions can take effect with a delay. Pausing a project is an operational decision that should be agreed with its owners beforehand. Spend Management.
Specify an expected effect and a functional check for each change: Does content remain current? Do authentication and permissions work? Are images readable? Does the error rate change? Then compare a suitable period and document intervening changes in traffic or the application. This assessment plan is a recommendation, not a report of completed tests.
Decide on migration using total costs
Next.js can be self-hosted; caching, image optimization and multiple instances require appropriate configuration. A container alone does not replace a complete platform design. Next.js Self-Hosting.
For a decision, we recommend covering the same items on both sides:
| Comparison point | Include in target costs |
|---|---|
| Application and deployment | Runtime, builds, preview environments, rollback and access |
| Delivery | CDN, DNS, transfer, images and required caching |
| Persistent data | Databases, storage, backups and recovery |
| Operations | Monitoring, updates, responsibilities and incident handling |
| Transition | Adaptations, data transfer, parallel operation and acceptance |
Staying is a valid comparison path when required platform features and operations together are economically suitable. Assess moving once the intended target model and responsibilities are clear. This general table cannot establish a savings percentage. The Vercel-to-Coolify guide covers the technical path; Coolify is one possible component of target operations.
Our approach at WZ-IT
Vercel migration addresses the application, functions, data, domains and deployments in the selected target model. For an enquiry, we recommend a cost export, Vercel services in use, framework version, data paths and intended operational responsibilities. The actual scope is defined before commissioning work.
This breakdown supports that preparation. It promises no particular savings, duration or functional equivalence. The PaaS exit page provides the broader assessment for multiple platforms.
Further guides
- Migrate Vercel to Coolify or Hetzner
- Assess Coolify as an open-source PaaS
- Compare self-hosted PaaS platforms
Define the migration: Assess Vercel migration and target operations against your application. Arrange a consultation.
