Account
Checking your session…
Sign in
Sign in with the email address you paid with. We look your licence up by that address, so if you bought with a different one, use that.
Your licences
What your tier unlocks
These are the limits your container enforces offline, from the licence itself. Ask for more than your tier allows and the response tells you the limit it applied rather than failing, so a page size tuned for Pro does not break on Starter.
| Tier | Records per page | Delta feed /v1/changes | Bulk export |
|---|---|---|---|
| Community | no reads | No | No |
| Starter | 100 | No | No |
| Pro | 500 | Yes | No |
| Enterprise | 1000 | Yes | Yes |
| MSSP | 1000 | Yes | Yes |
Install and upgrade
Your licence is also your registry password, and your account reference is the username. Reveal your licence above, export it, then run these as they stand.
export TIRESIAS_WATCH_LICENSE='<reveal your licence above>'
docker login registry.saluca.com -u <account reference> -p "$TIRESIAS_WATCH_LICENSE"
docker pull registry.saluca.com/saluca/tiresias-watch:latest
Point it at your own Postgres. Nothing else is required.
docker run -d --name tiresias-watch -p 8355:8355 \ -e TIRESIAS_WATCH_LICENSE="$TIRESIAS_WATCH_LICENSE" \ -e TIRESIAS_WATCH_DSN="postgresql://user:pass@db:5432/watch" \ registry.saluca.com/saluca/tiresias-watch:latest
Then confirm what the container thinks your entitlement is:
curl -s localhost:8355/v1/status
Renewing, and upgrading a tier
When your subscription renews we mint a fresh licence and email it - and it also appears here, so a lost email is no longer a lost licence. Restart the container with the new value:
docker stop tiresias-watch && docker rm tiresias-watch # re-run the docker run above with the new licence
Is my feed healthy?
We cannot see your feed - it is your container and your database. But
/v1/status is ungated precisely so you can answer this yourself without a
credential, even when a licence has lapsed. Paste its output below and this page will read it
for you. It is parsed in your browser and never sent anywhere.
curl -s localhost:8355/v1/status
Quiet is not the same as dead
A source that has not changed is not a source that has stopped being fetched, and only one
of those is your problem. /v1/status reports the last successful fetch per
source from the run log, not the newest record - which is the only way to tell a genuinely
quiet day from a fetcher that has been crashing for three weeks. Alert on ingestion freshness,
never on record counts.
| What you see | What it means |
|---|---|
status: ok, few new records | Healthy and quiet. KEV moves in bursts; a still day is normal. |
degraded, age_hours over 36 | Fetches have stopped succeeding. Your scheduler is the first thing to check - ingestion only happens when you run it. |
degraded, last attempt failed | It succeeded earlier and is failing now. last_error names it. Usually egress or upstream. |
down, no successful fetch ever | This source has never once been read. Not "no data yet" - a fault, usually configuration. |
licence.status: grace | Expired but still honoured, for 72 hours. Renew now; reads stop after that. |
HTTP 503 from /v1/status | Expected whenever status is not ok. The body is still the full report - read it, do not just alert on the code. |
Billing
Invoices, card changes, tier changes and cancellation are handled in the billing portal, reachable from your licence above.
Help
Technical questions and licence problems: support@saluca.com - include your account reference. Billing, tier changes and invoicing: sales@saluca.com. The full reference is at tiresias.watch/docs.