←back to thread

Show HN: Self-Host Next.js in Production

(github.com)
90 points vednig | 2 comments | 20 Nov 24 22:07 UTC | HN request time: 0.556s | source
Show context
slashnode ◴[20 Nov 24 23:53 UTC] No.42199449[source]▶
I've been surprised by the number of companies adopting nextjs as their defacto framework without concern for the uncomfortable reality that the framework is built to be hosted on vercel with self hosting largely supported as an afterthought. It's great that opennext exists, but it really shouldn't _have_ to exist (as I believe some of the maintainers have publicly stated)
replies(6): >>42199660 #>>42199710 #>>42199736 #>>42199910 #>>42199951 #>>42200008 #
1. switz ◴[21 Nov 24 00:56 UTC] No.42199910[source]▶
It doesn't have to exist - I run next.js self hosted and it's arguably better than hosting on vercel (no cold starts, dedicated cpu, next to my api server/db).
replies(1): >>42202659 #
2. dbbk ◴[21 Nov 24 09:54 UTC] No.42202659[source]▶
I also self-host but it must be said that "no cold starts" and "next to my api server/db" are also supported by Vercel so that's not really a benefit