> We can’t wait to have this available as a preview later in Q2 and truly make global storage a breeze, so keep an eye out!

then apologised for missing that in September 2023 [2]

> We initially announced that we were working on S3 support for Bunny Storage all the way back in 2022. Today, as 2023 is slowly coming to an end, many of our customers continue to follow our blog, hoping for good news about the release.

changing the roadmap to early 2024 [2]

> But we are working aggressively toward shipping S3 compatibility in early 2024.

That same post also has the beautiful "At bunny.net, we value transparency." quote. It's early 2026, and they're literally ignoring my support requests asking about what the roadmap is looking like for this now.

So, do not trust their product or leadership at all.

[1] https://bunny.net/blog/introducing-edge-storage-sftp-support... [2] https://bunny.net/blog/whats-happening-with-s3-compatibility...

Their log delivery api is delayed by over 3 days, despite them promising only "up to 5 minutes delay" in their docs: https://docs.bunny.net/cdn/logging

Why isn't it on the status page you might ask? Oh, that's because a delay is not "critical", but I fear I am losing loglines now, their retention is 3 days.

It's an interesting strategy for them, because it doesn't inspire confidence in me about their other offerings. When they can't reliably operate a log delivery API or be transparent about issues, it's hard to trust them with something as critical as a database.

Any Linux distro can have MySQL or Postgres installed in less than five minutes and works out of the box

Even a single core VPS can handle lots of queries per second (assuming the tables are indexed properly and the queries aren't trash)

There are mature open source backup solutions which don't require DB downtime (also available in most package managers)

It's trivial to tune a DB using .conf files (there are even scripts that autotune for you!!!)

Your VPS provider will allow you to configure encryption at rest, firewall rules, and whole disk snapshots as well

And neither MySQL or Postgres ever seem to go down, they're super reliable and stable

Plus you have very stable costs each month

  While in public preview, Bunny Database is free.

  When idle, Bunny Database only incurs storage costs. One primary region is charged continuously, while read replicas only add storage costs when serving traffic (metered by the hour).

  Reads - $0.30 per billion rows
  Writes - $0.30 per million rows
  Storage - $0.10 per GB per active region (monthly)

They don't elaborate, but apparently libSQL has an HTTP API called "Hrana": https://github.com/tursodatabase/libsql/blob/main/docs/HRANA... - if that's what they're exposing, wouldn't it make more sense to call it libSQL-compatible or something?

Its European rather than from USA so its less dependent on that orange guy in that white/golden house

If not, it seems like it would be quite a bit of work to implement the synchronization... and I don't understand why one would use it otherwise.

Isn't the operational burden of SQLite the main selling point over Postgres (not one I subscribe to, but that's neither here nor there)? If it's managed, why do I care if it's SQLite or Postgres? If anything, I would expect Postgres to be the friendlier option, since you won't have to worry about eventually discovering that you actually need some feature even if you don't need it at the start of your project. Maybe there are projects that implement SQLite on top of Postgres so you can gradually migrate away from SQLite if you need Postgres features eventually?