The neki router shares no code with Postgres.

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

Correct.

Many of the engineers who built Neki also worked on Vitess for years. But it's a ground up new implementation designed to specifically target Postgres.

Once they implement sharding...

Yet. But it’s built by the guy who created Vitess and cofounded PlanetScale, so while it doesn’t have sharding implemented at the moment I think it would be foolish to discount it. Plus it’s open source.

The PlanetScale team spent years improving Vitess with lessons learned from many different high scale customer workloads. We continue to invest in and improve Vitess. It's a substantial and growing part of our business.

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.

Sugu? The guy that "barely worked" and "shipped nothing at PlanetScale" according to Planetscale's CEO?

Anyone who has worked with Sugu knows this simply isn’t true. Sam Lambert is lying.

every metric we have proves otherwise

We literally have the counterfactual of the old product and company before he left. We can fully discount Multigres doing anything.

Bus ads have been running for a little while now. A few billboards around too.

You can expect to see it in early 2026 for both Metal and EBS backed databases.

In typical PlanetScale style, we like to beat our estimates.

https://planetscale.com/blog/postgres-18-is-now-available

To add to this, if you look at the top 10 committers to Vitess over the last 12 months, 8 of them are helping with Neki in one way or another:

https://github.com/vitessio/vitess/graphs/contributors?from=...

I can't really help with what you're specifically looking for, but I'm pretty sure my grandfather worked on these as an engineer. He retired from Boeing in 1985. Died almost 20 years ago.

  ls -lh hello.wasm
  -rw-r--r--@ 1 tcole  staff    24M Apr 22 14:18 hello.wasm

This is on macOS. That is hello.py compiled to wasm with Py2wasm.

Indeed, this can be way further optimized. For example, you can probably do a wasm-strip and wasm-opt passes that would leave the wasm file being ~5-10Mb. Still very big, but a bit more reasonable.

The good thing is that thanks to Nuitka you could actually do some tree shaking and only include the imported files and not everything in between (although this might break other behavior such as eval and so).

You got it to work? For me it complains about some header files missing and breaks the nuitka installed on the system.

I wonder what's the meaning of doing this , if hello world program need 20M to download before run ?

Wow! 24M makes it even less practical than interpreted pyodide.

Here is a trivial example, also on a M3 Max:

  cat hello.py
  print("Hello, Wasm!")

  time python3 ./hello.py
  Hello, Wasm!

  ________________________________________________________
  Executed in   26.86 millis    fish           external
     usr time   16.37 millis    0.13 millis   16.24 millis
     sys time    7.25 millis    1.14 millis    6.11 millis

  time wasmer hello.wasm
  Hello, Wasm!

  ________________________________________________________
  Executed in   84.77 millis    fish           external
     usr time   50.26 millis    0.14 millis   50.12 millis
     sys time   28.97 millis    1.21 millis   27.76 millis

  time wasmtime hello.wasm
  Hello, Wasm!

  ________________________________________________________
  Executed in  141.72 millis    fish           external
     usr time  120.86 millis    0.13 millis  120.72 millis
     sys time   16.65 millis    1.20 millis   15.45 millis