ISAI RANGE — testing platform
A closed environment in which the customer tests its own AI systems. The Institute provides the infrastructure, the isolation, the session log and the report; the testing itself is carried out by the customer.
What ISAI RANGE is
ISAI RANGE is a testing platform under development. It gives a customer a bounded, isolated environment in which its own AI systems can be placed under unfavourable conditions — and a record of what happened.
Who does the testing
The customer. The platform does not replace the customer's team: the customer's specialists connect themselves, run their own scenarios and decide for themselves what is to be tested.
What is provided
A separate environment for the session, an agreed network perimeter, a session log and a report. Access is opened under a contract only.
Where it runs
On the computing resources of the Institute. The environment is created for the session and does not carry over to the next one.
Status
The platform is a prototype. It is not a commercial service yet, and the organisation that operates it is at the stage of formal registration.
Why a customer needs it
Under pressure an AI system behaves differently than in a demonstration. A separate environment makes that visible without putting the working system at risk.
Test without touching production
Unfavourable input, unstable model behaviour, failures of coordination between agents — all of it can be reproduced away from the system that is already running.
Keep the evidence
Every action in the session is recorded. The log is what makes the result discussable: what was run, when, and what the environment answered.
Judge with your own hands
The customer's specialists see the behaviour themselves rather than reading someone else's conclusions.
How access works
Access is opened under a contract and within the agreed scope only. There is no public sign-up and no anonymous entry.
- The contract is concluded with the right holder of the system to be tested. The scope, the permitted actions and the session limits are agreed in an annex to it.
- The customer confirms that it holds the rights to the system. If the system belongs to a third party, that right holder's consent is required.
- A session code is issued under the contract. It is the only way into the environment: the code is personal and is not passed on to third parties.
- The customer's specialists connect over the agreed channel and within the agreed hours.
What a session includes
The composition of a session is fixed by the contract. Below is what the platform provides by default.
Isolated environment
A separate computing environment for the duration of the session. The customer works inside it and does not see the infrastructure around it.
Agreed perimeter
Network access is limited to the addresses named in the contract. Anything outside the agreed perimeter is unreachable from the session.
Session log
Every action in the session is recorded in a log. Both parties can rely on it; the customer receives it together with the report.
Report and destruction of artefacts
At the end of the session the customer receives a report, and everything created during the session is destroyed. What remains afterwards is the contract, the log and the report.
Perimeter and rules
The platform works only within the boundaries agreed in writing. That is what makes the work lawful and the result usable.
- The perimeter — addresses, systems, time — is named in the contract and is not widened during the session.
- Only the actions listed in the annex are permitted. Anything outside that list is a breach of contract.
- Attempts to leave the perimeter are recorded, and the session can be stopped.
- The session runs within the agreed time window; outside it the environment does not exist.
- The customer does not upload data that may not be processed there: personal data outside a separate instruction, state secrets, or third-party trade secrets.
What we do not do
The boundaries are set by law and by the contract. They are stated here plainly so that no wrong expectations are formed.
- In this mode the Institute does not test systems on the customer's behalf: the testing is carried out by the customer's specialists.
- We do not issue conclusions on compliance with information security requirements and do not perform licensed work of that kind.
- We do not work outside the agreed perimeter and do not access third-party systems, even where they are connected to the system under test.
- We do not promise that testing will find nothing, nor that it will find everything. The report states what was checked, what was not, and what the result supports.
Responsibility and stopping
Responsibility is allocated by the contract before the session starts, not after it.
- The customer is responsible for the lawfulness of the testing and for the rights to the system under test; the Institute is responsible within the limits set by the contract.
- Emergency stop: either party may stop the session at any moment. The stop procedure is set out in the contract.
- After a stop the log is preserved and handed over, and the artefacts of the session are destroyed.
Cost
The cost of a session is calculated individually and is not published as a figure: it depends too much on the task.
- The computing resources reserved for the session and their configuration.
- The size of the perimeter, the number of systems and the length of the session.
- The composition of the report and the requirements for supporting documents.
The indicative range and the composition of the stages are provided on request — within one working day, without registration on the site.
How to request access
Write to info@isai.su and describe briefly: whose system is to be tested, what result you need and what timeframe you are considering. We will answer with questions first, and then with a proposal. Registration is not required to receive the pricing information.