Wolfram|Alpha is officially launched

Background

Wolfram|Alpha is a query service that computes answers from structured data instead of returning a list of web links. Before the launch the team made its preparations public: an announcement titled "Going Live — and Webcasting It" said the team would start webcasting its preparations at 7pm CDT on Friday evening, 15 May 2009^[2]. That gave the launch a scheduled starting point and an audience that could watch the team get ready.

What happened

Stephen Wolfram wrote that he pressed the button at 9:33:50pm central time on 15 May 2009, and that Wolfram|Alpha went live at that moment^[3]. The launch team's own posts describe the same evening slightly differently: the team said the site went live in test mode at 8:48pm CST on the Friday^[1]. The two accounts agree on the day.

The formal announcement came at the start of the following week. In a post dated 18 May 2009, the launch team wrote that Wolfram|Alpha was officially launched^[1].

Key details

The team treated the first weekend as a working test rather than a finished release. It said the team worked through the weekend on load testing and bug fixes^[1].

The numbers from those days were reported by the team itself. During testing the service processed nearly 23 million queries, and by the team's estimates approximately three out of four of them gave satisfactory results^[1]. Users sent over 22,000 feedback messages during the launch weekend^[1]. By late Sunday night the team said it was able to test all compute clusters at full capacity^[1], which indicates the whole system was exercised end to end rather than only at partial load.

Why it matters

The launch weekend did not mark the end of the load. A first-week post from Stephen Wolfram, dated 26 May 2009, said the service was approaching 100 million queries^[1]. Against the roughly 23 million queries handled during testing, that figure shows query volume kept climbing well after the launch weekend was over.

Because the team webcast its preparations and then published its own operating numbers, the launch is also a documented case of how a public release of an online service was run: a scheduled start time, a weekend spent on fixes, feedback collected in bulk from users, and a cluster-by-cluster capacity check before the service was declared officially live^[1][2]. The progression from "test mode" on Friday to "in production" three days later is visible in the record the team left behind.