Virtual machine · 2 min read
Technical details
What is installed on an assistant's virtual machine, and how the machine is kept secure.
This page describes the virtual machine every assistant uses to run programs on your files.
What is on the machine
Section titled “What is on the machine”The VM runs Debian Linux. The assistant works in a standard shell as an ordinary, unprivileged user. Installed:
| Python 3.13 | With the standard library, plus pandas for tables and calculations, openpyxl for Excel, python-docx for Word, python-pptx for PowerPoint, and pdfplumber for reading text and tables from PDFs |
| PDF tools | pdftotext and pdftoppm (Poppler), to extract text and to render a page as an image |
| Text recognition (OCR) | Tesseract, for reading text from scanned documents and images in Latin-script languages |
| LibreOffice | Writer, Calc and Impress, run without a screen, to convert Word, Excel and PowerPoint files, for example to PDF |
| Command-line tools | The usual Linux utilities for working with files and text |
It is LibreOffice, not Microsoft Office. Files the assistant creates are standard .docx, .xlsx and .pptx files that open normally in Office, but a document with unusual Office-only formatting can look slightly different when the assistant converts or renders it.
The assistant cannot install anything else: the machine has no internet connection.
Where the machines run
Section titled “Where the machines run”The virtual machines do not run on the servers that run Intric itself. They run on a separate server whose only job is to host them. Your Intric environment, its databases and your stored files are on other machines, so code running in a VM has nothing of the platform beside it to reach.
That server cannot be reached from the internet. Only Intric environments that have been registered with it can connect, each with its own key, and each environment can only start and reach its own machines.
Each machine is a complete virtual computer with its own operating system, built on Firecracker, the virtualisation technology cloud providers use to run code from different customers side by side. Each machine is sealed off from the others on the same server, and from the server itself.
On an on-prem installation, the machines run on your own servers, inside your installation, and never leave your network.
How it is kept secure
Section titled “How it is kept secure”An assistant that can run code needs firm boundaries. Intric builds them into the platform itself, so they hold whatever the assistant is asked to do.
- One conversation, one machine. Every conversation gets a machine of its own. Nothing an assistant does in one conversation can be seen from another, and never from another user’s.
- No internet connection. The machine cannot reach the internet, the Intric platform’s databases or any other system in your organisation, so code running on it cannot send your data anywhere.
- Your originals are protected. The assistant can read the files you share, but it cannot change or delete them. It can only add new files, which you see when it hands them to you.
- Code is kept on a short leash. It runs without administrator rights, a task that runs too long is stopped automatically, and a heavy job in one conversation cannot slow down anyone else’s.
- Nothing is kept longer than needed. While you keep working, the assistant can build on what it did earlier in the conversation. Once the conversation has been idle for a while, the machine and everything on it are deleted. Files the assistant gave you are stored with the conversation and follow the same retention rules as everything else in it.