Beluga

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

~ the obituary ~

i missed beluga. it had a december 2010 launch and a december 2011 shutdown, total lifespan twelve months, the entire visible run happening inside the english-language san francisco tech press cycle. by the time anyone in turkey would have heard of it, the underlying code had already been repackaged as facebook messenger. that messenger app is what reached turkey at scale. beluga itself was a footnote that only the people who read techcrunch every morning would have noticed before it disappeared.

the founders were lucy zhang, ben davenport, and jon perlow. all three had left google in 2010 to build the thing they thought google should have built and had not. the thing was group chat for small ad-hoc friend groups. sms could not really do groups in 2010, blackberry messenger could but only between blackberry users, whatsapp existed but was still a one-to-one product, and group-chat-as-a-feature was the obvious gap. beluga's design called those groups pods. you would make a pod for your weekend dinner crew, another pod for your colleagues, another pod for your high school friends, and conversation would stay scoped inside the pod.

the product launched quietly in late 2010 and got tech-press attention through the first two months of 2011. by the end of february facebook had reached out. on march 1, 2011 facebook acquired beluga in what was described publicly as an acqui-hire. lucy, ben, and jon joined facebook's messaging team. the agreement was that beluga would continue running for the rest of the year while facebook used the codebase and the design ideas to build its own product. the actual deal terms were never disclosed but were small enough that the press described it as a talent acquisition rather than a strategic purchase.

~ the case file ~

~ what it became ~

facebook messenger shipped on august 9, 2011, eight months after the original beluga launch and five months after the acquisition closed. the architecture was recognizably the beluga architecture. the group-chat-as-pods idea became facebook messenger's group threads. the push-notification immediacy that beluga had built around was the same immediacy that messenger inherited. lucy zhang stayed at facebook on the messenger team for years afterward. ben davenport went on to other crypto and infrastructure projects. jon perlow continued at facebook on the messaging product surface.

by late october 2011 facebook messenger was the top free app in the apple app store and was rolling out aggressively across android. the original beluga product had become redundant. on october 28, 2011 the founders posted a farewell on the beluga blog confirming the shutdown plan. november 11, 2011 was the read-only date when new messages stopped being accepted. existing message history stayed accessible for one more month so people could export. december 15, 2011 was the full shutdown. all servers went down and the domain redirected to facebook's messenger landing page.

~ the funny part ~

beluga is the cleanest example of the acqui-hire ladder working as intended for the founders. three ex-googlers shipped a product in december 2010, got bought by facebook three months later, watched their architecture become the foundation of a messaging product that today has more than a billion users, and the original product gets a twelve-month run and a polite shutdown. measured by months of independent existence beluga was a short life. measured by impact on the design of subsequent messaging products beluga reshaped how every modern messenger handles group threads.

the thing that makes beluga readable as a category is that the work survived even though the brand did not. the team's design choices about how groups should be created and named and notified are still visible in messenger's group-chat ui in 2026. whatsapp's group chats borrow the same patterns. discord's server-and-channel model is a different shape but inherits the same underlying assumption that group conversation needs its own scope object rather than being a flat list of recipients. beluga is part of the underground lineage of that assumption.

~ what replaced it ~

what got buried with beluga was the standalone-startup version of the same idea. there was a brief window in 2011 when several other group-messaging startups were trying to do the same thing facebook had just acquired beluga to solve. groupme, kik, fast society, textplus, all of them competing for the same gap. groupme got acquired by skype in august 2011 for around eighty-five million dollars and became a still-living product. the rest mostly faded. the messaging app market consolidated into whatsapp, messenger, imessage, and a handful of regional winners over the next five years, none of which look much like beluga on the outside but all of which carry pieces of its design vocabulary underneath.

by 2026 the beluga brand is a search result that mostly points to retrospective writeups. the official site has been gone for fourteen years. the only visible artifact is the github profile of the original team and an old farewell post that techcrunch and the next web archived in october 2011. for a december 2010 to december 2011 product that ended as the foundation of a billion-user app, that is a quieter legacy than the impact deserves.

@}-->--

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

« previous  ·  random  ·  next »