Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vercel Service Markup

service-markup.vercel.app

Post reply on HN
Print view View original

41–50 of 109 posts

Re: Vercel Service Markup

#41

Post by beginnings »

re-thc wrote: post #25
steve_adams_86 wrote: post #22

Earlier quoted context omitted.

I’ve got a lot of dumb little things living out on the internet deployed this way, and I don’t think I’ve ever been compromised. Maybe you were just especially unlucky? There are some things I’ve deployed without much care and yet they’re always as I left them. I’m not saying there’s nothing to worry about. I’m just not sure it’s all that difficult with some rudimentary (but sane) security practices.

It is a common theme. Bots and others scan ports and IP ranges all the time. Looking at server logs I always see random server connections trying to get to things like wp-login.php to look for an exploit. If you put it out there and don't actively secure it it's bound to get compromised - just a matter of when.

Yeah, it's actually crazy just how much every open address gets spammed. You freak out like why are there thousands of attempts to login to my server that I haven't advertised at all, then you Google it and find out it's just the normal state of the internet.

Re: Vercel Service Markup

#42

Post by brundolf »

egeozcan wrote: post #37
msy wrote: post #24

Vercel raised $300m+ at the top of the market and paid over the odds to hire a ton of JS ecosystem luminaries. Those investors are going want to see a return, not just an eyewatering wage bill. Anyone building on top of their ecosystem is going to get fleeced, they have no other route to possibly justifing their valuation or ever providing a passable return on that capital. Everyone else should be preparing their pla…

> Everyone else should be preparing their plan b for what happens if they impode and Next.js, Turborepo etc development fractures or grinds to a halt. Isn't next.js too big to fail? Currently we are trying to define a modern stack for our front-end, and I always thought next.js/react to be the next java -> Perhaps Solid.js is much better (IMHO it surely is) but I probably won't get fired for choosing next. If not, wh…

It might be. It was eg a first-class part of React's Server Components design/rollout strategy

The question is exactly what would happen if it lost its backing, even if it wouldn't outright fail:

- Meta forks it and/or takes over from there?

- Multiple community forks that fracture adoption?

- Stagnation and slow decline as it stops shipping big upgrades and goes into community-maintenance mode?

Re: Vercel Service Markup

#43

Post by chrisco255 »

satvikpendem wrote: post #30
paxys wrote: post #15

Earlier quoted context omitted.

Next.js is incredibly popular in the industry. Some of the largest companies out there use it. Whether they host on Vercel or not I can't say, but I'm sure that number isn't zero. Of course we are talking more about auxiliary stuff like landing pages, marketing sites, blogs and documentation, not hosting for their core business.

Vercel's revenue was 25.5 million in 2022 (according to Nathan Latka who has pretty reputable figures) on a 2.5 billion dollar valuation [0]. They're hyped but it doesn't seem like any big players actually use them at scale, as it's likely much, much cheaper to host on bare cloud providers like AWS, which Vercel themselves wrap (with Vercel also now wrapping the services included in OP's site). [0] https://getlatka.c…

How does Latka get its data?

Re: Vercel Service Markup

#44

Post by PaulWaldman »

What's the feasibility of replicating Vercel's services and architecture?

Without supply side limitations, resellers generally become reduced to commodities over time. This is especially likely with high margin markups, which seems to be the case with Vercel.

Is the integration of Next.js on Vercel really that superior to other platforms?

Re: Vercel Service Markup

#45

Post by satvikpendem »

chrisco255 wrote: post #43
satvikpendem wrote: post #30

Earlier quoted context omitted.

Vercel's revenue was 25.5 million in 2022 (according to Nathan Latka who has pretty reputable figures) on a 2.5 billion dollar valuation [0]. They're hyped but it doesn't seem like any big players actually use them at scale, as it's likely much, much cheaper to host on bare cloud providers like AWS, which Vercel themselves wrap (with Vercel also now wrapping the services included in OP's site). [0] https://getlatka.c…

How does Latka get its data?

He interviews them on condition of revealing the numbers, which he sells to investors. He has enough clout in the industry that people want to reveal their numbers to him in exchange for being able to raise more money.

Re: Vercel Service Markup

#46

Post by alexghr »

Well, if nothing else, at least Vercel's new integrations have put new things on my map of free things to use in side-projects (I had never heard of Upstash before now) :))

Re: Vercel Service Markup

#48

Post by tobase »

jrudolph wrote: post #38

The appeal of a no-ops workflow for basic frontend apps is there. We’ve got a bunch of static docs sites built with vuepress and docusaurus that are a great fit for this. Not that we can’t whip up a CDN with terraform and a CI/CD pipeline with preview environments, but my team would rather spend its energy on our core product. However we’ve been badly burned by vercel, netlify and render.com switching their pricing m…

It’s simple. It’s not more popular because of bad UX. I would not be surprised if the best customer that Vercel chasing is also a customer that can add these costs to their customer or take a hit on the margin.

Re: Vercel Service Markup

#50

Post by brundolf »

jrudolph wrote: post #38

The appeal of a no-ops workflow for basic frontend apps is there. We’ve got a bunch of static docs sites built with vuepress and docusaurus that are a great fit for this. Not that we can’t whip up a CDN with terraform and a CI/CD pipeline with preview environments, but my team would rather spend its energy on our core product. However we’ve been badly burned by vercel, netlify and render.com switching their pricing m…

I've been wondering what the limits of the user-based pricing actually are

If it's just the number of people who can go in the UI and press the button (when it automatically gets deployed from git anyway), or change env secrets, can't you just have a single admin account and call it "one user"? That could be a single actual person (how often do you change those things?) or could even be a single account shared by the whole team

What am I missing?

Post reply on HN