Skip to content

COMMERCIAL.md

Latest commit

 

History

History
74 lines (53 loc) · 2.66 KB

COMMERCIAL.md

File metadata and controls

74 lines (53 loc) · 2.66 KB
Raw

Commercial use & enterprise licensing

falsify is released under the MIT License. You can use it, modify it, ship it, and fold it into a commercial product without paying anyone. That's not going to change.

This page is for the case where you want something more than MIT gives you — support, SLAs, private patches, a name other than falsify, or a written commercial agreement your legal team can sign.

When to reach out

Contact hello@falsify.dev if you are:

  • Deploying falsify in a SaaS product and want vendor support.
  • Embedding falsify in a regulated environment (healthcare, finance, government) and need a signed SLA or liability agreement.
  • Building a managed falsify-as-a-service offering and want co-marketing or a commercial license that waives MIT attribution.
  • Looking for custom features, private patches, or prioritised bug fixes.
  • Interested in white-labelling the CLI under a different brand.
  • Planning a fork that would re-use the "falsify" name or the chevron logo — see the trademark policy below.

Please include:

  1. Your company and use case (one paragraph).

All commercial engagements are contracted with and invoiced by Falsify OÜ (registry code 17574308, Narva mnt 5, 10117 Tallinn, Estonia). 2. Deployment scale (users, requests/day, internal vs external). 3. What you'd want from a commercial engagement (support, features, branding, etc.).

Response time: usually within 3 business days.

Trademark policy

The authoritative policy is TRADEMARK.md; this is a summary. Where the two differ, TRADEMARK.md governs. The marks are held by Falsify OÜ and are unregistered.

The MIT License covers the source code. It does not cover the "FALSIFY" name or the chevron logo.

You may:

  • Use "falsify" to describe what the software does ("we use falsify internally").
  • Link to github.com/studio-11-co/falsify in docs and blog posts.
  • Mention "falsify" in academic papers with standard attribution.

You may not, without prior written permission:

  • Publish a product, service, or fork using "falsify" (or a confusingly similar name) in its title.
  • Use the chevron logo in marketing for a non-falsify product.
  • Imply official endorsement or partnership.

Forks are welcome under a different name and logo.

Open-source commitment

falsify will remain MIT-licensed. Upstream development happens in the public repo. Commercial licenses coexist with the open-source distribution — they add a signed agreement, they do not remove code from the community.

Contact

Cüneyt Öztürk hello@falsify.dev