How do I use Quay with my servers and code?

Using Quay with your infrastructure is separated into two main actions: building containers and distributing them to your servers.

You can configure Quay to automatically build containers of your code on each commit. Integrations with GitHub, Bitbucket, GitLab and self-hosted Git repositories are supported. Each built container is stored on Quay and is available to be pulled down onto your servers.

To distribute your private containers onto your servers, Docker or rkt must be configured with the correct credentials. Quay has sophisticated access controls — organizations, teams, robot accounts, and more — to give you full control over which servers can pull down your containers. An API can be used to automate the creation and management of these credentials.

How is Quay optimized for a team environment?

Quay's permission model is designed for teams. Each new user can be assigned to one or more teams, with specific permissions. Robot accounts, used for automated deployments, can be managed per team as well. This system allows for each development team to manage their own credentials.

Full logging and auditing is integrated into every part of the application and API. Quay helps you dig into every action for more details.

Additional FAQs

Yes, you can change your plan at any time and your account will be pro-rated for the difference. For large organizations, Quay Enterprise offers unlimited users and repos.

Please contact us at our support email address to discuss the details of your organization and intended usage.

Yes! We offer unlimited storage and serving of public repositories. We strongly believe in the open source community and will do what we can to help!

Quay uses Stripe as our payment processor, so we can accept any of the payment options they offer, which are currently: Visa, MasterCard, American Express, JCB, Discover and Diners Club.