Cloud compute
StoriBot does its work in its own cloud environment, not on your computer. You can close the tab, and a job can run at three in the morning, and the work carries on the same way.
What it does there
Section titled “What it does there”When StoriBot builds a Stori, it starts a working session in the cloud. In that session it can:
- Read the systems you have connected, and the files you uploaded.
- Run code against the data: joins, aggregations, forecasts, work over hundreds of thousands of rows that a browser could not handle.
- Make the outputs: a live page, or a Word, Excel, PowerPoint, PDF or CSV file in your template.
- Keep the Stori’s files beside it, so the next session starts from where the last one finished.
Everything runs in AWS Sydney (ap-southeast-2). Data does not leave the region to be processed.
Each Stori has its own files, and they are kept between sessions. StoriBot organises them as the work needs; there is nothing for you to set up. The files you upload land in two places, data for datasets and context for briefs and reference material, and the pages, scripts and outputs StoriBot makes sit beside them. What it learned about the Stori is written to the Stori’s memory, which the next session reads first.
Security
Section titled “Security”Nothing StoriBot runs touches your machine, your network or your other accounts. The only things in reach of a session are the sources you connected and the files you gave it. There is no crawl of your wider environment.
A session never holds the keys to a connected system. Every read and write goes through StoriBot’s integration layer, which checks that the operation was granted before it runs. See Integrations.
Isolation
Section titled “Isolation”- One session, one environment. Each working session gets a fresh environment, started for that session and shut down when it ends or goes idle.
- Scoped to the organisation. The credentials a session holds are temporary and scoped to your organisation. It can reach that organisation’s Stories and files, and nothing belonging to anyone else.
- One Stori’s files at a time. A session works in the files of the Stori it was started on. It can read other Stories in the same organisation, but not change them.
Every organisation is logically isolated on shared Australian infrastructure, with credentials scoped per organisation and no cross-customer access. A fully dedicated deployment, with separate infrastructure and customer-managed keys, is not something we run today. The detail is on stori.bot/trust.