Source-available, honest about it.
Resolvd is licensed under the Functional Source License (FSL-1.1-Apache-2.0). Free to self-host. Free for internal commercial use. Becomes Apache 2.0 two years after each release.
What you can do
-
Self-host for yourself or your team
Run Resolvd on your VPS, homelab, or company hardware. No license fee, no seat cap, no expiration. Internal commercial use is fully permitted.
-
Fork it, modify it, audit it
The source is on GitHub. Read it, patch it, run your patched build. You can keep modifications private.
-
Redistribute under FSL
Share copies as long as the FSL license travels with the code.
-
Use it in client services
Consultants and managed-service providers can deploy and operate Resolvd for clients, as long as the deployment is for the client's internal use — not as a competing hosted SaaS product.
What you can't do (during years 1–2)
-
Reselling Resolvd as a hosted SaaS
Standing up your own "hosted Resolvd" service and charging customers for it would be a competing use. That's the one thing FSL blocks.
-
Embedding Resolvd in a competing commercial product
Bundling our code into something you sell that competes with Resolvd or hosted Resolvd is also a competing use.
After two years, each version converts to Apache 2.0 — at which point even competing-SaaS use of that version is allowed.
How the conversion works.
FSL is time-locked. Every release ages out into Apache 2.0 on its own schedule.
- 1
Day 0 — release published
Version v1.x is released under FSL-1.1. Self-host it free. Internal commercial use allowed. Hosted-SaaS resale not allowed.
- 2
Year 1–2 — non-compete window
During this window only the Resolvd team can offer hosted Resolvd as a service. Everything else is fair game.
- 3
Year 2 anniversary — converts to Apache 2.0
That exact version becomes dual-licensed under FSL + Apache 2.0. From that point forward, it's fully open source. Anyone can do anything Apache permits — including hosting it as a paid service.
Common questions.
Is this open source? +
It's source-available, not OSI-approved open source. The full source is public, you can self-host for free, and the code becomes Apache 2.0 (a fully open-source license) two years after each release. We're deliberately careful with the wording — calling it "open source" today would misrepresent what you can and can't do.
Why not MIT or Apache? +
MIT and Apache let anyone — including large cloud vendors — fork our code, host it as a paid service, and undercut the team building it. FSL keeps the project sustainable by reserving the hosted-service business for us during the non-compete period, while still giving you nearly every freedom MIT does for self-hosting.
Can my company use Resolvd internally? +
Yes. Internal use at a commercial company — including using Resolvd to track tickets for paying customers — is explicitly a Permitted Purpose. The line is whether you're operating Resolvd as a competing product, not whether your company makes money.
What converts to Apache 2.0 after two years? +
Each released version. Two years after we publish a version, that exact version becomes available under Apache 2.0 in addition to FSL. Newer versions stay on FSL until they age out. So the codebase is always converging toward fully open source on a rolling basis.
Can I contribute? +
Yes — pull requests welcome. By contributing, you agree your contribution is licensed under the same FSL terms via the project's DCO (Developer Certificate of Origin) sign-off in commits.
I need a different license for my legal team. Can we talk? +
Yes. If FSL doesn't fit your procurement process, we can discuss a separate commercial license. Reach out at hosted@resolvd.dev.
Read the full license.
The plain-English summary above is not the license. The legally binding text lives in the repo.