SHARED PAIR2c–2e
About →

Shared Electron runtimes for Linux

One runtime.
More room.

Shared Pair separates compatible desktop applications from the versioned Electron runtime they have in common—and keeps the packages, tests, provenance, and security updates together.

Packages built and tested · APT publication pending approval

Two-centre, two-electron bondTwo centres joined by an overlapping electron-density field containing two electrons with opposite spin projections.2c–2e · paired spin
StatusPublished · public install verified
Runtimes2 tested runtime lines
Applications8 packaged and tested
TargetUbuntu 26.04 · amd64
Updated31 Aug 2026

The shared region

Electron,
shared.

In the ordinary 2c–2e model, two centres are held together by a shared electron pair. Shared Pair applies that compact idea to desktop packaging: applications remain distinct while a compatible runtime occupies the common region.

The electrons are shown with opposite spin projections. They share the bonding region; the spin itself is not “shared.” The chemistry is a metaphor, but we intend to get the metaphor right.

Measured package set

Save 535.7 MiB.

Seven tested applications use two runtime lines. Sharing one runtime per line reduces the modeled compressed package set by 42%.

Runtime per app
1275.5 MiB
Shared Pair
739.8 MiB

Package-set accounting from built `.deb` files · measured 31 Aug 2026 · the bundled case adds one actual runtime archive per app

Packaged applications

A curated catalog of shared-runtime applications.

Each application is selected, adapted, and tested against a shared Electron runtime. Maintainers of compatible Electron apps are invited to adopt the same runtime packages and join the catalog.

01tested

LosslessCut

Lossless video and audio cutting

Package
3.69.0-1foundry2
Runtime
electron-runtime-42
Split from its bundled runtime and tested alongside the Electron 42 application set.Read technical report →
02tested

draw.io Desktop

Offline diagram editor

Package
31.3.1-1foundry1
Runtime
electron-runtime-42
Packaged without Electron; clean-container CLI export passed.Read technical report →
03tested

MarkText

Visual Markdown editor

Package
0.19.1-1foundry2
Runtime
electron-runtime-42
Packaged without Electron; its packaged-mode adaptation preserves electron-log and its ABI 146 native modules.Read technical report →
04tested

Joplin

Notes and knowledge management

Package
3.7.14-1foundry1
Runtime
electron-runtime-42
The 3.7 prerelease package persists and reopens its SQLite profile.Read technical report →
05tested

Teams for Linux

Unofficial Microsoft Teams wrapper

Package
2.18.1-1foundry1
Runtime
electron-runtime-42
Initializes and reopens its profile through the shared runtime.Read technical report →
06tested

JupyterLab Desktop

Desktop notebooks and data tools

Package
4.6.3-1foundry1
Runtime
electron-runtime-42
Runs its private Jupyter environment and persists its desktop profile.Read technical report →
07tested

Netron

Neural-network model viewer

Package
9.2.4-1foundry1
Runtime
electron-runtime-44
Packaged as a plain app payload without Electron, Chromium, or its upstream self-updater.Read technical report →
08tested

Trilium Notes

Hierarchical notes and personal knowledge bases

Package
0.105.0~git20260831.d2df448d-1foundry1
Runtime
electron-runtime-44
The pinned development snapshot is packaged as an application-only payload with its private SQLite module and no bundled Electron or Chromium.Read technical report →
Explore applications →

Adoption path

One runtime.
A growing catalog.

Package a runtime line once, support applications against it, then repeat the audit, adaptation, and testing process for the next compatible app.

01 · Runtime readyelectron-runtime-44Electron · Chromium · locales · sandbox
02 · Supported nowNetron · Trilium NotesAdapted packages · bounded dependency · passing tests
03 · Next adoptionCompatible Electron appAudit → adapt → package → test → catalog

Runtime notes

Decisions behind the runtime.

Architecture, reproducibility, and maintenance notes now live with the runtime versions they govern.

Security

The runtime is a responsibility.

One Chromium runtime means less duplication—and one place that must be patched quickly. Fast, visible updates are non-negotiable.

Read the security model
01Watch upstream

Track supported Electron lines and Chromium fixes.

02Test every app

Rebuild and test the full app set on every runtime update.

03Bring receipts

Hashes, SBOM, provenance, test results, and rollback stay together.

Application feed

Verified and published.

Follow each application through verification, publication, updates, and holds without duplicate release items.

Subscribe via RSS →
  1. next

    Publish the signed APT repository and verify a clean installation from apt.sharedpair.dev.

  2. shipped

    Trilium Notes passed SQLite profile creation, integrity, and reopen tests on Electron 44.

  3. shipped

    Netron passed model-opening tests on the new Electron 44 runtime.

  4. shipped

    Electron 42 and 44 were verified side by side.

  5. shipped

    The first seven applications were split from their bundled Electron runtimes.