LICENSING
What you can and cannot do with HaroFlow
We believe in honest, plain-language licensing. This page answers the questions developers and business owners actually ask before buying. If something isn't covered here, just ask us.
What you own
Project-specific custom code
Business logic and customizations that are specific to your brand, workflows, and operations are yours to use and modify in your deployment.
Your data, forever
Your database, your users, your content. No vendor lock-in, no data held hostage. You can migrate to your own infrastructure at any time.
The right to modify the codebase freely
You can change, extend, or delete anything in your copy of the code. Hand it off to your own team, use AI tools on it, refactor it — entirely up to you.
Transparent scope classification before build
Before implementation, we define which parts are project-specific and which are generic, reusable enhancements in the proposal or statement of work.
Permitted uses
Single product deployment — included in base purchase
One purchase covers one product for one end-use. You can run it in staging, production, and local dev without additional licences.
Deploying for a client — allowed with a per-project licence
Agencies and freelancers can use HaroFlow as the foundation for client projects. Each separate client deployment requires its own licence at the base product price. Contact us for volume pricing if you plan multiple projects.
White-labelling — allowed
You can rebrand the UI, remove all HaroFlow branding, and present it as your own product to your clients. The base components stay under our licence — your clients don't need their own licence to use what you deliver.
Charging your own customers for the product you build
Yes — you can run a paid SaaS, charge a subscription, sell access to the portal you build on top of HaroFlow. You are building a business product, not a demo.
Optional temporary exclusivity for generic features
If needed, you can request a temporary exclusivity period for a generic enhancement before it is added to the base product. Terms are agreed case by case.
Optional full feature buyout
If you need permanent exclusivity for a reusable feature, a buyout can be agreed separately at additional cost.
What we retain (and why)
HaroFlow is built on a generic, reusable foundation — auth, admin panel, user management, and the core API structure. We retain the right to sell this foundation to other customers. We may also include broadly reusable enhancements in the base product unless exclusivity or buyout terms are agreed in writing. This is what allows us to keep standard pricing lower than traditional custom software builds.
You cannot resell or sublicence the base components as a product
You can't take the base HaroFlow codebase and sell it as your own boilerplate or starter kit. That's the only restriction. Everything else — including the business you build on top — is yours.
You cannot open-source the base components
The base product code must remain private. Your custom additions on top of it can be open-sourced if you choose — just not the foundation itself.
Quick reference
Use case
Allowed?
Run one product for yourself
Yes
Build and deploy for a client
Yes — per-project licence
White-label and rebrand
Yes
Run a paid SaaS on top of it
Yes
Modify the code freely
Yes
Get temporary exclusivity on a generic feature
Available by agreement
Buy out a feature for permanent exclusivity
Available by agreement
Resell or sublicence the base kit
No
Open-source the base components
No
Have a specific use case in mind?
If your situation isn't covered above, just ask. We'll give you a straight answer — no legal runaround.