Terms & Conditions
Last updated 2026-09-15. This governs purchasing and using a Ferflow license from us.
1. What you're buying
A Ferflow license is a right to run one copy of the Ferflow software, self-hosted on your own infrastructure (on-premise servers, your own cloud account, or any environment you control). We don't host or operate your instance — you deploy it, you administer it, and your data never passes through our servers. This is different from a SaaS subscription: there's no account of ours your data lives in, and no service of ours to depend on for your dashboards to keep working day to day.
2. One serial number, one server
Each order has one serial number, and that serial is registered to the Hardware ID of one server at a time. The license is cryptographically signed for that Hardware ID and runs only there. When the server changes, you move the registration: the new Hardware ID replaces the old one.
- Two self-service moves per order in any 12 months. Sign in to your account, open the order, choose "Move to a new server" and enter the new server's Hardware ID. Each move re-issues the license for the new server and replaces the previous registration.
- A move never changes the term. The new license ends on exactly the same date as the one it replaces.
- Beyond that allowance, if a server failed: contact us. Where a failure is shown, we will re-issue the license for the replacement server.
- A move is for replacing a server, not adding one. Licenses are validated offline, so the previous server keeps running until its term ends; running Ferflow on more than one server at a time requires a license for each.
- You are told when a move is needed. The installer, Ferflow's startup log, and Admin → License each show this server's Hardware ID when it differs from the one the license is registered to.
What changes a Hardware ID
On Linux the Hardware ID is built from the system's machine ID (/etc/machine-id) and the CPU
model. On Windows it is built from the machine's SMBIOS UUID, its MachineGuid and the motherboard serial.
Anything that changes one of those changes the Hardware ID, and needs a move.
| Change | Hardware ID | What to do |
|---|---|---|
| Moving to a different physical server | Changes | Move the license |
| Reinstalling the operating system, even on the same machine | Changes | Move the license |
| Rebuilding, re-creating or cloning a virtual machine (for example from an image or template) | Changes | Move the license |
| Linux: changing to a different CPU model (another instance family or host CPU) | Changes | Move the license |
| Windows: moving the virtual machine to another hypervisor, or anything that issues it a new SMBIOS UUID | Changes | Move the license |
| Windows: replacing the motherboard | Changes | Move the license |
| Adding disk, storage, memory or CPU cores of the same model | Unchanged | Nothing |
| Restarting, operating system updates, Docker updates | Unchanged | Nothing |
| Reinstalling or upgrading Ferflow on the same server | Unchanged | Nothing |
A running Ferflow keeps working after its Hardware ID changes and stops at its next restart, because the
license is checked when Ferflow starts. Planning a change from the first part of this table? Check the new
Hardware ID with the get-hwid script afterwards, and move the license before restarting Ferflow.
Free trials are bound to their serial number rather than to a server, and cannot be moved. To keep a trial installation, place an order and enter the new order's serial in Admin → License.
3. Payment is one-time, not a subscription
Every package (Standard, Business, Corporate) is sold as a one-time, upfront payment for a fixed license term (one month, one year, or a custom term for Corporate) — not a recurring subscription. Nothing auto-renews and nothing auto-charges you. When a term ends, you decide whether to place a new order.
4. All sales are final
We don't offer refunds, and orders can't be cancelled once a license has been issued. Because Ferflow is delivered as a fully-working, unlocked product the moment your license is signed — not a trial or a service that can be "turned off" — there's no partial-use state to refund from. Please confirm the package, term, and target hardware are correct before completing checkout.
5. License terms don't stack or extend each other
Each order issues its own independent license with its own term, starting from the date it's issued. Placing a new order — including one for the same hardware — does not add its term on top of an existing license's remaining time, and does not extend an existing license's expiration date. If you order again before your current license expires, the unused remaining time on the current one isn't carried forward.
6. What happens when a license expires
Ferflow validates its license on every startup, before any of the application's code is even decrypted. An expired (or otherwise invalid) license means the software will not start at all — not a reduced-functionality mode, a read-only mode, or a grace period. Back up your data and plan any renewal before your current term ends if continuous uptime matters to you.
7. Package tiers and what they include
Standard, Business, and Corporate differ in user limits and which features are unlocked (scheduling, SSO, the Manager role, AI-assisted insights, and so on — see the pricing page for the current breakdown). Entitlements are fixed into the license at the time it's issued, based on the package you purchased. Support level (chat, priority, or custom SLA) also follows your package tier.
8. Your data stays yours, and stays with you
Because Ferflow runs entirely on infrastructure you control, we never have access to the data sources, dashboards, or credentials you configure inside your own instance. You're solely responsible for securing, backing up, and maintaining your own deployment, database, and data. If you lose your server or its data without a backup, we have no copy to restore from.
9. Ownership and acceptable use
Purchasing a license grants you the right to run the software under these terms — it does not transfer ownership of the software itself, which remains ours. You agree not to attempt to circumvent, disable, or reverse-engineer the license validation or protection mechanisms, and not to redistribute, resell, or sublicense the software or your license to a third party.
10. No warranty
Ferflow is provided "as is," without warranty of any kind, express or implied, including without limitation warranties of merchantability, fitness for a particular purpose, or non-infringement. We don't guarantee the software will be error-free or meet every requirement of your specific use case.
11. Limitation of liability
To the maximum extent permitted by law, we are not liable for any indirect, incidental, special, or consequential damages arising from your use of (or inability to use) Ferflow, including lost data, lost revenue, or business interruption — even if we've been advised of the possibility. Our total liability for any claim relating to a license is limited to the amount you actually paid for that license.
12. Changes to these terms
We may update these terms from time to time — for example, as the product or our policies evolve. The "Last updated" date above reflects the most recent revision. Continuing to use a license after a change is posted means you accept the updated terms; changes don't apply retroactively to license grants already issued.
13. Governing law
These terms are governed by the laws of Indonesia, without regard to conflict-of-law principles.
14. Contact
Questions about these terms, or about a specific order, go to dilan@ferflow.com or the contact page.