zlacker

This sounds a lot like https://turso.tech/ ? Unless I misunderstand, they're both pitching SQLite-for-the-cloud.

>>ForHac+(OP)
Yes, they mention they use libsql. Don't know why I should use them and not the product by the actual libsql authors.

>>Square+n
An advantage is the integration with other Bunny services like containers etc.

Also, not sure about now, but historically Turso didn't have to best uptime.

>>Square+n
Some European companies migrate their dependencies from US clouds to European ones. Turso is registered in Delaware. Bunny HQ is in Slovenia. Different data related policies apply.

>>Square+n
Bunny has their own infra while Turso relies on a cloud provider (AWS) which is unfortunately a no-go for many European companies

>>Square+n
turso deprecated their edge replica offering when they went all-in on rewriting sqlite so bunny fills a nice void here. while turso didn't pull the plug for existing customers, new customers were left looking for alternatives with edge replica (that couldn't replicate on-device), and bunny does a nice job here.

turso also made it so your primary had to be in one location, but bunny will move it around based on latency on next boot.

>>ForHac+(OP)
Bunny is more like Cloudflare. Database is just 1 part of their offering. They're doing full service edge compute, storage and CDN.

>>Square+n
Marek from bunny.net here. Another advantage is our global network: Bunny Database is available in 41 regions, so if your app has global users (or users in specific locations), you can avoid workarounds to hide latency from the DB.

We actually ran a benchmark to see how read latency degrades with distance from the database: https://bunny.net/blog/how-database-location-affects-far-awa...