There is nothing to build on yet. This is who it would be for.
This page exists so that a developer who lands here does not waste time hunting for a package or a key that has not been published. Atarla does not have a public SDK, a public API, or a developer programme right now. What follows is who the platform is being designed for and what a developer would eventually need.
Who this is for.
The intended audience is a small business's technical contact, an independent developer building for a local operation, and eventually contributors to the open components described on the open-source page. The web application is currently in invite-only testing and the mobile MVP is built with Expo tooling, both used internally rather than exposed through any developer interface.
What would need to exist first.
- A documented architecture, so a developer knows what they are integrating with before writing code.
- A published API or SDK surface, with authentication and permission scopes defined rather than assumed.
- An agent and integration interface, matching the intent described on the open-source page.
- A contribution guide for any component that becomes open, and a security process for reporting issues in it.
What is not claimed.
There is no public SDK, no public API, no package registry entry, and no developer programme today. Nothing on this page can be installed or called.