-
+
- 5 private repositories +
- Unlimited public repos +
-
+
- 30-day free trial +
-
+
- 10 private repositories +
- Unlimited public repos +
- Team-based permissions +
-
+
- 30-day free trial +
-
+
- 20 private repositories +
- Unlimited public repos +
- Team-based permissions +
-
+
- 30-day free trial +
-
+
- Unlimited public repos +
- Team-based permissions +
-
+
- 30-day free trial +
-
+
-
+ Continuous Integration
+
Build your containers in response to git pushes: GitHub, BitBucket, Gitlab and others
+
+
+ -
+ 30-Day Free Trial
+
Your first 30 days are free on Quay. Test it out and start building containers!
+
+
+ -
+ Public Repositories
+
Provide a public download page for your container. The best part, they're free!
+
+
+ -
+ Robot Accounts
+
Create credentials designed for deploying software automatically.
+
+
-
+
-
+ Teams
+
Teams can collectively have access to manage specific repositories on your account.
+
+
+ -
+ SSL Encryption
+
Transit between Quay and your servers is secured automatically.
+
+
+ -
+ Logging & Auditing
+
Auditing is essential for everything in your CI pipeline. Actions via API and UI are tracked.
+
+
+ -
+ Invoice History
+
Download past invoices for your billing team or purchasing department.
+
+
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 credientials. 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
+ + Can I change my plan? + +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.
+ + Do you offer special plans for business or academic institutions? + +Please contact us at our support email address to discuss the details of your organization and intended usage.
+ + Can I use Quay for free? + +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!
+ + What types of payment do you accept? + +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.
+-
-
- Can I use Quay for free? -
- 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! + +
- Does my plan have secure communication? -
- Yes! All plans provide secure communication to and from Quay via SSL. +
- 30-day free trial +
- Support via ticket +
- Unlimited repos, users and teams +
- No dedicated builders +
- No geo replication +
- What types of payment do you accept? -
- 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. - -
- Can I change my plan? -
- Yes, you can change your plan at any time and your account will be pro-rated for the difference. -
- Do you offer special plans for business or academic institutions? -
- Please contact us at our support email address to discuss the details of your organization and intended usage. -
- 30-day free trial +
- Support from 9 AM - 5 PM PT +
- Unlimited repos, users and teams +
- Up to 5 dedicated container builders +
- Geo replication between 3 regions +
- 30-day free trial +
- Support from 9 AM - 5 PM PT +
- Unlimited repos, users and teams +
- Up to 25 dedicated container builders +
- Geo replication between 5 regions +
-
+ Enterprise Authentication
+
Integrate to your existing identity infrastructure: LDAP, Keystone, Tectonic Identity and more
+
+
+ -
+ Flexible Storage Backends
+
Store your container images on Amazon S3, OpenStack SWift, Google Cloud Storage, or directly to disk.
+
+ -
+ Continuous Integration
+
Build your containers in response to git pushes: GitHub, BitBucket, Gitlab and others
+
+
+ -
+ 30-Day Free Trial
+
Your first 30 days are free on Quay. Test it out and start building containers!
+
+
+ -
+ Public Repositories
+
Provide a public download page for your container. The best part, they're free!
+
+
+ -
+ Robot Accounts
+
Create credentials designed for deploying software automatically.
+
+ -
+ Teams
+
Teams can collectively have access to manage specific repositories on your account.
+
+
+ -
+ SSL Encryption
+
Transit between Quay and your servers is secured automatically.
+
+
+ -
+ Logging & Auditing
+
Auditing is essential for everything in your CI pipeline. Actions via API and UI are tracked.
+
+
+ -
+ Invoice History
+
Download past invoices for your billing team or purchasing departement.
+
+ - Fits into your existing deployment +
- Runs anywhere a container does +
- Orchestration is up to you +
- Deployment is consistent between regions +
- Machine failure is handled automatically +
- Orchestration is handled by the cluster +
-
Fees and Payment Terms
-
In exchange for your rights to the Services, you will pay to CoreOS the Subscription Fees. The Subscription Fees do not include taxes, and the Subscription Fees are payable in advance in accordance with your Quay.io Plan.
+In exchange for your rights to the Services, you will pay to CoreOS the Subscription Fees. The Subscription Fees do not include taxes, and the Subscription Fees are payable in advance in accordance with your Quay Plan.
Unless CoreOS states otherwise, all payments must be made (a) in U.S. Dollars; and (b) by payment card via an authorized CoreOS payment processor. If you pay via a payment card, you hereby (i) authorize CoreOS (or its authorized payment processor) to make automatic recurring charges to your designated payment card number in the applicable amount of the Subscription Fees on an annual or monthly basis (as applicable) for the duration of the Subscription Period, (ii) represent and warrant that you are authorized to use and have fees charged to the payment card number you provide to CoreOS, and (iii) understand that you may withdraw this consent by emailing CoreOS at support@quay.io. Accounts can be canceled at any time in the Plan and Usage section of your Account Settings. No refunds will be issued (unless expressly stated otherwise).
Notwithstanding any terms to the contrary in these Terms, CoreOS, at its sole discretion, may modify its pricing during any Subscription Period and such modifications will be effective as of the directly subsequent Subscription Period.
Interest on any late payments will accrue at the rate of 1.5% per month, or the highest rate permitted by law, whichever is lower, from the date such amount is due until the date such amount is paid in full. You will be responsible for, and will pay all sales and similar taxes on, all license fees and similar fees levied upon the provision of the Services provided under these Terms, excluding only taxes based solely on CoreOS’ net income. You will indemnify and hold CoreOS harmless from and against any and all such taxes and related amounts levied upon the provision of the Services and any costs associated with the collection or withholding thereof, including penalties and interest.
diff --git a/util/invoice.tmpl b/util/invoice.tmpl index 68228886f..1e29cdadb 100644 --- a/util/invoice.tmpl +++ b/util/invoice.tmpl @@ -3,10 +3,10 @@- 
+
- Quay.io
+Quay
CoreOS, Inc
https://coreos.com
diff --git a/util/useremails.py b/util/useremails.py index fb562fde4..f7b319a13 100644 --- a/util/useremails.py +++ b/util/useremails.py @@ -147,7 +147,7 @@ def send_org_invite_email(member_name, member_email, orgname, team, adder, code) def send_invoice_email(email, contents): # Note: This completely generates the contents of the email, so we don't use the # normal template here. - msg = Message('Quay.io payment received - Thank you!', recipients=[email]) + msg = Message('Quay payment received - Thank you!', recipients=[email]) msg.html = contents mail.send(msg)
-
+
-
-
Run Quay.io Behind Your Firewall
-
- +
- 
+ -
+
-
+
-
+
-
+
-
+
How can I run Quay Enterprise?
+ +Quay Enterprise is delivered as a set of containers that is self-managed, or run it as an application on top of a Tectonic cluster. Quay Enterprise is included for free with all Tectonic clusters.
+ +Running as a single container excels for the Basic plan. Quickly get started during your trial.
+ +For production setups, Tectonic provides a level of consistency between your regions, allows Quay to share the same identity infrastructure powering Tectonic, provides easy scaling of your builders, and seamless recovery from a machine failure.
+ +
+ Deploy Individual Containers
+ -
+
+ Deploy on Tectonic
+ -
+
How is Quay Enterprise different than Quay?
+ +Quay Enterprise is closely related to Quay, but runs on your own hardware or in your cloud environment. Running the application yourself is more secure and is more performant when running on the same cluster as your containerized applications.
+ +When running behind your firewall, Quay Enterprise can connect to private Git repositories, LDAP insfrastructure, and more.
+ +Additional FAQs
+ + Is there a free trial for Quay Enterprise? + +Yes, the first 30 days of usage are free, and then your license will be automatically converted to the standard rate. We’ll send you an email before that happens as a reminder.
+ + What types of payment do you accept? + +Quay Enterprise is billed monthly through your Tectonic account. Major credit cards are accepted and invoices are available by request.
+ + Can I pay annually? + +Yes, you can annually. During the purchase process, you can choose between using a credit card or paying via an invoice.
+ + Can I change my plan? + +Yes, you can change or cancel your license at any time via your Tectonic account.
+
+ To start your trial, please choose an option:
+
+ 
+ Quay.io Security
-We understand that when you upload one of your repositories to Quay.io that you are trusting us with some potentially very sensitive data. On this page we will lay out our security features and practices to help you make an informed decision about whether you can trust us with your data.
+Quay Security
+We understand that when you upload one of your repositories to Quay that you are trusting us with some potentially very sensitive data. On this page we will lay out our security features and practices to help you make an informed decision about whether you can trust us with your data.
SSL Everwhere
-We expressly forbid connections to Quay.io using unencrypted HTTP traffic. This helps keep your data and account information safe on the wire. Our SSL traffic is decrypted on our application servers, so your traffic is encrypted even within the datacenter. We use a 4096-bit RSA key, and after the key exchange is complete, traffic is transferred using 256-bit AES, for the maximum encryption strength.
+We expressly forbid connections to Quay using unencrypted HTTP traffic. This helps keep your data and account information safe on the wire. Our SSL traffic is decrypted on our application servers, so your traffic is encrypted even within the datacenter. We use a 4096-bit RSA key, and after the key exchange is complete, traffic is transferred using 256-bit AES, for the maximum encryption strength.
Passwords
-There have been a number of high profile leaks recently where companies have been storing their customers' passwords in plain text, an unsalted hash, or a salted hash where every salt is the same. At Quay.io we use the bcrypt algorithm to generate a salted hash from your password, using a unique salt for each password. This method of storage is safe against rainbow attacks and is obviously superior to plain-text storage. Your credentials are also never written in plain text to our application logs, a leak that is commonly overlooked.
+There have been a number of high profile leaks recently where companies have been storing their customers' passwords in plain text, an unsalted hash, or a salted hash where every salt is the same. At Quay we use the bcrypt algorithm to generate a salted hash from your password, using a unique salt for each password. This method of storage is safe against rainbow attacks and is obviously superior to plain-text storage. Your credentials are also never written in plain text to our application logs, a leak that is commonly overlooked.
Access Controls
-Repositories will only ever be shared with people to whom you delegate access. Repositories created from the Docker command line are private by default and repositories must subsequently made public with an explicit action in the Quay.io UI. We have a test suite which is run before every code push which tests all methods which expose private data with all levels of access to ensure nothing is accidentally leaked.
+Repositories will only ever be shared with people to whom you delegate access. Repositories created from the Docker command line are private by default and repositories must subsequently made public with an explicit action in the Quay UI. We have a test suite which is run before every code push which tests all methods which expose private data with all levels of access to ensure nothing is accidentally leaked.
Data Resilience
-While not related directly to security, many of you are probably worried about whether you can depend on the data you store in Quay.io. All binary data that we store is stored in Amazon S3 at the highest redundancy level, which Amazon claims provides 11-nines of durability. Our service metadata (e.g. logins, tags, teams) is stored in a database which is backed up nightly, and backups are preserved for 7 days.
+While not related directly to security, many of you are probably worried about whether you can depend on the data you store in Quay. All binary data that we store is stored in Amazon S3 at the highest redundancy level, which Amazon claims provides 11-nines of durability. Our service metadata (e.g. logins, tags, teams) is stored in a database which is backed up nightly, and backups are preserved for 7 days.
+ 
{% block content %}
{% endblock %}
diff --git a/templates/generatedtoken.html b/templates/generatedtoken.html
index a7e493216..5d259aa5a 100644
--- a/templates/generatedtoken.html
+++ b/templates/generatedtoken.html
@@ -1,5 +1,5 @@
- CoreOS Privacy Policy
Last Revised: February 2, 2015
-Welcome to Quay.io from CoreOS, Inc. (“CoreOS”, “we”, “us” or “our”).
+Welcome to Quay from CoreOS, Inc. (“CoreOS”, “we”, “us” or “our”).
This privacy policy explains how we collect, use and disclose information about you when you use any of the websites owned or operated by CoreOS (the “Sites”) and any of the online products and services that link to this privacy policy (collectively, the “Services”) or when you otherwise interact with us. By using any of our Services, you consent to our collection, use and disclosure of your information as described in this privacy policy.
The Services allow users to store, manage, and retrieve container repositories.
We may change this privacy policy from time-to-time. If we make changes, we will notify you by revising the date at the top of the policy and, in some cases, we will provide you with additional notice (such as adding a statement to our homepage or sending you an email notification). We encourage you to review the privacy policy periodically to stay informed about our practices and the ways you can help protect your privacy.
diff --git a/templates/tos.html b/templates/tos.html index b86128256..567f1face 100644 --- a/templates/tos.html +++ b/templates/tos.html @@ -1,7 +1,7 @@ {% extends "base.html" %} {% block title %} -CoreOS Terms of Service
Last Revised: February 5, 2015
-These Quay.io Terms of Service (these “Terms”) apply to the features and functions provided by CoreOS, Inc. (“CoreOS,” “our,” or “we”) via quay.io (the “Site”) (collectively, the “Services”). By accessing or using the Services, you agree to be bound by these Terms. If you do not agree to these Terms, do not use any of the Services. The “Effective Date” of these Terms is the date you first access any of the Services.
+These Quay Terms of Service (these “Terms”) apply to the features and functions provided by CoreOS, Inc. (“CoreOS,” “our,” or “we”) via quay.io (the “Site”) (collectively, the “Services”). By accessing or using the Services, you agree to be bound by these Terms. If you do not agree to these Terms, do not use any of the Services. The “Effective Date” of these Terms is the date you first access any of the Services.
If you are accessing the Services in your capacity as an employee, consultant or agent of a company (or other entity), you represent that you are an employee, consultant or agent of such company (or other entity) and you have the authority to agree (and be legally bound) on behalf of such company (or other entity) to all of the terms and conditions of these Terms.
For the purpose of these Terms, you and, if applicable, such company (or other entity) constitutes “Customer” or “you”.
CoreOS reserves the right to change or modify any of the terms and conditions contained in these Terms (or any policy or guideline of CoreOS) at any time and in its sole discretion by providing notice that these Terms have been modified. Such notice may be provided by sending an email, posting a notice on the Site, posting the revised Terms on the Site and revising the date at the top of these Terms or such other form of notice as determined by CoreOS. Any changes or modifications will be effective 30 days after providing notice that these Terms have been modified (the “Notice Period”). Your continued use of any of the Services following the Notice Period will constitute your acceptance of such changes or modifications. Therefore, you should review these Terms whenever you access the Services and at least every 30 days to make sure that you understand the terms and conditions that will apply to your use of the Services.
@@ -74,7 +74,7 @@