Architecture
How Exchange Terminus is put together
A desktop application with its data inside it. The only network call the application needs for identity is a read-only session check.
Status labels: Live (checked directly, dated) Built in code; not independently verified In progress Planned, not shipped Open decision or unverified Not offered / no claim made
Components
Everything in the left column ships inside the application. The right column is what it talks to, and what it does not have.
| Component | What it is | Status |
|---|---|---|
| Globe app | A static single-page app written in TypeScript, using a Three.js globe, bundled into the desktop build. | Built |
| Desktop build | Windows x64 portable, packaged with Electron. The 0.1.3 build is a self-extracting archive of the app with its pictures; first run extracts to the local application-data folder, and the app serves its local files itself. | Built |
| Packs and data | Catalog index JSON, overlay packs, completeness data and pictures, all inside the app. | Built |
| Session check | Read-only verification against the account host. | Built |
| Media host | A public, no-login location for pictures. A missing file returns 404 and the app shows empty. Checked for the brand icon only. | Live |
| Update delivery | Design: fetch only changed packages out of 303. | In progress |
Read from the project files on September 30, 2026. Nothing here was run end to end for this site.
What is deliberately absent
No server of ours that holds your data
Desk state and project locks are stored locally. There is no ET user database and no ET payment system.
No web or cloud edition
There is no browser version. The packaged product is the Windows desktop app.
Delivery and updates explains the release state and update design. Trust model explains what is stored where.
Reviewing for IT?
The IT and security review page lists the questions we can and cannot answer yet.