TursoDB aims to be fully compatible with sqlite, so files you create with tursodb can be read by sqlite and vice-versa. Like sqlite, turso is in-process, so it runs alongside your application, which is quite different from postgres' client-server architecture.
The only think turso has in common with postgres is mvcc, which is a rather standard concurrency control model across modern databases. Idk if I answered your question :)
It's an interesting move because the PE playbook is to buy a company and jack up the prices and cut half the workforce while doubling the workload of the other employees.
EA is already widely reviled for this stuff so it will be like getting blood from a stone