Open source, with nothing held back
Glideworth's planner is open source. The build you can run yourself is the whole product: the hosted service sells convenience, not features.
What is licensed how, and why.
| Part | Licence | Where the text is |
|---|---|---|
| The application: engine, API, MCP server, web app, scripts and docs | GNU AGPL v3.0 only | LICENSE |
| The importers and exporters package (ProjectionLab, CSV, bank files, JSON, report) | MIT | packages/importers/LICENSE |
| Bundled data: market-history series, tax tables, samples | Each source has its own terms | DATA-LICENSES.md |
| Third-party dependencies | Their own licences | THIRD-PARTY-NOTICES.md |
| The Glideworth name and logo | Not licensed by any of the above | TRADEMARKS.md |
Why the AGPL
You may use, study, change and share the planner for any purpose, including commercially. If you distribute a copy you pass on the same licence and the source. The part that differs from the ordinary GPL is the network clause: if you change it and let other people use your modified version over a network, you must offer them your source. That keeps a hosted copy from quietly becoming a closed fork, and it is the licence the project's own hosted service runs under, too.
Why MIT for importers
The importers and exporters are MIT so other software can read and write Glideworth's formats, and the ProjectionLab, CSV and bank-file readers, without taking on the AGPL's network clause. That package depends on the AGPL core, so check with your own lawyer how this affects what you build on it.
"Only" means version 3 and no later version, unless the copyright holders deliberately change the licence (the contributor agreement below is how contributions allow that). Copyright is held by Web Ninja FZCO, a free zone company in Dubai, United Arab Emirates, which runs Glideworth.
No edition, no key, no switch.
The build in the repository is the whole product. There is no separate paid edition, no feature that is switched off unless you pay, no licence key and no usage reporting. Tax-table updates and fixes go into the open repository for self-hosters and the hosted service alike: we never charge for correctness. Code that only the hosted service needs is in the same repository under the same licence, and stays out of the way of a self-hosted install.
If this rule is ever changed for a future feature, the change will be announced in advance and recorded in the licensing file. You can hold the project to that.
The hosted service pays for the project.
Glideworth Cloud is $9 a month or $90 a year, after a30-day trial with no card. It runs the same open-source code for you: servers, backups, updates, and a stable address for your AI assistant. That is the whole business model: convenience, not features. There is no advertising, no sale of data and no paid tier of the code.
| Capability | Self-hosted, free | Glideworth Cloud |
|---|---|---|
| Engine, tax models, Monte Carlo, solvers, explanations, importers and exports | Yes | Yes |
| Owner, editor and viewer sign-ins, share links | Yes | Yes |
| REST API and MCP server | Yes, on your own server | Yes, at a stable HTTPS address with OAuth (planned) |
| Scheduled check-ins and alerts | Yes, through webhooks | Also by email (planned) |
| Tax-table updates and fixes | In the open repository when released; you upgrade | Applied for you |
| Backups | You run them; one command | Automatic and encrypted (planned) |
| Two-factor sign-in | No; passphrase sign-in | Planned |
| Support | Community | Email support (planned) |
How to help, and what a good contribution looks like.
Because Glideworth produces numbers people may act on, correctness and evidence matter more than speed. Bugs and requests go through the issue templates, questions through GitHub Discussions, and larger changes (a new feature, a new package, a schema change) start with an issue, so you do not build something that will not be merged.
Updating or adding a tax year
Open an issue first
Use the tax-rule correction template if you are not sure what has changed.
Use official sources only
The tax authority's published rates and thresholds, the legislation, or the government's own guidance. Not blogs, forums or other calculators. They may point you to the right page.
Record the evidence
In the pull request and in a comment next to each figure: the URL, the document and section or table, and the date you read it. A figure you could not confirm is marked provisional.
State the tax year exactly
For example 2026/27 for the UK or 2026 for the US, and say what happens for later years.
Add test vectors
At least one worked example per changed band, allowance or rule, with synthetic inputs, the expected tax and where it comes from, plus the edges just below, at and just above each threshold.
Update the docs and run the checks
The tax-year table, the list of figures that could not be confirmed, and the country's simplifications. Typecheck, lint, test and build must pass.
The rest of the rules
- Synthetic data only. Never commit real balances, account numbers, names, exports from your own planner or bank, tokens or database files. Pull requests containing real data are closed.
- A new country needs a maintainer who can verify it against official sources, a written list of what the estimate leaves out, and tests. A country nobody can verify will not be merged.
- The self-hosted build keeps every feature. No feature reachable only with a key, a payment or a hosted flag, and no telemetry of any kind.
- Machine-generated contributions are allowed, with conditions. A human reviews and can defend every line, runs the tests, and discloses the tool in the pull request. A generator cannot be the source of a tax rate or rule: each figure needs an official source that a person has opened and read. Fully automated pull requests are not accepted.
- A code of conduct applies, and the project is run by very few people, so please be patient.
What you agree to, in plain words.
- You sign once, in your first pull request, by posting a comment. The signature covers your later contributions.
- You keep the copyright in what you write.
- You give the project, and everyone who receives the software, a licence to use, change, distribute and sublicense your contribution, and a patent licence for the claims your contribution necessarily infringes.
- You also let the project owner relicense your contribution under other terms, including later versions of the same licence and proprietary or commercial ones. That is the reason the project asks for an agreement at all, and you should be comfortable with it before signing. The agreement also carries a written promise that your contribution always also stays available under an open-source licence.
- In the MIT-licensed importers package, your contribution is also available to everyone under the MIT terms.
- You confirm the work is yours to give, that it contains no real financial data, and that you reviewed anything machine-generated. If an employer may own your work, get their permission first.
The name is separate from the code.
The licence lets you copy, change and host the code. It does not give you the right to use the Glideworth name or logo, so people can always tell the real service from a copy, especially one that holds their financial plans. You may say your project is based on, a fork of, or compatible with Glideworth, write about it, run it for yourself under any hostname, redistribute unmodified official releases, and link to the official site. You may not name a product, service, domain or account Glideworth (or something confusingly similar), use the logo, run a service that presents itself as Glideworth or as endorsed by it, or suggest endorsement that does not exist. Forks and hosted copies should choose their own name and say they are unofficial. The policy is the owner's statement of how it will treat uses of the name, it has not been reviewed by a lawyer, and no trademark has been registered yet.
Where the numbers come from.
Some files in the repository are data rather than code: historical return and inflation series, tax tables, and synthetic samples. They come from public sources with their own conditions, recorded source by source in the data-licence file, with the attribution each requires. The AGPL does not replace those conditions.
- Tax tables are taken from official sources where possible, for stated tax years, and figures that could not be confirmed are marked provisional. Reuse terms differ by country.
- Market history: US stock, bond and bill returns come from Aswath Damodaran's published series and US inflation from the US Bureau of Labor Statistics. The UK history is being replaced with an openly licensed set, built from openly licensed public sources.
- Samples are synthetic. Nothing real ships with the code.
The data-licence file was written from an audit on 2026-11-16. It lists a few sources whose terms are still to be settled, or that will be replaced, and says which. If you redistribute or host the software, follow the terms it lists. See also Monte Carlo for what the history covers.
Licence questions.
Can I use Glideworth at work, or for clients?
Yes. The AGPL lets you use it for any purpose, including commercially. Running an unmodified copy for yourself, your family or your company needs nothing further. If you modify it and let other people use your modified version over a network, you must offer them its source.
Can I embed it in closed-source software?
Not under the AGPL. Software that only reads and writes Glideworth's file formats can use the MIT-licensed importers package, though that package depends on the AGPL core, so check with your own lawyer how that affects what you build. Commercial licensing is a question for the project; no commercial terms are published.
Could the self-hosted build lose features later?
The stated rule is that the self-hosted build is the whole product. If that rule is ever changed for a future feature, the change will be announced in advance and recorded in the licensing file. Code that only the hosted service needs, such as billing, lives in the same repository under the same licence.
Can I run my own hosted copy for other people?
Yes, under your own name and brand, following the AGPL and publishing your changes. You may not present it as Glideworth.
Read it, run it, or let us run it.
Self-hosting is free. The hosted service funds the work.