Purchasing and licensing
BuiltForProd products are bought in one of two ways: directly from BuiltForProd, or as a private offer on AWS Marketplace. Either way the repositories are delivered under the PolyForm Internal Use License 1.0.0, with Nexstella as licensor: you may deploy, modify and share the code inside your organization, and you may not resell it, publish it or use it to run managed services for others.
Buying directly
BuiltForProd reaches out to customers, or customers reach out through email or the website. BuiltForProd sends an offer; when you accept it, BuiltForProd sends an invoice and you pay BuiltForProd directly. Onboarding and delivery follow. The billing FAQ answers the common questions about invoices and terms.
Buying through AWS Marketplace
- Log in to the AWS account where you want to pay.
- Request a private offer from BuiltForProd via AWS Marketplace for the product you want to purchase.
- BuiltForProd validates the request and shares a private offer.
- Review and accept the private offer in AWS Marketplace.
- Once accepted, BuiltForProd reaches out to kick off onboarding and delivery.
The benefits of the Marketplace path are the ones AWS gives every Marketplace purchase: you pay with your AWS account, the purchase appears under AWS consolidated billing, AWS discounts apply, the spend counts toward AWS spending commitments, and the purchase supports open source. The AWS Marketplace explainer describes how private offers work.
What is purchased
| Product | What the purchase covers |
|---|---|
| Baseline Tier 1 | The environment deployed by BuiltForProd, the customized repositories and the documentation |
| Baseline Tier 2 | Tier 1 plus any two blueprints, deployed |
| Tier 3 | An additional blueprint for an existing Baseline customer |
| Managed | On-Demand hours (minimum 10), a pre-paid Support SLA year (minimum 100 hours), or Team Augmentation on a 6- or 12-month commitment billed monthly |
The license
Every repository carries the PolyForm Internal Use License 1.0.0 and a copyright notice of Nexstella. The README of each repository summarizes it:
| You can | You cannot |
|---|---|
| Deploy and manage: use the code to deploy, manage and scale your internal cloud infrastructure | Resell or sublicense: sell the code, or any derivative of it, as a standalone product or service |
| Modify: change the variables, resources and logic to fit your internal technical requirements | Distribute publicly: host the code in public repositories |
| Share internally: share the code with employees and contractors working directly for your organization | Use externally: use the code to provide managed services to third-party clients |
| Remove notices: you must retain all copyright notices and license files in the source |
The full terms include the following points:
- Acceptance. You get a license only by agreeing to the terms as strict obligations and conditions.
- Copyright and changes. You may do everything with the software that would otherwise infringe the licensor's copyright, for a permitted purpose, and you may make changes and new works based on it, but you may not distribute the software.
- Patent license. The licensor grants a patent license covering claims you would infringe by using the software; it ends if you claim the software infringes a patent.
- Internal business use. Use for the internal business operations of you and your company is a permitted purpose. "Your company" includes organizations under common control with yours.
- No other rights. The license cannot be sublicensed or transferred and does not stop the licensor licensing others.
- Violations. On a first written notice of violation, your licenses continue if you come into full compliance and correct past violations within 32 days; otherwise they end immediately.
- No liability. As far as the law allows, the software comes as is, without warranty, and the licensor is not liable for damages arising from the terms or the use of the software.
The license text in the repository is authoritative; this page summarizes it. The customized repositories handed over at delivery name your organization as licensee.
What the license means in practice
- Fork, customize and extend the repositories in your own GitHub organization: permitted.
- Give contractors working for you access to the repositories: permitted.
- Run your own workloads, for your own customers, on the platform the code deploys: permitted, since the platform is your internal infrastructure.
- Publish the repositories, sell them, or operate them as a managed service for other companies: not permitted.
The Baseline product page lists what is delivered under this license; the shared responsibility model states what you own from handover.