- Sign up and say what you do
A couple of lines about the business — what you sell, how you price it, how you talk to customers. This is the context every job is worked from.
- Hand over one job
In plain English: “chase every invoice more than thirty days overdue”, “answer the enquiries that came in overnight”. Outcomes, not steps.
- Watch it work, and see where it stops
Kaer shows the plan, does the work, and pauses at the step that carries a consequence — the message before it sends, the invoice before it is issued.
- Approve, and keep the result
One tap with the whole thing attached. What it did is recorded, and the same job can be handed over again or put on a schedule.
Before you start
Do I need someone technical?
Not for the first four paths. You connect a mailbox or a calendar and hand over a job in plain English. The software path is the only one where a repository comes into it, and even there the no-repo route needs nobody technical.
Do I need to install anything?
No. Kaer runs in the browser, and its own compute happens on isolated machines we manage. There is an API and a CLI when you want them; none of these paths need either.
What access does it get?
Exactly what you grant: per-tool and per-repo scopes, revocable at any time, with approval gates before anything irreversible.
Which mailboxes can I connect?
Two ways in: take a mailbox hosted by Kaer, or connect one you already have over IMAP. Either can run on your own domain — if it sits on Cloudflare, Kaer sets the email routing up for you.
What does it cost to try?
Nothing — the Starter tier includes free daily credits, no card required.
Five minutes. One job.
The fastest way to understand Kaer is to hand it something you would rather not do today.
