[cdaringe]

Using next strictly for the front-end feels like a slight miss. It works fine to do so, but its strong suit is being a full stack react framework. If your app needs a server and you opt out of next, you sacrifice the common config model, isomorphic pages and data loading patterns, integrated api routes, optimized route/path browser bundles, …more. I get that folks like python, but if you’re already paying the cost of one major tech framework in your project, you should seriously consider if you really want to pay for two (pay used loosely for cost of tech ownership). Next can and will do support your BE needs, presuming you’re not deeply reliant on some biz value from company python packages

[aosaigh]

I think it depends on your needs. Any time I've tried to use an "all-in-one" full-stack solution I've quickly run into limitations, whether it's task running, authentication, web sockets, load balancing, redirects. Many of the platforms have limitations that you only run into once you're deeply committed and you've then got to find all sorts of hacks to fill in the blanks. Not saying Next and Vercel is like that per-se, but there is a lot more control when running your own backend services.

[leros]

I disagree very strongly. Next is great for just front-end. I use Next with the static export.

- Next does a good job as a React framework (ie CRA alternative) - Next does a great job with code bundling and splitting out of the box - Next's static build system makes it easy to query your backend statically at build time to generate things like blogs, SEO pages, etc.