Security and access
Ari works on a copy of your store. A person approves and releases every change.
A copy of your code and catalog, with no customer data in it.
Ari suggests each change. A person on your team approves it before it goes live.

Your live store, your servers and your customers’ data.
| Live store | Preview store | Pull requests | Chat | |
|---|---|---|---|---|
| You and your team | ||||
| Your developer or agency | ||||
| Ari engineersOn the Ari + human plan | ||||
| Ari | ||||
| Your customers |
Merged pull requests
#214Add a free delivery barapproved by TomSep 23#209Quebec sales tax on the CA store viewapproved by AnaSep 18#203September security patchapproved by TomSep 11#198Replace the abandoned reviews moduleapproved by TomSep 4#191Promo bar on the US store viewapproved by MartaAug 29Each change is a pull request, with what changed, when and who approved it, and it reaches your repository when a person merges it.
PCI DSSCompliant for payment data
ISO 27001Information security
ISO 27017Cloud security
ISO 9001Quality managementNo. Ari works on a copy of your store. Changes reach your live store only when a person merges and releases them.
No. The database copy Ari works with has customer and order data removed.
You connect your code and its history, your Composer credentials and a database copy without customer data, once at setup.
No. Ari uses the business services of OpenAI and Anthropic, which do not train their models on the data sent to them.
When you remove Ari from your repository, Ari stops opening branches and pull requests.
Only on the Ari + human plan, the Ari engineers who review and release your changes.
Pricing
Enterprise plans carry custom volumes and terms. Contact sales, or read what it costs and how it works.