Questions
The questions people ask first
Most of an evaluation happens before anyone gets in touch. These are the questions that come up every time, answered directly rather than deferred to a call.
Security and access
What access does Arrio need to our systems?
Arrio reads your repositories, and it reads them read-only. It does not need write access, it does not need production systems, and it does not need your customer data. Beyond that, Arrio supports several deployment and security models, so exactly where the analysis runs and what it touches is set to what your business requires rather than fixed by us.
Can Arrio run in our own cloud?
Yes. Arrio supports running in the customer’s own cloud, and it is model-agnostic: you can bring your own model and your own key. You choose where your data lives. Which arrangement is right depends on your requirements rather than on a default we impose.
Engagement
How long does it take to get an answer from Arrio?
A first reading of a defined scope comes back in days rather than months. Engagements start with a proof of concept against a real part of your estate, so the first thing you see is your own organisation rather than a demonstration. Whole-estate coverage takes longer and is usually approached in stages.
Comparison
How is Arrio different from a code audit?
A code audit is a one-off engagement that tells engineers what to fix. Arrio is a continuing measurement that tells the people who fund software what the investment produces, in business terms. The inputs overlap; the question, the audience and the shelf life do not.
If the question you have is not here, ask it directly.