Read-only access
A job reading your database cannot change it - enforced three ways, on every query. A probe sends no query at all.
Countdat reaches into your systems in two ways, and neither can change anything.
#Jobs: read-only, three ways
Every query a scheduled job runs against your MySQL database goes through all three:
| Layer | What it does |
|---|---|
| Read-only connection | The connection itself is opened read-only. |
| Read-only session | The database session is set to read-only, so a write is refused by your database. |
| Time limit | Each query has a time limit, so a slow query can't tie up your server. |
And before a job is saved at all, it's dry-run so you see exactly what it reads.
Belt and braces: give Countdat a database user with read-only permissions on only the tables it needs. Then read-only is enforced by your own grants as well.
#Probes: no query at all
A probe needs no database login. Your system publishes a few fixed, signed health checks, and Countdat reads them over one signed request. Probes are in pilot.
#Common questions
#Can Countdat change my database?
No. Jobs read through a read-only connection, in a read-only session, with a time limit - and a probe sends no query at all.
#Does the AI see my database password?
No. See Secrets & passwords.
Updated 2026-10-09