License

FIM One Source Available License v1.2 — what you can and cannot do with the software.

FIM One is distributed under the FIM One Source Available License v1.2. This is not an OSI-approved open source license. The source code is publicly available, but certain commercial uses are restricted.

If your use case falls outside the permissions below, contact us for a commercial license.

Quick Summary

Permitted

Use case	Details
Internal use	Use FIM One within your organization and affiliates for internal business operations.
Modification	Modify the source code and create derivative works.
Distribution	Distribute the software (with a copy of the license included).
Embedding in your apps	Use FIM One as a component in your own applications, as long as they are not a Competing Product or Hosted Service.
Single-tenant deployment	Deploy FIM One for a single customer in a dedicated environment, provided branding remains intact and no third-party access is granted.

Restricted

Restriction	Details
Multi-tenant SaaS / Hosted Service	You may not offer FIM One as a service to third parties (e.g., “FIM One-as-a-Service”, managed multi-tenant platforms, or reselling access to FIM One functionality as a cloud service).
Competing product	You may not use FIM One to build or operate a competing agent orchestration, workflow execution, or task planning product.
White-labeling / removing branding	You may not remove, alter, or obscure FIM One branding, logos, copyright notices, or license notices. White-labeling requires a separate commercial license.
Circumventing license checks	You may not remove, disable, or circumvent any license verification, feature gating, or entitlement checks.

Common Scenarios

The license restricts how you deploy FIM One — not whether you charge money for it. Paid and commercial use is fine; only three specific shapes are off-limits without a commercial license: multi-tenant hosted service, white-labeling, and building a competing platform.

Scenario	Allowed?	Why
Run FIM One internally for your own company or team	✅ Yes	Internal use (§2a)
Embed FIM One as the engine inside a product you build and sell — where the product is not itself an agent platform and is not offered as multi-tenant SaaS	✅ Yes	Embedding (§2d), branding kept
Deliver a FIM One-based solution to one client (consulting / systems integration): dedicated, single-tenant, FIM One branding intact, for that client’s own internal use	✅ Yes	Single-tenant exception (§3a)
The same client delivery, but white-labeled under the client’s brand (FIM One branding removed)	❌ No	Needs commercial license (§3c)
Reuse one deployment to serve multiple clients, or any multi-tenant setup	❌ No	Hosted Service (§3a)
Use FIM One to build another agent-orchestration, workflow, or task-planning platform	❌ No	Competing Product (§3b)
Operate a multi-tenant SaaS / “FIM One-as-a-Service”	❌ No	Hosted Service (§3a)

Doing client or consulting work? Delivering a FIM One-based solution to a single client is permitted — but only if all of these hold:

1. The deployment is dedicated to that one client (single-tenant, not shared or reused across customers);
2. What you deliver is a business application, not a reusable agent-orchestration platform (that would be a Competing Product);
3. FIM One branding, logos, and notices stay visible and unaltered.

The most common trip-up is white-labeling — clients often want the solution under their own brand. The moment you remove or hide FIM One branding, you need a commercial license. Multi-tenant reuse and competing-platform builds are the other two hard lines.

Key Terms

• Hosted Service — Any service that allows third parties to access the Software’s functionality over a network (SaaS, PaaS, API services, managed deployments).
• Competing Product — Any product providing agent orchestration, agent runtime, workflow execution, or task planning capabilities substantially similar to FIM One.
• Derivative Works — Any work based on or derived from the Software, including modifications, extensions, and adaptations.

Commercial Licensing

If your intended use is restricted by this license, commercial licenses are available for:

• Multi-tenant SaaS and hosted service deployments
• White-labeling and OEM distribution
• Other use cases not covered by the source available license

Contact: [e-mail] or open a discussion on GitHub.

Full License Text

This page is a summary for convenience and does not replace the actual license. For the complete legal text, see LICENSE on GitHub.