OpenTremor

Commercial licence

Build OpenTremor into a product you sell.

The AGPL already lets you use OpenTremor commercially. A commercial licence is for companies that redistribute it as part of their own product and don't want to take on the AGPL's source-sharing obligations.

The commercial licence is only for redistribution as part of your own product. Using OpenTremor commercially is free under the AGPL.

Terms
Price
From $20kper year
Licence
Annual, non-exclusiveRenewed each year on the then-current terms. Each licence is quoted individually.
The price reflects
How widely you distribute it and how many customers you reachWhich rights you need and for how long · Whether you need support alongside the licence
This page describes the offer, not the rights. What a commercial licence grants is set out in the signed agreement.

Use it, or ship it

Enterprise and a commercial licence answer different questions.

TermEnterpriseCommercial licence
You are…Using OpenTremorShipping OpenTremor to customers
You getSupport, onboarding, a flat billRights the AGPL doesn't give you
Priced onTeam size and support needsDistribution volume and the rights you need
TermMonthlyAnnual, renewable
From$500 / month$20k / year

When you need one

You distribute the OpenTremor server as part of a product you sell.

OEM
You ship OpenTremor as part of your own product and sell it to your customers.
Appliance
You distribute a physical or virtual appliance that includes the OpenTremor server.
Embedded platform
You integrate OpenTremor's server functionality into a proprietary platform.
White-label
You present OpenTremor's functionality as part of your own commercial product.
Proprietary modifications
You distribute modified OpenTremor server components without offering your changes under the AGPL.

When you don't

All of these are already allowed for free under the open source licences.

  • Self-hosting OpenTremor, for any number of people, commercially
  • Modifying it for your own company's use
  • Running it as a hosted service and sharing your modifications
  • Writing your own packs, closed-source included
  • Forking the Apache-2.0 modules: packs, Helm chart, Terraform provider
  • Calling it from your own scripts, CI jobs or agents
What you owe in each case

Tell us what you're building.

Tell us what you're building, how you distribute it, and roughly how many customers it will reach.