License FAQ

Yes. Internal business use is a permitted purpose under the license, and a paid key is not needed just because a company uses Community internally. The only excluded purpose is offering others a product that competes with Opfield.

The limits are checked only when you add a server, a user or a permission group. Servers, users and groups that already go over them, for example after a paid plan ends, keep working and are never deleted or disabled.

Yes. Every plan, Community, Personal, Business and Enterprise, can be self-hosted. A paid key unlocks features on an installation you run. Managed cloud, where we run the control plane for you, is an optional add-on to a paid plan.

The Opfield source is public under the PolyForm Perimeter License 1.0.1. It lets you use, change and share the software for any purpose except providing others with a product that competes with Opfield. It is a source-available license, not an OSI-approved open-source license.

Running Opfield for your company, in production too; changing the code and building on it; and sharing copies, as long as everyone who gets one also gets the license terms and the required copyright notice. It also includes a patent license from the licensor, which ends for anyone who claims in writing that the software infringes a patent.

Providing others with a product that competes with Opfield. You may not sublicense or transfer your license either. Everything else is a permitted purpose.

A product competes if you use Opfield to market it as a substitute for Opfield’s functionality or value, whether it is sold or free, offered as software or as a hosted service, or ported to another platform or language. A hosted Opfield-style service for others, a white-label version or a fork offered as an alternative would compete. Running your own products on Opfield does not, even when you sell those products.

The first time you are notified in writing, your license continues if you come into full compliance and take practical steps to correct past violations within 32 days.

The Opfield core is public on GitHub at github.com/opfield/opfield, together with the license texts. Paid features come as a separately signed commercial core that a licensed installation downloads and verifies; its source becomes public under the MIT License if the Product Continuity Grant takes effect.

A Personal, Business or Enterprise key unlocks that plan’s features and limits for one active Opfield installation at a time. It does not narrow what the PolyForm Perimeter license already allows. Paid keys follow the Opfield Paid Key Terms.

Nothing stops. Paid features stay on for a grace period after the expiry date: 24 hours on Personal, 3 days on Business, 7 days on Enterprise. After that, everything you already run keeps working, including workloads, routes, databases, backups and failover. Only creating paid resources and changing their configuration is blocked until you renew, and SIEM forwarding and external registry access pause. Renewing restores everything without rebuilding anything.

A paid installation keeps its plan for 100 days after its last signed license state, never past a known expiry date. Community installations keep running while the service is unreachable.

Revocation, moving the key to another installation and deactivation have no grace period: the after-grace rules apply at once, and running workloads still keep working. A key revoked for a breach of its terms, fraud, a chargeback or a refund also loses its continuity rights.

Yes, in two forms. Paid keys, on the Paid Key Terms, unlock paid features on your own installation. Uses that PolyForm Perimeter excludes, such as OEM, white-label, resale or a competing hosted service, need a separate written agreement with the licensor; an ordinary key does not grant them. Talk to us about those.

An irrevocable grant that comes with every Opfield release, so that you are never left with software you cannot run if Opfield stops being provided.

At the first of three events: 12 months in a row with no new release while the license service is unavailable; a published notice that Opfield has reached its end of life; or the licensor’s death or legal incapacity. Nothing else starts it.

The source code of the last release, including the commercial core, becomes available to everyone under the MIT License and is published within 90 days. Anyone holding a key that is valid at that moment also keeps a perpetual, royalty-free license to use and self-host that release for their plan, and may run it without the license service.

Updates, support, trademarks, names and logos. Third-party components keep their own licenses.