OPENOSINT-COMMERCIAL(1) | Commercial Service Agreement | openosint.tech

## NAME

openosint-commercial — optional service agreement for organizations that need a vendor contract, warranty, indemnification, SLA, or priority support on top of the MIT license

## THE MIT LICENSE — FREE FOR ANY USE

OpenOSINT is free and open source under the MIT License for any use — personal, commercial, SaaS, closed-source, academic, everything. No purchase required, ever.

The MIT License already allows:

- Commercial use — selling products, offering SaaS, consulting
- Closed-source and proprietary use
- Modification and redistribution
- Sublicensing

You do not need a commercial plan to use OpenOSINT commercially or in a closed-source product.

## WHY A COMMERCIAL PLAN EXISTS

Commercial plans exist for organizations that need a real vendor relationship — a signed contract, a supplier to pay, written warranties, indemnification language, or a priority-support SLA. These are the things procurement and legal teams require that an MIT-licensed open-source project cannot provide on its own.

Purchasing a commercial plan does not restrict or replace your MIT rights. It is a separate service agreement layered on top of the existing MIT license. Your right to use, modify, and redistribute OpenOSINT under the MIT License is unaffected regardless of whether you purchase a plan.

## FREE VS. COMMERCIAL

| Free (MIT) | Commercial Plan
--- | --- | ---
Personal & academic use | ✓ | ✓
Commercial use | ✓ | ✓
Closed-source / SaaS use | ✓ | ✓
Modification & redistribution | ✓ | ✓
Community support (GitHub Issues) | ✓ | ✓
Written commercial use agreement | — | ✓
License assurance letter | — | ✓
Priority email support | — | ✓
Defined response-time target | — | ✓
Named maintainer contact | — | ✓
Basic indemnification clause | — | ✓
SLA documentation | — | Enterprise
Security & compliance documentation | — | Enterprise
Vendor onboarding paperwork | — | Enterprise
Purchase orders / net-30 invoicing | — | Enterprise

## PLANS

Tier | Price | What you get
--- | --- | ---
Starter | €300 / year | Commercial use agreement + written license assurance letter + email support (best-effort, business days)
Business | €600 / year | Everything in Starter + priority email support with a defined 2-business-day response target, named maintainer contact, basic indemnification clause
Enterprise | €1,000+ / year (custom) | Everything in Business + SLA documentation, security & compliance documentation support, vendor onboarding paperwork, optional purchase-order / net-30 invoicing

Not sure which tier fits? Email and ask — it takes one message to find out.

## GET IN TOUCH

Email commercial@openosint.tech with:

- Subject: `OpenOSINT Commercial — [your organization]`
- Your organization name
- Your use case (what you are building or deploying)
- The tier you are interested in, or “unsure — need advice”
- Any specific compliance or procurement requirements

You will receive a response within 3 business days.

Email commercial@openosint.tech →

## FREQUENTLY ASKED QUESTIONS

Do I need a commercial plan to use OpenOSINT in my company?
No. The MIT License already permits commercial use, closed-source use, and SaaS products with no restrictions. A commercial plan is for organizations whose procurement or legal teams require a vendor contract, warranty, or SLA — not a prerequisite for commercial use itself.

Does buying a plan change the MIT license?
No. The MIT License remains in force. The commercial plan is a separate service agreement layered on top of it. Your open-source rights are unaffected.

Can I use OpenOSINT in a closed-source product without a plan?
Yes. MIT permits closed-source use. No attribution is required either, though it is appreciated.

What currency and payment methods do you accept?
Plans are priced in EUR. Payment methods are confirmed during onboarding — email to discuss.

Can I get a custom quote?
Yes. The Enterprise tier is explicitly custom. Email with your requirements.

Home · Blog · Tools · Cloud API · GitHub
— OpenOSINT — Terms · Privacy · Acceptable Use · Subprocessors