StyleOps agreement at a glance
A plain-language summary of the StyleOps customer agreement.
A plain-language summary of the StyleOps Customer Agreement, for convenience. The Agreement and the order form are the contract. If anything here differs from them, they control.
What you are buying §
A license to run StyleOps inside your organization for a year. StyleOps checks your documentation against the Developer Experience style guide and drafts new documentation that follows it. You install it and run it yourself.
What it costs §
The annual fee on your order form, set by the size of your organization. One invoice a year, payable within 30 days. Your own model usage is billed to you by Anthropic and is not part of this fee.
What you own §
Everything you put in and everything that comes out. Your documents, the findings reports, and the drafts are yours. Developer Experience claims nothing in them, asks for no attribution, and takes no license in them.
Drafts are partly written by a language model. They are a starting point, not finished work, and you decide what to publish.
Where your documents go §
Nowhere. StyleOps runs on your computers and in your build system. Your documents, your API keys, and your findings never reach Developer Experience. Model calls go straight from your systems to Anthropic on your own key.
Nothing is hosted, so there is nothing to go down and no uptime promise.
What you can and cannot do §
| You can | You cannot |
|---|---|
| Let everyone in your organization use it, with no seat limit | Resell, share, publish, or sublicense the toolkit or the style guide |
| Let the contractors who write your documentation use it on your documents | Run it on another company’s documents as a service, unless you sign a separate agency addendum |
| Run it in your builds, your continuous integration, and your coding agents | Republish the rules or the word list as a style guide, dataset, or reference of your own |
| Configure it, edit the templates, and add your product vocabulary | Use it to build or train a competing style guide or product |
| Point it at a different style guide | Share your access credentials outside your organization |
What you get during the year §
Every release we publish, including revisions to the style guide, and email support at support@developerexperience.com. We aim to reply within 3 business days. Support covers installing, updating, and using StyleOps, and defects in it. It does not cover writing your documentation, customizing the guide to your house style, or work inside your build system. Those are separate engagements.
Renewal and cancellation §
Your license renews for another year automatically. Either of us can stop that with written notice 30 days before the year ends. If you renew every year without a gap, any price increase is capped at the consumer price index or 7 percent, whichever is higher.
Fees are not refundable, and you cannot cancel partway through a year.
What happens if you stop §
Your access to the release repository ends, and so do updates and support. The copy you already installed keeps working, and you may keep using it inside your organization for as long as you like. There is no license check and no expiry in the software. You stop getting new versions.
If something goes wrong §
StyleOps gives you advice, not a guarantee. It does not certify that a document complies with anything, it can miss problems, and it can flag things that are fine. You are responsible for reviewing its output and for what you publish.
If you ever have a claim against Developer Experience, the most it can be worth is the fees you paid in the previous year. Neither of us is liable to the other for lost profits or other indirect losses.
If someone claims the style guide or the software infringes their copyright, trademark, or trade secret, Developer Experience defends you and covers the result, within the limits in the Agreement.
The legal details §
Washington law, King County courts. The Agreement, the order form, and any signed addendum are the whole deal, and no terms in a purchase order or vendor portal change them.
Read the full Agreement before you sign. This page is a summary and is not part of the contract.