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
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%.
Package-set accounting from built `.deb` files · measured 31 Aug 2026 · the bundled case adds one actual runtime archive per app
Packaged applications
Compatibility is earned.
Matching an Electron major starts an audit. Each report records the package boundary and the behavior actually tested.
LosslessCut
Lossless video and audio cutting
- Package
- 3.69.0-1foundry2
- Runtime
- electron-runtime-42
draw.io Desktop
Offline diagram editor
- Package
- 31.3.1-1foundry1
- Runtime
- electron-runtime-42
MarkText
Visual Markdown editor
- Package
- 0.19.1-1foundry2
- Runtime
- electron-runtime-42
Joplin
Notes and knowledge management
- Package
- 3.7.14-1foundry1
- Runtime
- electron-runtime-42
Teams for Linux
Unofficial Microsoft Teams wrapper
- Package
- 2.18.1-1foundry1
- Runtime
- electron-runtime-42
JupyterLab Desktop
Desktop notebooks and data tools
- Package
- 4.6.3-1foundry1
- Runtime
- electron-runtime-42
Netron
Neural-network model viewer
- Package
- 9.2.4-1foundry1
- Runtime
- electron-runtime-44
Trilium Notes
Hierarchical notes and personal knowledge bases
- Package
- 0.105.0~git20260831.d2df448d-1foundry1
- Runtime
- electron-runtime-44
Package boundary
Common core.
Private edges.
Only generic Electron/Chromium files move into the shared runtime. Application code, native modules, helpers, and identity remain application-owned.
Reports
Show the work.
Read the decisions, measurements, failures, and test results behind the package cards.
What belongs where
Which files belong to the runtime, which stay with each app, and why.
Can we build it twice?
Pinned builders, frozen inputs, matching outputs, SBOMs, and provenance.
One runtime, one responsibility
Fast patches, app-wide testing, rollback, and a clear end to old runtime lines.
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 modelTrack supported Electron lines and Chromium fixes.
Rebuild and test the full app set on every runtime update.
Hashes, SBOM, provenance, test results, and rollback stay together.
Progress log
What changed.
What’s next.
Trilium Notes passed SQLite profile creation, integrity, and reopen tests on Electron 44.
Netron passed model-opening tests on the new Electron 44 runtime.
Electron 42 and 44 were verified side by side.
The first seven applications were split from their bundled Electron runtimes.