- Intro: Explains problem but not what is Neki or what it's for.

- Why Neki: Explains alternatives and why they suck but not what is Neki or what it's for.

- How does Neki work: Describes the technical components but not what is Neki or what it's for.

- What you get beyond sharding: Explains how to run/deploy but not what is Neki or what it's for.

- What is a platform preview + Try Neki today: 140 words on the definition of "preview" and links to get started... but not what is Neki or what it's for.

Edit: The landing page has 100x more useful information up front -> https://neki.dev/

Edit #2: They've since added a "What is Neki" section. Good reaction time.

Edit: your marketing site actually has excellent marketing information.

Edit #2: They've since replaced the blog post with a link to the marketing page. Good reaction time.

- short paragraph saying "we launched neki"

- short paragraph saying why neki was needed

- paragraphs about what neki is (with a header)

That seems like a very reasonable structure for a blog post like this one. Not being able to get to the third paragraph of a blog post seems like a "you" problem, not a blog problem.

Why do people post screenshots of an article on social media instead of linking to it?

Sometimes ignorance, but often because the web is such a hostile experience these days - paywalls and subscribe banners and cookie warnings and slow pages.

That's sad.

If you know that to be true and still add your links everywhere ("helping"), isn't this a spammer's confession?

Vitess today is not the Vitess of 2021. About 70% of the current codebase was written in the last five years, based on lessons we learned running it at scale.

Neki is built for Postgres from the ground up, by the engineers who did that work.

On the Multigres comparison, I'll admit we get a bit salty, mostly because "Vitess for Postgres" invites the comparison. But to date there's no public evidence of a working sharding implementation in Multigres. Their sharding design doc landed this week, and it lists cross-shard query planning and resharding execution as explicitly out of scope.

Neki does sharding today, including online resharding that switches traffic without a maintenance window. It isn't open source, but you can spin up a cluster and try it yourself.

Found this from neki.dev.

If you have such luxuries, I bet you don't have enough scale to be really profitable for him.

I can think of at least 4 other ways of scaling horizontally without switching DB engines. I'd have to be mightily constrained to have this particular product as the only option.

Based on what I've read so far, with his shit-talking the competition, he seems like... a bit of an asshole.

They build good stuff and care.

(I'm a paying PS customer)

https://x.com/samlambert/status/2098075451373834681?s=20

PS - Just some advice that I learned in sales 101 early in my career...focusing on shit talking the competition generally isn't a strategy that works well.

"You're not wrong Walter, you're just an asshole." - The Dude

Only petty people can hold that view.

No one accused you of dishonesty.

Sam, it feels like you're just playing games. It's hard to take anything you say or do seriously. Are you going to OSS this thing? Or have you decided to backpedal?

Congrats on the checks notes closed launch, I guess?

0: https://github.com/multigres/multigres

Open source being by far the more important of the two, since it means the user is more insulated by terrible corporate decisions thus making it more suitable for long term planning.

Their CEO always immediately comes in and makes a fool out of himself. He is what you get when you mix narcissism and being a midwit.

Unlike you, probably, if we're slinging unfounded accusations.

A remarkable own goal given that if they'd literally held their tongue, I'd be at worst indifferent.

I want to let you know that I have customers that pay PlanetScale millions of dollars and have told me they came to the product because of my Twitter account. So you will never make me feel bad about this.

Commerical open source is fine. It's nobody else's fault if you raised too much to make it work sustainably.

Sad to see this coming from a company that was itself built on the foundation of an open-source project like Vitess.

We maintain Vitess using our company funds. Why are you going after a small company for defending itself against companies like Amazon but not criticizing the reason we have to do this.

I would love to open source Neki and I have not said we won't.

> When we are ready we will release Neki as an open source project suitable for running the most demanding Postgres workloads.

Has this changed?

https://web.archive.org/web/20260516145550/https://planetsca...

https://web.archive.org/web/20260910204345/https://planetsca...

Just launch the product and let it speak for itself. The constant need to take shots at competitors comes across as pretty childish.

- PgDog is open source

- It runs anywhere, not just your cloud

- It's built for Postgres, not a MySQL pivot

I wonder how the performance will be, but I can just rewrite everything in Rust.

And now planetscale have made a Vitess like equivalent for Postgres which they have made proprietary

Google is big enough to survive open-sourcing Vitess, k8s, angular, etc. Planetscale isn't.

That Youtube built. I know at the time Youtube was already part of Google but I don't think of Vitess as a Google Stack.

Apparently not.

However we have a whole team working to improve Postgres and we always prefer to contribute those efforts to the Postgres community.

They claim to provide unlimited IOPS (I/O operations Per Second).

I would like to get some of these drives myself. Sounds like a technical miracle.

On the other hand claiming such miracles makes me wonder which other aspects in this are are actually a working miracle or rather a mythos/false marketing claim.

I think this is marketroid for “we don’t limit them” not a statement about physics