1. Early access
The service is changing quickly. Features described on these pages may change, move or be marked as coming before they are released, and the What's new page highlights what has shipped.
If something on these pages does not match what the service does, the service's own behaviour and your agreement win, and we would like to hear about it.
2. Access
Console accounts are created by an admin; there is no self-signup. Projects get their own API keys, which you can issue, rotate and revoke yourself.
The CLI and its installers are currently available only to collaborators on the private iStable repository. Public downloads are not released yet.
3. Your data
Each project's data is kept separate, and keys and connected-tool credentials are protected.
How the service handles data is described on the privacy page, which reflects how the service is built today.
Keep your keys to yourself . A key is shown once, when it is issued; if one leaks, revoke it from the iHarness console.
4. Pricing
Pricing for aarna.pro has not been announced. Ask us about access and we will tell you where things stand.
5. Agents and humans
The service is designed so that agents may check and request, and only a human grants. Automation can never approve an action or resume stopped work; that takes a signed-in person.
6. Controls the service gives you
Human admins can stop agents at any time, without waiting on us:
- Stop an agent so it takes on no new work
- Stop a group of agents together
- Stop a whole project at once
- Resume work when you are ready
- Revoke an API key outright
7. Questions
If you have questions about early access or how the service handles your data, use the contact page. For the details of what is stored and why:
- Accounts and sign-in
- API keys
- Connected-tool credentials
- Project data
- Retention
are each covered on the privacy page.