Documentation

Last updated 19 September 2026

Canary is in active development. This page describes how the product works today and will change as features ship. If something here does not match what you see, write to contact@jimapps.dev.

Getting started

Install the app Install Canary once at the agency level and approve the requested permissions.
Wait for the first scan Canary enumerates your client accounts and runs a first pass. This usually takes a few minutes.
Add your domains For email authentication and SSL checks, paste the domains you send from and publish sites on. These are checked against public DNS, so they cannot be discovered automatically.
Choose where alerts go Email, Slack, or both. Alerts can be sent per account or batched into a daily digest.

The checks

Check	What it looks at	Source
Social & profile connections	Token expiry and disconnected accounts for Facebook, Instagram, Google Business Profile, LinkedIn and TikTok	Account API
Email authentication	Presence and validity of SPF, DKIM and DMARC records	Public DNS
SSL certificates	Certificate expiry date and chain validity	TLS handshake
Message delivery	Rate of failed and undelivered messages against recent baseline	Account API

How often checks run

Connection and delivery checks run on a short interval throughout the day. DNS and certificate checks run less frequently, because the things they watch change slowly — a certificate expiry is known weeks in advance, and Canary warns you well before the date rather than on it.

Permissions

Canary requests read access only. It reads the status of connected accounts, message delivery outcomes, and the list of client accounts under your agency. It does not post, send messages, modify settings, or read message content.

Domains you add for DNS and SSL checks are queried over public DNS and a standard TLS handshake — the same information any visitor to the site can observe.

Alerts

Immediate — sent when a check changes from passing to failing.
Digest — one message per day summarising everything currently failing.
Resolved — sent when a failing check starts passing again, so you know it is fixed.

Each alert names the account, the check, when it was last seen healthy, and the usual fix.

Pricing

Canary is priced per client account being watched, with a free tier that covers your first few accounts. Accounts you are not watching are never charged for. Final pricing is published before general availability.

Questions

Anything not covered here — support or contact@jimapps.dev.