Terms of Service
Last updated: 2026-08-19
These terms cover Flanner Mesh, the hosted service. The flanner client is separate: it is open source under the MIT licence, and that licence governs it, not this page.
1. What this covers, and what it does not
Two different things share the name flanner, and only one of them is covered here.
- The client — the CLI, the MCP server and the local web UI — is open source under the MIT licence. You may use, modify and redistribute it on those terms. It needs no account, and we are not a party to how you use it.
- Flanner Mesh is a hosted service that manages accounts, devices and access for a team. These terms cover that service.
Where the two disagree about the client, the MIT licence wins. Nothing here removes a right that licence grants you.
2. Your account
There is no password. You sign in with a link sent to your email address, and each machine you add holds a key it generated itself. Keeping access to that address, and to those machines, is your responsibility.
You must be able to form a binding contract to open an account, and you must give an address you actually control. If you open an account for an organisation, you confirm you may bind it.
3. Your plans stay yours
We claim no ownership of anything you write. Plan content lives on your machines and syncs between them directly. The service never receives it, so there is nothing here for us to licence, publish or train on, and no clause below should be read as granting us any of that.
What we do hold is described in the Privacy Policy: your email address, your team's membership, the public half of each device key, and a record of administrative actions.
4. Acceptable use
Using the service means following the Acceptable Use Policy. It is short, and it is part of this agreement.
5. Paying
Teams start on a 14-day trial with no card. After that a seat costs $19 per month, or $190 per year, billed in advance.
A seat is a member who has accepted an invitation. Inviting somebody costs nothing until they accept. Seat counts are reconciled as your team changes, so adding people mid-cycle is prorated by our payment provider rather than deferred.
Card details are handled by Stripe. We never see or store them. Taxes are your responsibility unless we are required to collect them.
6. Stopping
Cancel whenever you like, from the billing portal. Cancellation takes effect at the end of the period you have paid for. See the Refund Policy for what is returned.
Nothing local is ever taken away. When a subscription ends, team sync and access management stop. Your plans, their full history, the CLI, the MCP server and the local web UI keep working exactly as before. We do not delete, encrypt, lock or withhold anything on your machines, because we could not: it was never ours to reach.
Workspace roles are kept, so resuming a subscription restores what was there rather than starting over.
7. Suspension
We may suspend an account that breaks the Acceptable Use Policy, does not pay, or is being used in a way that threatens the service for other people. Where the problem can be fixed we will say what it is and give you a chance to fix it first, unless doing so would prolong harm to somebody else.
8. Availability
We do not promise the service will be available at any particular time. There is no SLA on these plans.
One consequence is worth stating plainly, because it is the reason the product is built this way: an outage here does not stop you working. Entitlements are signed and verified offline, so devices keep syncing with each other while we are down, until the entitlement they hold expires.
9. Changes to the service and to these terms
We may change the service. If we remove something you are paying for, or change these terms in a way that materially disadvantages you, we will give notice by email to the address on the account before it takes effect, and you may cancel and receive a refund for the unused remainder.
Routine changes are published here with a new date at the top.
10. Liability
The service is provided as is. To the extent the law allows, Flanner is not liable for indirect or consequential loss, and total liability for any claim is limited to what you paid in the twelve months before it arose.
Nothing here limits liability that cannot lawfully be limited, including for fraud or for death or personal injury caused by negligence.
See also the Disclaimer, which explains what the freshness and review features are and are not.
11. Governing law
These terms are governed by the laws of Kenya, and disputes are subject to the courts there.
12. Contact
Questions about these terms go to support@flanner.io.