Terms of service
The agreement between you and observant.computer.
Draft · 25 August 2026
This is a draft. No lawyer has read it. It is written to describe what the service actually does, in plain sentences, so that a person can read it. It is not legal advice, and it may change before the service opens to the public. If a clause matters to you, ask before you rely on it.
1. Who you are dealing with
observant.computer is run by one person, James. There is no company behind it and no support team. When you email, James reads it.
PLACEHOLDER — James decides the legal name and the address to publish here, and whether a company holds the service.
In this document, "the service" means the hosted software at observant.computer and observant.computer. "The collector" means the open-source program you install on your own servers. "You" means the person or the organization that holds the account.
2. What the service does
The service receives measurements from the collector, stores them, runs rules over them, and shows you what it found. It answers one question: is anything wrong, and what changed.
The service is monitoring, not a backup, not a control plane, and not a security product. It sends no command to your servers. It opens a connection to one only to deliver an alert to a webhook address, and today only the operator can set that address. A route for you to set one yourself is being built. The one thing it can change on your machine is the collector itself: the collector polls this service for a signed release and replaces its own binary. The collector is open source, so you can read exactly what that does.
3. Your account
You need an account to use the service. You may sign in with an email address and a password, with a passkey, or with GitHub, Google, or GitLab.
You are responsible for what happens under your account. Keep your tokens secret. An ingest token can write measurements into your account, so treat the file that holds it as a secret file.
A new account can push from one host for 24 hours until you confirm your email address. A job deletes an account whose users are all still unverified 7 days after signup, with its measurements.
You may create tokens for your own scripts and for AI agents you run. A token you mint acts as you.
4. What you may not do
- Do not push measurements for machines you do not run.
- Do not use the service to break the law.
- Do not try to read another account's data.
- Do not attack the service, and do not test its limits without asking first.
- Do not resell the service as your own product.
You may automate everything you can do by hand. Every action is an API route, and the CLI and an AI agent use the same routes the dashboard uses. That is deliberate.
5. The collector is open source
The collector is published under the MIT license at gitlab.com/jamesobrien/observant-collector. The MIT license governs the collector. This document governs the hosted service. They are separate.
6. Limits and plans
Billing is not open yet. Every account today runs on the flat limits and nobody is charged.
| Plan | Price | Servers |
|---|---|---|
| Free | $0 per month | Up to 2 monitored servers |
| Flat | $9 per month | Up to 10 monitored servers, plus unlimited ephemeral build hosts |
Metric history is 31 days on both plans.
The limits above are not enforced today. The service reads an account's limits and does not yet act on them. When enforcement ships, the service will refuse measurements past the limit with a reason it states plainly, rather than dropping them quietly.
7. Payment and refunds
Nobody is charged today. When billing opens, the price shown on the pricing page is the price you pay, and the service will tell you before it charges you the first time.
PLACEHOLDER — James decides the refund rule. Suggested plain rule: a monthly plan may be cancelled at any time, it stops at the end of the month already paid for, and an unused month charged by mistake is refunded in full on request within 30 days. Replace this box with the rule you choose, on this page and on the pricing page.
8. Uptime and accuracy
The service runs on one server. It has no redundancy. It can be down. Keep a second way to learn that your servers are in trouble.
The service tries to say only true things. A number on the screen is measured, not estimated, and a value it does not have prints as a dash rather than a zero. Even so, a missed alert is possible, and the service is provided as it is, with no warranty of any kind.
To the extent the law allows it, James is not liable for any loss that follows from using the service, and any liability that survives is limited to the amount you paid in the 12 months before the claim.
9. Your data
Your measurements and your account data are yours. The privacy policy says what is collected, how long it is kept, and how to export or delete it.
James does not sell your data and does not use it to train a model.
10. Ending the agreement
You may delete your account at any time, from the account screen or
over DELETE /api/v1/account. Deletion removes your metric
series and every row your account owns. It cannot be undone. Export
first if you want a copy.
James may suspend or close an account that breaks section 4, or that threatens the service for everybody else. Where there is a choice, you get a warning and a chance to fix it first.
James may also close the whole service. If that happens, you get at least 30 days of notice and time to export your data.
11. Changes to these terms
These terms can change. The date at the top of this page shows the last change. A change that materially reduces what you get is announced by email before it takes effect.
12. Law and contact
PLACEHOLDER — James decides the governing law and the jurisdiction, and the contact address to publish here.