Quay.io was originally created out of necessity when the company wanted to use Docker containers with an original IDE product. Docker containers were being used to host and isolate server processes invoked on behalf of our users and often running their code. The project was started by building the Docker image dynamically whenever a new host node spun up. The image was monolithic. It was too large, took too long to build, and was hard to manage conflicts. It was everything that Docker wasn't supposed to be. When it was decided to split it up into pre-built images and host them somewhere, it was noticed that there wasn't a good place to host images securely. Determined to scratch the itch, Quay.io was built, and officially launched it as an aside in a presentation to the Docker New York City Meetup on October 2nd, 2013.
After launch, customers demanded that Quay.io become the main focus. They rely on the company to make sure they can store and distribute their Docker images.
In August, 2014, Quay.io joined CoreOS to provide registry support for the enterprise.
|Mar 8, 2015||TechCrunch - The State Of Enterprise Tech In NYC|
|Jan 23, 2015||TechCrunch - Google Launches Private Docker Repositories For Cloud Platform Users|
|Aug 13, 2014||eWeek - CoreOS Acquires Quay.io for Private Docker Repositories|
|Aug 13, 2014||TechCrunch - CoreOS Acquires Quay.io To Launch Its Private Docker Repository|
|Aug 13, 2014||Gigaom - CoreOS acquires Quay.io to give Docker users better control of their data|
New York, NY