Like to use <b>Dockerfiles</b> to build your images? Simply upload your Dockerfile (and any additional files it needs) and we'll build your Dockerfile into an image and push it to your repository.
</div>
<divclass="tour-section-description">
If you store your Dockerfile in <iclass="fa fa-github fa-lg"style="margin: 6px;"></i><b>GitHub</b>, add a <b>Build Trigger</b> to your repository and we'll start a Dockerfile build for every change you make.
<divclass="tour-section-title">Share at your control</div>
<divclass="tour-section-description">
Share any repository with as many (or as few) users as you choose.
</div>
<divclass="tour-section-description">Need a repository only for your team? Easily <b>share</b> with your team members.</div>
<divclass="tour-section-description">Need finer grain control? Mark a user as <b>read-only</b> or <b>read/write</b>.</div>
<divclass="tour-section-description">Have a build script or a deploy process that needs access? Generate an <b>access token</b> to grant revocable access for pushing or pulling.</div>
<divclass="tour-section-description">Want to share with the world? Make your repository <b>fully public</b>.</div>
<divclass="tour-section-title">Docker diff whenever you need it</div>
<divclass="tour-section-description">
We wanted to know what was changing in each image of our repositories just as much as you do. So we added diffs. Now you can see exactly which files were <b>added</b>, <b>changed</b>, or <b>removed</b> for each image. We've also provided two awesome ways to view your changes, either in a filterable list, or in a drill down tree view.
Being responsible for operations of a startup means finding tools that just work, and Quay.io has provided that for us. Whenever we've needed a new feature, or found an issue, it was resolved immediately. I wish every third party we relied on offered the same level of support as Quay.io.
Docker is at the core of Aptible's deployment platform, and Quay provides the secure repository hosting we need to safely store our customer's application images, and our own. With its thorough team access control model, we can be sure that only authorized users are able to access a Docker image repository. No other Docker repository index makes this as easy as Quay.
<ahref="/user/?migrate"data-title="Starts the process to convert this account into an organization"quay-show="Config.AUTHENTICATION_TYPE == 'Database' && !user.anonymous"bs-tooltip="tooltip.title">
<divclass="tour-section-title">Take control of your own security</div>
<divclass="tour-section-description">
The nature of machine images is that they often contain keys and passwords. We're pretty proud of the <ahref="/security/">security</a> of our hosted offering, but we recognize that there are situations, such as compliance or auditing, where you must control your own end to end security. Quay.io Enterprise Edition runs in your own data centers, inside your firewall.
<divclass="tour-section-title">Auditing and insight done right</div>
<divclass="tour-section-description">
Our platform has built in logging and insight tools, allowing you to see who performed every action on the contents and access control settings of your repositories. This will help you pass internal auditing and compliance requirements more easily.
</div>
</div>
</div>
<divclass="tour-section row">
<divclass="col-sm-3 enterprise-icon">
<spanclass="fa-stack fa-5x">
<iclass="fa fa-circle fa-stack-2x"></i>
<iclass="fa fa-users fa-stack-1x fa-inverse"></i>
</span>
</div>
<divclass="col-sm-9">
<divclass="tour-section-title">Organize your repositories like you organize your business</div>
<divclass="tour-section-description">
The built in teams and organizations features of Quay.io allow you to finely control how the different teams and projects within your enterprise collaborate on repositories.
</div>
</div>
</div>
<divclass="tour-action">
<ahref="mailto:support@devtable.com?Subject=Enterprise%20Quay.io%20Inquiry"data-title="Email us to find out more."bs-tooltip="tooltip.title">
