← All documentation

Security

The sandbox

Every app you install from Software runs in a box of its own. It sees its own folder and what you allow, and nothing else.

On most systems, any program you install can read every file in your home: your documents, your browser’s cookies, your SSH keys. On AOS, an app you install from Software runs in a sandbox. It is still your program, running as you, but it only sees what it has been given.

What an app sees

When an app starts, AOS builds a private view of the computer for it:

  • Its own home. The app’s home folder is ~/AppData/<org>.<name>, for example ~/AppData/mozilla.firefox. Everything it saves goes there. You can open the folder in Files, and deleting it resets the app.
  • The folders it declared or you allowed. A video player might see Videos read-only. An editor sees Projects. They are shown at their real paths, so files land where you expect.
  • The system, read-only. The core of AOS and the app’s own packages, pinned to the exact versions it was tested with.
  • Your desktop, through safe doors: its windows, sound playback, notifications, printing, USB sticks you plug in, and the theme you chose.

What it does not see:

  • Your other files, other apps’ folders, ~/.config, or browser data.
  • ~/.ssh and ~/.gnupg, unless it has the SSH permission.
  • Other people’s homes on the same machine.
  • The admin service. A sandboxed app has no way to ask for root.
  • Your screen. Only the screen-sharing dialog can capture it, and it asks you which display first.
  • Your microphone and camera, unless you switch them on.

Permissions

Each app says up front what it needs, and Software shows that before you install, for example “Sees: its own files and Downloads · Uses the network”. Once it is installed, the app’s page in Software has a Permissions section with switches you can change at any time:

Permission What it gives
Downloads, Documents, Pictures, Music, Videos That folder, read and write
Allow a folder… Any other folder in your home that you choose
Network Internet and local network. Off means no network at all
Camera Webcams
Microphone Recording. Without it, the app can still play sound
Developer tools The compilers and tools you installed through apm, read-only
Discrete GPU The NVIDIA graphics card on laptops that have two GPUs
X11 windows Older programs that need XWayland (see below)
Starts when you log in Autostart

Changes apply the next time the app starts. The page also has Its folder, Clear cache and Delete its data.

Your choices are stored in ~/.config/aos/sandbox/<org>.<name>, a place no app can see, so an app cannot grant itself more.

X11 is a real trade-off. An app with “X11 windows” can see the keys and contents of other X11 windows. Normal (Wayland) windows stay invisible to it. Only switch it on for programs that need it.

Opening files from outside

When an app opens a file through the file dialog, the dialog is drawn by AOS, not by the app. If you pick a file the app can’t otherwise see, only that one file is handed over. If you pick a folder it doesn’t have, AOS asks Allow / Don’t allow. Allow grants that folder, and the app restarts with it. Double-clicking a file in Files works the same way.

A few places can never be granted: your whole home, AppData, .config, .local, .cache, .ssh and .gnupg.

Network ports

An app that needs to accept connections, such as a game server or a sync tool, must declare its ports. You switch each one on or off in Settings → Network → Advanced → Open ports. Anything not declared stays closed.

Which apps are sandboxed

Sandboxed?
Core apps: Settings, Software, Files, Terminal, Disks, System Monitor, the installer, the desktop itself No. They are part of the system and run as you.
Official apps: Notepad, Images, Videos, Sound Recorder, Clock, Calendar, Calculator, Weather, Camera, Scanner Yes, most of them without network access
Third-party apps: Firefox, Steam, VS Code, Discord, Claude… Yes, and labelled third-party
Command-line tools from apm (compilers, gh, ripgrep…) No. They run as you, from the Terminal

If an update breaks an app

If an app crashes within 20 seconds of starting right after an update, AOS starts it again with the previous version and tells you. Software also offers Use previous version on the app’s page.

For developers

The sandbox is declared in the package’s [sandbox] section. See Making and publishing apps for every key.