Home / Documentation / Spaces & Session Isolation

Spaces & Session Partitioning

In classic browsers, all tabs in the same window share the same cookies, authentication tokens and cache files. LastBrowser breaks with this model and implements true session isolation per Space.

The partition architecture

Each Space in LastBrowser gets a unique partitioning ID following this scheme:

Partition scheme (Electron)

persist:profile:<spaceId>

Examples:
persist:profile:default
persist:profile:work
persist:profile:client-acme

What is isolated per Space?

Cookie jar: Logins on Google, GitHub, AWS or Microsoft apply exclusively within their respective Space.
LocalStorage & SessionStorage: Web apps store state separately.
IndexedDB: Offline databases of notes and messaging apps are strictly separated from each other.
HTTP disk cache: Static resources and API responses are cached separately.

Automatic memory management (discarding)

To prevent many open Spaces from consuming excessive RAM, LastBrowser monitors the activity of each WebContents. Tabs in inactive Spaces are suspended (discarded) after 30 minutes of inactivity. Clicking the tab restores the page flicker-free from the cache.