Terms of Service

This page outlines the terms of service and use of Gruntwork’s products and services.

It’s important to understand these Terms of Service, as they define your rights and our rights in our relationship. But legalese is not always easy to understand, so we’ve provided “plain English” summaries on the left side of the page to help you understand the official legal language on the right side of the page. Remember that we’re providing you these summaries for informational purposes only. Our actual Terms are the ones on the right under "Legalese" and will apply if we ever need to work through any issues.

Last Modified: September 20, 2018

Need to modify these terms?

Modifying these Terms of Service requires an "Enterprise Subscription" with us. For details, see How can I modify these Terms of Service? in our FAQ.

Translate legalese to human-friendly
Plain English
Legalese

By using Gruntwork products and services, you agree to these Terms of Service and our Privacy Policy.


General Terms

1. Updates to these Terms

We might update these Terms of Service at some point, and if we do, we'll proactively notify you about it.

2. Authorized Users

An Authorized User is a human or machine user that accesses our private repos, training materials, or support services. Email support@gruntwork.io to add/remove users.

3. Additional Terms for the Services

Our individual products and services each have their own supplemental terms. Scroll down to see them!

4. Compensation and Invoicing

All our pricing is published at https://gruntwork.io/pricing, and we don't charge any hidden fees. We won't change the price you pay for our services unless:
(1) we announce new pricing, AND
(2) you ask us to apply the new pricing to your next renewal period.

When you submit your order, we'll immediately charge you a $500 initial deposit, regardless of the services you ordered. Soon after, a Grunt will review your order, and once it's approved, we'll charge your credit card any remaining amounts you owe for your first month of service.

Going forward, we'll bill you automatically by credit card on the same day of the month that we approved your order.

If you're late with your payments, you'll owe us a late fee and have to cover our costs of collecting from you.

5. Term and Termination

We have "master terms" that cover all our products and service, plus each product or service has its own additional terms. You can cancel individual products or services without canceling other products or services or these master terms.

You can terminate these master terms any time with 30 days' notice (or, if we fail to live up to this agreement, with 14 days' notice), but keep in mind that the specific product or service you ordered may have a different term. For example, the Gruntwork Subscription has an annual subscription.

If you do terminate, you'll still owe us any amounts you owed us before terminating.

6. Intellectual Property Rights

You can do anything you want with our code and training as long as only Authorized Users access it and you use it for your company only. In particular, you cannot share our code or training with another company, resell it, publish it as open source, or try to sub-license it.

Each person on your team who accesses our code, training, or support must be an Authorized User. For example, we don't allow the use of a single GitHub profile that's shared by multiple individuals.

Note that, per Gruntwork Subscription / Section 1.5, our license allows you to keep using the code even if you cancel! Just make sure that you never directly compete with us (per section 12).

We give you a very permissive license to the code, but we remain the official owners of it.

We plan to share this code with other customers just like you!

Anything you do with our code in your own code repos is your intellectual property and we will not have any rights to it.

But if you find a bug in our code or see an opportunity for an improvement, you might want to contribute some code back to us. If you do that, we'll want to share that code with all our customers. So if you open a Pull Request on one of our GitHub repos, we'll own the code you submit.

Some of the code in our library contains open source tools that use a "copyleft" license like GPL (e.g. curl). We won't modify these tools in such a way that we trigger a "viral" obligation that requires our code (or your derivative works from our code) to be released as GPL.

In section 6.8, we make a commitment to you not to modify any open source code to trigger a "viral" obligation.

Here, we ask you to do the same. In practice, this means that if you modify our code, you can't modify any GPL code that we distribute with the code. For example, we use curl in many of our bash scripts. If you need to make a change to how we use curl, don't modify curl itself because the GPL license on curl will then require that all the code that uses curl be made GPL as well.

TL;DR: Don't modify source code written by a third party when you submit a Pull Request to us.

7. Confidentiality

We won't share any confidential information about you, and you agree not to share any confidential information about us, including our code.

We'll each treat each other's confidential information at least as carefully as we treat our own.

This is a pretty typical definition of Confidential Information, and what's specifically not considered Confidential Information.

If a government body tells either of us we have to disclose the other's confidential information, we'll do it, but we'll make sure to update the other party on what happened.

8. Limited Liability

9. Indemnifications

If someone else sues us or has any other claim against us for something that's really your fault and not ours, you'll defend and cover us.

If someone else sues you because our code or services infringe on their intellectual property rights, we'll defend and cover you.

10. Representations and Warranties

You are stating to us that you can enter Into this agreement and that you are not violating any other agreements or the law by doing so.

We'll do a good job with our services to you, and we won't violate any other agreements or the law in providing them.

We are not stating anything else to you about the quality of our services beyond what we say in section 10.2.

11. Independent Contractor

We're not going to become an employee of yours, but we are grateful to become your vendor!

12. Use of Services to Compete

If you compete with us by selling reusable infrastructure modules, we will immediately terminate your license.

13. Force Majeure

If an earthquake or some other kind of major crisis occurs and we can't deliver our services to you, you can't consider that a breach of contract, as long as we deliver on our commitment to you as soon as we reasonably can.

14. Notices

An official notice under this agreement can be sent by personal delivery, registered or certified mail, overnight courier, or email.

15. Assignment

You can't assign this agreement to someone else, but if you're acquired by or merged with another company, the agreement will transfer to the new company.

16. Governing Law and Dispute Resolution

If we have a dispute, we'll attempt to settle it directly with each other for at least 30 days. If that fails, either of us can bring a court action in the state of Delaware, which is generally considered to have well-defined business laws.

17. Miscellaneous

This agreement overrides any other verbal or other written agreement we might have, unless we have an existing Master Services Agreement, in which case this agreement only adds to to the Master Services Agreement but does not take away anything.


Gruntwork Subscription Terms

This attachment was last updated on July 15, 2018. Unless otherwise defined in these Gruntwork Subscription Terms, capitalized terms will have the meaning given to them in the Terms.

1. Term and Termination

The Gruntwork Subscription is a 12-month subscription, and renews for 12 months at a time.

If you terminate this agreement before the term ends, you'll have to pay us for the full remaining term.

If you terminate this agreement, we'll make sure you have access to the services you purchased for the remainder of the term.

After you terminate, you'll still have the full rights we grant you in section 6.1 of the master terms to any forks of our code, and any derivative works you create from those forks.

2. Payment Terms

Although this is a 12-month contract, we'll bill you by credit card on a monthly basis.

3. Included Features

See https://gruntwork.io/training for additional details.

We'll notify you when we publish a new blog post at https://blog.gruntwork.io that we think you'll find relevant.

If you need support, post your questions to https://community.gruntwork.io.

4. Disclaimer Regarding Software Updates

We'll take responsibility for updating our code, but it's your responsibility to deploy those updates to your infrastructure.


Dedicated Support Terms

This attachment was last updated on July 15, 2018. Unless otherwise defined in these Dedicated Support Terms, capitalized terms will have the meaning given to them in the Terms.

1. Term and Termination

Dedicated support is offered on a month-to-month basis.

2. Payment Terms

We will bill you by credit card on a monthly basis.

3. Included Features

This section lists what's included with Dedicated Support. For more information, see https://gruntwork.io/support.

We'll provide support via email or a shared Slack channel.

If needed, we'll schedule a real-time chat.

We do not provide 24/7 coverage or emergency support. There may be days like Christmas or New Year's when no one is available for support inquiries, but we'll let you know in advance if such a day will occur.

Otherwise, we'll respond within 1 business day to your inquiries.

We'll notify you about urgent security alerts when they occur via our newsletter.


Reference Architecture Terms

This attachment was last updated on July 15, 2018. Unless otherwise defined in these Reference Architecture Terms, capitalized terms will have the meaning given to them in the Terms.

1. Term and Termination

Once you sign up for the Reference Architecture, we don't offer a refund (unless we fail to deliver what we said we would).

2. Payment Terms

We'll charge you upfront for the Reference Architecture.

3. Included Features

This section lists the features included in the Reference Architecture. For more information, see https://gruntwork.io/reference-architecture.


Gruntwork Houston Terms

This attachment was last updated on September 17, 2018. Unless otherwise defined in these Gruntwork Houston Terms, capitalized terms will have the meaning given to them in the Terms. You may only access and use Gruntwork Houston (“Houston”) if you have a current and valid Gruntwork Subscription.

1. Term and Termination

You can use Gruntwork Houston while you have an active Gruntwork Subscription.

You can terminate these Houston terms at any time with 15 days' notice.

We can only terminate your right to use Houston if you don't pay us on time, you breach these Terms of Service, you declare bankruptcy, or we think your use of Houston is a legal or security threat.

If either Gruntwork or you terminates your right to use Houston, you have to stop using it completely.

Houston sits on top of other tools like GitHub, Jenkins/CircleCI, and AWS. So if either Gruntwork or you terminates your right to use Houston, you will still have access to all those tools and their data. You'll even have access to any data that Houston created, but you won't be able to access that data via a Houston UI or API.

2. Payment Terms

3. Included Features

To learn more about Houston, see https://gruntwork.io/houston

One feature of Houston allows you to authenticate to AWS, VPN, and SSH using an Identity Provider of your choice such as Okta, OneLogin, Google, or Active Directory.

We will make periodic updates to Houston available, but it will be your responsibility to apply those updates.

4. Customer Responsibilities

Some Houston features like "SSH with Houston" will only work if you configure your environment correctly.

Houston runs in your own AWS account, so any user that has admin privileges to that account will have the ability to hack Houston's security measures. Therefore, it's your responsibility to limit access to the AWS account where Houston runs.

Houston is designed to trust your Identity Provider, so if your Identity Provider is hacked, Houston will not know the difference. Therefore, it's your responsibility to secure your Identity Provider.

5. Additional Provisions

You cannot modify Houston or use Houston source code to create your own new intellectual property.

Any information you create with Houston is owned by you, and we can only use that data to operate Houston for your company. However, if we anonymize that data, we may use it to help provide valuable services to other customers like community insights.

If your users use an old version of Houston, have network issues, try to abuse Houston, or modify Houston in an unauthorized way, Gruntwork will not be liable for the consequences.

We will make a reasonable attempt to secure Houston!

Houston is not designed to store personally identifiable information such as Social Security Numbers, so you should not use Houston to submit or collect such information.

If you give us ideas on how to improve Houston, we have the right to use those ideas to improve Houston.