Terms
There is no hosted Micaforge to buy, subscribe to or be locked out of. What exists is software under a licence, and whatever you decide to run with it.
Sections 1 to 4 and 8 to 9 describe the project and are true as written. Sections 5 to 7 and 11 are a starting point for an operator running something on top of Micaforge, with the parts only you can decide marked [LIKE THIS].
No lawyer has reviewed this page. If people are going to rely on your service, have one read your version before you publish it. The licence text itself, which is the part that legally binds anybody, is in the repository and is not a template.
1. What this covers
Micaforge is an open-source project. Using it means downloading the source, building it, and running it on a machine you control. There is no account with the project, no subscription, no usage limit and nothing to cancel.
If [OPERATOR NAME] offers other people access to an installation, sections 5 to 7 are the terms of that offer and the operator, not this project, stands behind them.
2. The licence
The server and the dashboard are licensed under the GNU Affero General Public License, version 3. The browser tracker and the SDK packages are licensed under the MIT licence, deliberately, so that embedding them in your pages does not reach your own code.
You may run it for any purpose, commercial or not, for as many sites as you like. You may read, modify and redistribute it. What you may not do is redistribute it without the source, or under a licence that takes those freedoms away from the next person.
3. The network clause, in plain words
The AGPL has one obligation that surprises people, and it is worth stating before it catches you.
If you modify Micaforge and then let people use your modified version over a network, you must offer those users the source of your modified version. Running the unmodified project is not affected. Modifying it for your own internal use is not affected either, until other people are using it across a network.
In practice, for a self-hoster: install it, configure it, use it, and nothing here applies to you. Fork it and offer the fork as a service, and it does.
4. No warranty
The software is provided as is, with no warranty of any kind, express or implied, including merchantability, fitness for a particular purpose and non-infringement. The full text is in the licence, and this paragraph does not soften it.
Concretely: this is pre-release software with no tagged release and no production track record. If you put it in front of something that matters, that is a decision you are making with your eyes open.
5. If you run a service on it
[Delete this section if you do not.] When [OPERATOR NAME] gives other people access to an installation at [ANALYTICS DOMAIN]:
- They must use it lawfully, and not to collect data they have no right to collect.
- They must not attempt to break, overload or gain access beyond their account.
- They must have their own lawful basis for measuring their visitors, and their own privacy notice. Yours does not cover their sites.
- [State what happens on breach: suspension, notice period, appeal.]
6. Data you collect with it
Data collected by an installation belongs to whoever runs it and is subject to their own privacy policy and the law that applies to them. This project never receives it, because a self-hosted build makes no outbound call at runtime.
If you are measuring other people's sites for them, you are probably a processor for them. See the data processing template.
7. Liability
[Your lawyer's wording goes here.] The project's authors accept no liability of any kind for anything done with this software, to the fullest extent the law allows. An operator offering a service will need their own limitation, and in many places cannot exclude liability for death, personal injury or fraud, however the clause is worded.
8. Name and marks
The licence covers the code, not the name. You may say your product is built on Micaforge, or is a fork of it. Do not name a fork in a way that suggests it is this project, and do not imply endorsement that has not been given.
9. Contributions
Contributions are accepted under the same licence as the file they touch: AGPL-3.0 for the server and dashboard, MIT for the tracker and the SDKs. By opening a pull request you confirm you have the right to license your contribution that way. There is no contributor licence agreement to sign, and no copyright assignment.
10. Changes and ending
The project may change, stall or stop. It is open source, so a copy you have already taken keeps working and can be maintained by anybody, which is a large part of why it is licensed this way.
[If you run a service, say how a user ends it, how much notice you give, and how they get their data out.] Micaforge exports to CSV and a self-hosted install can be read directly from ClickHouse, so nobody's data need be trapped.
11. Governing law
[Name the jurisdiction whose law governs your terms and where disputes are heard.] For the software licence itself, the AGPL text applies as written.
12. Contact
For the project: the issue tracker in the repository. For an installation: [CONTACT ADDRESS].