Which tools connect,
and exactly how.
Kaer holds direct, authorised connections to 7 services. Everything else it operates the way your team does — signed in, in its own browser. Both work. This page says which is which, service by service, so a logo never implies more than it should.
A direct, authorised connection. You grant scoped access once; Kaer reads and writes through the service's own API or protocol, and you can revoke it at any time.
7 services
No API needed. Kaer signs in and uses the web app in its own browser session, the same way your team does — with the same approval gates before anything is sent, paid or published.
22 services
On the roadmap and not connectable yet. Until it ships, Kaer can still operate the service through Kaer Computer.
4 services
Mail & calendar
Files & docs
Communication
Money & billing
Customers & sales
Work tracking
Websites & storefronts
Software
An API is faster. A browser is universal.
Where a service offers an API and we have built the connector, Kaer uses it — it is quicker, more reliable and easier to scope. Where it does not, Kaer signs in and uses the web app in a Kaer Computer session, which means the long tail of business software works without waiting for anyone to build anything.
- Native connections are scoped per tool and revocable individually
- Browser sessions are isolated per run and destroyed after
- Both paths pass through the same approval gates before anything consequential
Integrations, answered.
What does “planned” actually mean?
It is named in the product's own connector catalogue and not connectable yet. Until it ships, Kaer can still operate the service through Kaer Computer — so a planned label is about how it connects, not whether the work can be done.
Is a browser session less secure than an API connection?
It is scoped differently. A native connection carries explicit, revocable API scopes. A browser session runs in an isolated machine that is destroyed when the run ends, using credentials you granted for that purpose. Both are recorded, and both stop at the same approval gates.
Can Kaer work with our internal system?
If a person can use it in a browser, usually yes — that is the point of the browser path. Systems behind a VPN or with unusual sign-in need a conversation first.
How do I revoke access?
Per tool, at any time, from the connectors screen. Revoking one connection does not affect the others.
Connect one tool.
Hand over one job.
A mailbox and a calendar is enough to start. Everything else can wait until you have seen it work.
or request an integration