If you need to self-host Nextjs at scale we wrote up an article with all the hidden feature flags and secrets we had to discover about running Nextjs in high traffic environments: www.sherpa.sh/blog/secrets...

Glad it was helpful. And yeah that skew protection issue is ongoing at the moment. The github issue link in the article is a pretty interesting read.

If you want to share our article or service with anyone that might find it helpful. I'd appreciate it 😊

We actually do this at Sherpa.sh but its a full PaaS platform.

But fwiw I think you are right about self-hosting being difficult. We ran into a lot of issues that we documented here: www.sherpa.sh/blog/secrets...

Yeah, there are a ton of features that are not supported by nextjs in a selfhosting environment. We actually just wrote up all the hidden features and flags that we ran into running Next.js at scale in hopes that it helps others: www.sherpa.sh/blog/secrets...

If you don't want to move to another big VC backed provider. We just wrote up a post on how to self-host nextjs apps at scale to help: www.sherpa.sh/blog/secrets...

Hi Andy, Founder at Sherpa.sh here. If you end up giving us a try feel free to DM me for any help or feedback. We like to stay close to our users to drive roadmap and identify any friction points or issues early. Cheers!

Schedo.dev moved from Vercel over to sherpa.sh to reduce their infrastructure costs and per-seat billing without sacraficing a great developer experience. Now they can deliver their core platform to their customers without worrying about their cloud bill ballooning out of control.

I'm still figuring out how to DM on bsky. haha. I guess I'm curious if you know any activist websites specifically running on Vercel?

"What's your favorite technique for speeding up development? Drop your tips below! #TechInnovation #StartupLife"

Want to ship code as fast as you're writing it? @sherpa_sh eliminates infrastructure headaches. Connect your git repo → every push triggers deployment. No config hell, just you and your users. Try it: sherpa.sh

#NoCode #DeploymentAutomation

"Pro tip: Keep your subdirectory isolation clean to prevent AI overlap. #DevOps #TechTips"

"The result? As I finish reviewing one AI's output, the next solution is ready. My dev velocity has exploded while avoiding conflicts between agents. More code shipped = more time talking to actual users. #10xDeveloper #ProductivityHacks"

"My secret: Multiple @windsurfai.bsky.social instances working on the same project simultaneously, each limited to specific subdirectories. While one AI codes, I'm already setting up the next task for another. #SoftwareDevelopment #CodingHacks"