Terms of Service
These terms cover this website and the public demo. The software you download is governed by the MIT licence, which is deliberately more permissive than anything here.
Last updated
1. Scope
By using this website — the marketing pages, the documentation and the public demo — you agree to these terms. If you don't, please don't use it.
Two things are not covered here:
- The UptimeCove source code. Your rights to use, copy, modify and distribute it come from theMIT licence, and nothing on this page narrows that licence.
- Instances other people run. If you're looking at a status page operated by another company, their terms apply, not ours.
2. What you get
A free, no-signup website with documentation and a demo dashboard, plus a public repository you can clone. There is no paid tier, no account to create here, and no service-level agreement.
The demo is a shared sandbox filled with sample data. It may be reset, changed or taken down at any time without notice, and nothing you see there should be treated as durable.
3. Acceptable use
When using this website, don't:
- attempt to gain unauthorised access to the site, its dashboard, its APIs or its underlying infrastructure;
- send automated traffic at a volume that degrades the service for others, or attempt a denial-of-service;
- scrape or reuse content in a way that misrepresents it as your own product or implies an endorsement;
- upload or transmit malware, or use the site to distribute unlawful content;
- remove or obscure copyright and licence notices.
Security researchers are welcome. Please follow thesecurity policyand report privately rather than testing destructively.
4. If you self-host
Running your own instance makes you the operator, with the responsibilities that implies:
- Only monitor endpoints you're authorised to monitor. Pointing a monitor at someone else's infrastructure at a high frequency can constitute abuse, and it is your responsibility, not ours.
- Comply with the terms of your own providers, including Cloudflare's, and with any usage limits on your plan.
- Secure your deployment. Set a strong
ADMIN_TOKEN, keep it and your.dev.varsout of version control, and rotate credentials if they leak. - Handle your users' data lawfully — in particular the email addresses of anyone who subscribes to your status page. See the privacy policy for exactly what is stored.
- Keep your own backups. The maintainers have no access to your database and cannot recover it.
You are responsible for costs your deployment incurs. UptimeCove is designed to fit Cloudflare's free tier, but check intervals, monitor counts and retention are yours to configure and yours to pay for if you exceed it.
5. Not a safety-critical system
UptimeCove is a best-effort monitoring tool. Checks can be delayed or skipped when a scheduled Worker doesn't fire, a network path is degraded, or a platform limit is hit. Alerts can be delayed or lost by the notification provider you chose.
Do not rely on it as the sole safeguard where an undetected outage would cause serious harm — medical, financial, industrial or life-safety contexts included. Use independent, redundant monitoring for anything critical.
6. Intellectual property
The source code is MIT licensed — see the LICENSEfile for the authoritative text. The "UptimeCove" name and logo identify this project; you may use them to refer to it accurately, but not in a way that suggests your fork or product is the official project or is endorsed by it.
Contributions you submit are accepted under the same MIT licence, as described inCONTRIBUTING.md.
7. No warranty
This website and the software are provided "as is" and "as available", without warranty of any kind, express or implied, including the implied warranties of merchantability, fitness for a particular purpose and non-infringement. This mirrors the disclaimer in the MIT licence.
We don't promise the site will be uninterrupted, that the demo will stay up, that the software is free of defects, or that it will detect every outage.
8. Limitation of liability
To the fullest extent the law allows, the maintainers and contributors are not liable for any indirect, incidental, special, consequential or punitive damages, or for lost profits, lost revenue, lost data, or downtime that went undetected — whether the claim sounds in contract, tort or anything else, and even if we were told such damage was possible.
Since this is free software provided at no charge, our total aggregate liability to you iszero.
Some jurisdictions don't allow certain exclusions of warranty or liability. Where that's the case, the exclusions above apply only to the extent permitted, and your mandatory statutory rights are unaffected.
9. Changes and termination
These terms may change; the "last updated" date above will move, and the full history is public in the repository. Continuing to use the site after a change means you accept it.
We may restrict or block access to this website or the demo — for abuse, for cost reasons, or for no reason at all — but we cannot revoke your MIT licence to code you already have.
10. Governing law
There is no payment and no contract for services here, so we don't impose a specific forum or choice of law on you. Any dispute will be handled under the law that mandatorily applies to you, and consumer protections available where you live are not waived by anything above. Rights to the code are governed solely by the MIT licence.
If you fork UptimeCove and offer it as a hosted service, write your own terms — including a governing-law clause — rather than reusing this page.
11. Contact
Questions about these terms belong on the contact page. Bugs and feature requests belong inGitHub issues, where they're useful to everyone.
These terms are written to be readable and accurate. They are not legal advice.