How Ola worksA technical overview: where the work runs, what can leave the machine, and what is logged.
Ola runs on a staging machine for now.
Ola runs on a staging machine for now.
LiveCloud runtime. The agent and the project’s files are on the Ola machine. The clients are the web app at app.ola.cx, the Mac app and the iPhone app. All three show the same projects and conversations.
LiveLocal runtime. The Mac app or the ola command runs the agent on your Mac, in a folder you choose. The files stay on the Mac. Model requests and web searches go to the Ola machine’s gateway. The iPhone app can connect to the Mac over a private network.
LiveEach project gets its own secure, dedicated Linux system: a virtual machine with its own disk and no internet connection. It holds that project’s files and database, and nothing from any other project.
Documents can contain instructions aimed at the agent (prompt injection). The VM’s only outbound route is the model gateway, which carries model requests and the web requests that were allowed.
LiveThe gateway is a separate process on the Ola machine. It holds the model providers’ API keys; the VMs never see them. Each VM has its own access token, bound to its own connection, so a token copied out of one VM is refused through any other.
LiveCloud runtime. Each project’s data is on its VM’s disk: uploads, web downloads, the agent’s output and the conversation history. Each project has its own SQLite database, with a full-text index of its documents by page and every table the agent creates. Deleting a project deletes its disk and its database.
The web app shows all of it. Files lists every file. Data lists every table with its source and row count. The database can be downloaded as one file, and any table as an Excel file.
A separate platform database holds accounts, teams, projects and the access log. It stores no file names, file contents or message text. Files are recorded as keyed hashes.
LiveLocal runtime. Files stay in the chosen folder on the Mac.
LiveSign-in is a username and password, by invitation only. Passkeys are optional. Sessions are stored on the server, without IP addresses or browser details.
Each project has a team with three roles:
A non-member gets the same “not found” response as for a project that does not exist. Removing a member takes effect on their next request and closes their open connections.
The access log records sign-ins, file uploads, downloads and deletions, files the agent read, and every request sent to an outside model. Members can read their own project’s log.
The machine has one operator, with administrative access to everything on it. The admin tools report table names, row counts and sizes, not file contents.
Ola uses open-weight models first.
Live, stagingOn staging, the open models are rented from Together AI. Staging holds only test data.
Planned, DecemberThe models run on the Ola machine itself. Prompts do not leave it.
LiveTwo fallbacks, off by default: a hosted open-weight model (Together AI) and Claude (Anthropic). When one is used, the request and the file content the agent includes in it go to that provider.
The order is fixed: the local open model, then a hosted open model, then Claude.
LiveThe VM cannot reach the web. The gateway performs searches and downloads for the agent.
Built, not switched on yetNothing is public until the project owner selects Publish. The agent has no way to publish.
.env.LiveIn transit. Connections to app.ola.cx use TLS, terminated on the Ola machine. The relay that carries traffic in from the internet forwards it without decrypting it.
TodayAt rest. The staging machine holds only test data. Its disk is not encrypted.
Planned, DecemberFull-disk encryption on the production machine before any real data, with projects run under a dedicated system account. Staging never holds real data.
TodayBackups. No automatic backups. A project can be snapshotted and restored by hand; the restore is tested.
PlannedEncrypted backups. Deleted files will stay in them for up to 14 days.
LiveDeletion. Deleting a file removes it from the project immediately. Deleting a project removes its disk and its database.
Limits. Ola is one machine with one operator. It does not protect data from that operator, or from someone who compromises the machine.
Checked against the running system on November 19, 2026. This page is updated when the system changes.