Most likely an opening offer to be negotiated down to 3-5% would be my guess.

This looks very strange:

"Automattic will have full audit rights."

"WordPress.org and Automattic will have full audit rights, including access to employee records and time-tracking."

Well it's basically saying, just give us the money. The "audit rights" only apply if they're donating time, so they want that to be the most difficult and intrusive option -- ie., its only there for PR.

The choice is, "some money and we'll look the other way; or open all your books, and donate 8% of your workforce to wordpress"

The 'audit rights' are written at the end of 2(a) and apply to just giving money. It's not just time.

You're right, I should've focused on the " including access to employee records and time-tracking " aspect

isn't that necessary given the request of a revenue percentage?

Could automattic know the exact numbers in a different way, since WPEngine is not a public company?

Agree with this. Is this correct?

It's there in the Fee section.....

I get that regulatory bodies should have access under certain conditions, but letting a competitor do this? Makes zero sense.

Surely this would be a violation of HIPAA, Privacy and any number of state laws.

You can't just give out confidential employee records to third parties.

None of these parties are subject to HIPAA.

Employee health records are often stored in third party systems that are subject to HIPAA.

Point is that Automattic would have full access to this as well.

Those providers may be subject to it.

Attempts to go fishing in such records would be pretty unlikely to succeed; it'd be an uneforcable request contrary to public policy, with no relevance to such an audit. It would be correctly and easily fought.

Having advised a company who applied to YC with traction, proven MRR, and a serious team behind, I can’t say it is certainly the case. But having seen a number of companies coming out of the latest batch, it only smells like YC has been drinking from the punch bowl that is HackerNews’ front page hype train.

This is crazy. And then I hear about solid products/companies that don’t get any/very little funding at all because it has no “AI” and it baffles the mind.

Funders are betting on founders. They see somebody willing to take shortcuts and ride hype trains, turn good faith projects and pass them off as their own innovation, and the see the kind of sociopathic organization that has the potential to "become the next Uber."

They aren't funding the viability of the product, they are funding for a take of future earnings of the morally bankrupt or the righteous will of the hopelessly naive. In either case, it's all about how effectively they can affix a leash.

Rent-seeking over value-creation.

YC filters for companies for gorillion dollar missions / solve gorillion dollar problems.

A mission that is, "I have an AI, input is business plan, output is entire IT infrastructure" is what YC sees here. i.e. programming as a field (quite a cost center) is no longer needed, ironically. Because of that the bar is low. Honestly if anyone is reading this, if you find a very clever novel way to go after this, surely you would be funded

Very nice demo!

When you ran it the first time, it took a while to load up. Do subsequent runs go faster?

And what cloud provider are you all using under the hood? We work in a specific sector that excludes us from using certain cloud providers (ie. AWS) at my company.

You are correct! After the first request, an image will be on a machine and it’s cached for future use. This makes subsequent container startups much faster. We also route requests to machines where the image is already cached as well as dedupe content between images in order to make startups faster

We are running on top of AWS however can run on top of any cloud provider as well as are working on you using your own cloud. Happy to hear more about your use case and see if we can help you at all - email me at [email protected].

PS: I will state that vLLM has shocking load times into VRam that we are resolving.

My anecdotal experience tells me that it never works in a high scale product environment. Having managed and lead 2 teams that maintained a legacy system with hex-arch and we had to move DBs in both. We ended up rewriting most of the application as it was not suitable for the new DB schema and requirements.

Thanks for sharing. It matches my experience.

After many years of a lean team serving high scale traffic (> 1 million monthly active users per engineer), most abstractions between customer and data seem to turn into performance liabilities. Any major changes to either client behavior or data model are very likely to require changes to the other side.

There's a lot to be said for just embracing the DB and putting it front and center. A favorite system we built was basically just Client -> RPC -> SQL. One client screen == one sql query.

Wonder how this will work for remote companies. Will the post a super large band for positions ranging across Europe? Or will it geographically defined?

If I understand correctly, it’s the push back on the call center in general when using AI agents. Why go through the trouble at that point versus another manner of fixing my issue.

For example, when I need to activate a new SIM card, I need to call the company to get it activated. But if I’m talking to an AI agent at that point, why not have me go through another channel (website/app?) to activate it?

Sort of related, but I just came off a RyanAir flight of all things, and they have something similar. Instead of talking a stewardess to get a sandwich, I order it on the app and they bring it to me.

It worked quite well, and surprising coming from RyanAir.

Yeah but when you get into the taxi comparison, it’s based on roi more than anything.

For a phone, it’s purely esthetic, ergonomic and user friendliness that most people are buying them. Not usually roi based decision.

Not sure when this story took place but now you have riders who WANT the tan lines.

It's pretty easy to find pix of 80s-era racers (e.g., LeMonde) who sported pretty intense glove tans -- pale hands, but with a circle tan on the back and tan fingers. Sharp lines on the upper arm and thigh from jerseys and shorts are still common, too, but I see less of all of this now than I did back then.

I ride a lot, and I barely have them, because sunscreen exists and I don't want cancer.