Note: This post is from before Orchestrate was acquired by CenturyLink.
We are pleased to announce that Orchestrate has gone into general availability today – less than five months after we opened our private beta, and less than a year since we founded the company.
While we feel pride at what we’ve accomplished in that time (as well as the normal trepidation about bugs and snafus), we are mostly eager to see what users will build with Orchestrate.
The first set of beta users included an artist who creates his installations using code and data, a game designer who works a day job to supports his vision for a new kind of gaming platform, two prestigious e-commerce sites eager to reduce costs for applications already in production, and the CTO of a prominent financial institution interested in “spending less on software and more on people.”
As a database platform, we get to see a lot of ideas in their early stage – ideas we haven’t anticipated and which make demands on our system for which we haven’t planned. Community has a funny way of redefining the direction of a product based on its needs. With more than 1,300 beta sign ups, we have already made some important changes to the Orchestrate service.
We were surprised how fast a community developed, and how generously they supported us. Before Christmas, we already had a node.js, Ruby, Go, Java, python, and CLI client built by eager supporters. People weren’t shy about telling us to fix things, either. We are a community, and our users are part of our greater team.
And yet, for all that we’ve learned from our early users, Orchestrate remains largely true to the original premise. We have multiple databases supporting several query types behind a single API. We offer dead simple pricing so users can quickly calculate their total spend. People want something they can get started within minutes, if not seconds. And lock-in scares people so we make sure your data stays mobile. Most importantly, we still haven’t built our own databases…and pray we never will.
The most important aspect of today’s launch – one that can trace its origins back to the time when Orchestrate consisted of little more than a bunch of notes on a beer cosy – is our conviction that developers, freed from the constraints of managing traditional infrastructure, can focus more time and resource on design, user experience, and features that matter to end users. We believe more time devoted to creative tasks benefits all of us. And as we press the figurative launch button, we watch with curiosity at what this will allow our users to build.
So make cool things! Thanks for supporting Orchestrate.