Vireon DynamicsLiminal AIFSL-1.1-MIT · free to use
License

Functional Source License 1.1, MIT Future License

FSL-1.1-MIT applies to the Liminal harness and related source in the liminal-ai repository. Copyright 2026 Vireon Dynamics.

Important

Plain-language summary only

This page summarizes the LICENSE file in plain language. It is not legal advice. If anything here conflicts with the repository LICENSE, the LICENSE file controls. For commercial launches that might be a Competing Use, or for a different grant, contact Vireon Dynamics before you rely on this summary.
What it is

Fair source, not OSI open source

FSL-1.1-MIT is a fair-source / source-available license: you get readable source and broad use rights, but it is not an OSI-approved open source license because competing commercial products are restricted until each version converts to MIT.

Liminal is free to download and use for permitted purposes. You can read, run, and modify the source on your own machine. The license is designed to allow broad internal and educational use while preventing harmful free-riding: shipping a competing commercial substitute built on this codebase.

Summary

What this means in practice

Commercial work inside your company is allowed when you use Liminal internally (not offering it to others as a competing product). Non-commercial education and research are explicitly permitted.

Future license: two years after we publish a given version, that version also becomes available under the MIT License automatically (Grant of Future License in the full text). For each version (typically a release tag on the public liminal-ai repository), the two-year MIT clock starts on the date we first publish that version under these terms—not on the date you install or fork.

Patents: use for a permitted purpose includes a patent license from us where necessary; if you assert that the Software infringes your patents, that patent license ends immediately.

Permitted

Permitted purposes (examples)

  • Internal use on your machines and networks — including for-profit work inside your organization
  • Learning, research, and non-commercial education
  • Building on Liminal for your own workflows when the result is not a Competing Use
  • Professional services that help a licensee use Liminal under this license (consulting, integration, support)
  • Forking and modifying the code for permitted purposes, subject to redistribution rules below
Restrictions

Competing use (not permitted)

  • A commercial product or service that substitutes for Liminal
  • A commercial offering that substitutes for another Vireon product built on Liminal that existed when that version was published
  • A commercial product or service with the same or substantially similar functionality as Liminal

Examples that are usually not permitted:

  • Selling or SaaS-hosting a general-purpose coding agent built substantially from this codebase for third parties
  • White-labeling Liminal as your own commercial agent product without a separate agreement
Redistribution

If you share copies or derivatives

  • You may redistribute copies, modifications, and derivatives only if you include a copy of or link to the LICENSE and keep copyright notices intact
  • Recipients get the same FSL terms (and the same future MIT grant per version) — you cannot relicense under stricter or competing terms alone
  • Trademark use is limited: you may show license details and identify Vireon Dynamics as the origin, but not use our product or company marks without permission
Other software

Third-party dependencies

Liminal depends on many npm packages under their own licenses (often permissive open source). Those licenses apply to those components only; they do not change the FSL terms for Vireon's Liminal source code in the liminal-ai repository.

Questions

Enterprise & competing use

Building something that might be a Competing Use, or need a commercial license, warranty, or different grant for your organization? Contact Vireon Dynamics before you rely on this summary for a product launch. We can discuss alternative licensing for qualified use cases.

Authoritative text: LICENSE in the repository · Template reference: fsl.software