No integrations are listed here because none have shipped.
A restaurant or small operation already runs on other software, point of sale, scheduling, accounting, messaging. Atarla is designed to connect to those systems rather than replace them outright, but no such connection exists today, and there is no integration catalogue to browse.
The permission model an integration must satisfy.
Every connector is treated as a dependency, not a trusted authority. An integration is designed to request specific, named permissions, such as read access to a menu or write access to a calendar, rather than a blanket grant, and a business should be able to see and revoke what a connector can touch.
External tools and connectors do not get to make security or correctness decisions on Atarla's behalf. Where an integration's own vendor makes a security claim, Atarla treats that as the vendor's claim, not as something Atarla has verified.
What a future catalogue would record.
- Name, vendor, and category of the connected tool.
- Status: Official, Community, Experimental, Planned, or Deprecated, with Planned never presented as Available.
- Source, authentication type, and the specific permissions requested.
- Whether it runs in the cloud or locally, and whether it is Atarla-official or community-maintained.
- Documentation links, security notes, when it was last tested, and known compatibility limits.
What is not claimed.
No integration catalogue exists. No connector, official or community, has shipped, and nothing on this page can be installed or authorized today.