ElephantSQL

» see elephantsql.com as it lived, on the wayback machine

~ the eulogy ~

ElephantSQL sold one thing: a PostgreSQL database that somebody else installed and somebody else backed up. It arrived in 2013, when running your own Postgres meant a server you were personally responsible for at three in the morning, and it was among the first services anywhere to offer the database as something you clicked a button to get. The company behind it was 84codes, a small Swedish outfit in Stockholm that also ran CloudAMQP and CloudKarafka.

The plan everybody actually remembers was the free one. Tiny Turtle gave you twenty megabytes of storage and five concurrent connections, which sounds like nothing and was in fact enough. Twenty megabytes holds a lot of rows if those rows are a class project, a hackathon demo, or the first version of something you were not sure you would finish. No credit card, and no trial clock counting down to a conversion funnel at the end of thirty days.

On 26 February 2024 the company published an end-of-life announcement. New signups would stop on 1 May 2024, the service would reach end of life on 27 January 2025, and the reason given was plain enough: 84codes had seen significant growth in RabbitMQ and LavinMQ and had decided to focus on the AMQP protocol instead. Nothing had gone wrong. The database business was simply not the business they wanted to be in.

~ the dossier ~

~ what twenty megabytes was for ~

The free developer database is a category that barely gets written about because nobody pays for it and nobody markets it. It exists in the gap between a tutorial and a product, in the weeks where you need persistent storage but have no idea whether the thing you are building will last the month. Tiny Turtle sat in that gap for ten years and asked for nothing.

What that produces is an enormous number of small dependencies nobody tracked. Connection strings pointing at ElephantSQL ended up committed into course materials, blog posts, tutorial repositories and the config files of applications whose authors had long since moved on. When the deletion date came in February 2025, a lot of what broke belonged to people who were not reading the announcement because they had stopped thinking about the project years earlier.

~ eleven months of notice ~

Measured against how these usually go, the wind-down was unusually generous. Announcement to end of life was eleven months. After 27 January 2025 there was a brownout period of scheduled daily interruptions, designed to make the outage obvious to anyone still connected and ignoring email, and the final blackout with all shared-instance data deleted came on 28 February 2025. The company also arranged a migration path with Aiven rather than leaving customers to find their own exit.

~ the distance, and the part that is not distance ~

There is no Turkish angle to a hosted Postgres plan, and pretending otherwise would be inventing one. Infrastructure like this has no region and no culture around it. It was used by whoever needed a database that afternoon, in Ankara or anywhere else, and the thing that reached people was never the brand but the free tier underneath it.

What is worth noting is how the site reads today. elephantsql.com still resolves, still serves, and its title tag has been edited to say "ElephantSQL - discontinued PostgreSQL as a Service". The end-of-life page is still posted with all four dates on it. Most dead products get a parking page or a redirect to a parent brand. This one is still paying to host a page whose only job is to tell you it is over.

@}-->--

              )
             (_)
            .-'-.
            |   |
            |   |
            |   |
            |   |
          __|   |__   .-.
       .-'  |   |  `-:   :
      :     `---'     :-'
       `-._       _.-'
           '""""""

« previous  ·  random  ·  next »