3 ms·
I love developing on Vercel, but this is an absurdly complicated pricing structure: https://vercel.com/docs/pricing https://vercel.com/docs/pricing I have no
by aosaigh 3y ago
I love developing on Vercel, but this is an absurdly complicated pricing structure:
https://vercel.com/docs/pricing https://vercel.com/docs/pricing
I have no idea what sort of bill I can expect with new costs for "edge network routing" or "incremental static regeneration" (neither of which I understand nor want).
- deleted 3y ago[deleted]
- ffo 3y agoI agree, the network part looks overly complicated to me as well. Bandwidth was at least relatable to some extend. But now it looks like one needs to combine requests and client traffic as well as server traffic. It wonder how that works if you proxy another vercel site through a vercel project. I.e. a nextjs projects proxies /docs to a docusaurus page. Because as of today the billed the bandwidth and requests twice :-(