What connects natively, and what does not

Native integrations are the tools Kaer can drive without a browser. Everything else still works: Computer Mode opens the web app and does the job there.

We publish the native list because a vague 'we integrate with everything' is how teams get stuck mid-migration.

A native connector is 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.

Everything else runs through Kaer Computer. No API is 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.

Planned services are marked as planned and are not connectable yet. Until they ship, Kaer can still operate them through Kaer Computer.

If a tool is missing from native and Computer cannot reach it either, that is a gap. We would rather say so than invent a connector on the pricing page. The Integrations page lists every service and which of the three it is.