Sovereignty and offline work
What runs without a connection to Elizon, and where your data and keys stay.
Building, installing, running and configuring Packages requires no connection to Elizon. Everything runs on your own infrastructure.
What runs offline
| Command | Network | Account | What it touches |
|---|---|---|---|
init | None | None | The project folder |
schema | None | None | Nothing |
validate | None | None | Reads the project folder |
build | None | None | Reads the project, writes the .pkg |
target ls | None | — | Reads your local credential file |
These guarantees are enforced by the CLI's own test suite: the four authoring commands are run with all network access disabled, and none of them can reach the code that talks to an Organization.
The one thing that needs the network is getting the CLI: the first time you run a version, npx downloads it from the npm registry, or from your organization's npm mirror. After that, the version is cached and the commands above work with no connection at all.
What talks to an Organization, and only yours
target add, target key, sign, install, packages ls and packages bind talk to the address you connected
to, which is your Organization's own deployment. The CLI never contacts any other Elizon-operated
service, has no default host, and treats a self-hosted deployment exactly like an Elizon-hosted one.
Where things stay
| What | Where it stays |
|---|---|
| Your Package sources | Your machine and your repository |
The .pkg when signing | Your machine. Only the list of file hashes is sent |
| Your Organization's signing key | Your Organization's encrypted vault. Never returned to anyone |
| Installers' credentials | The installing Organization's vault. Never in a Package, never seen by the CLI |
| Installers' documents | The installing Organization. A Package carries Knowledge Base settings, not documents |
| Device tokens | Your user configuration directory, never inside a project |
Distributing without a registry
A signed .pkg verifies with nothing but the file and a public key, with no network call. Share it
however you already share files: a Git repository, an artifact store, a file share, email, removable
media. Installation verifies it locally before anything is written.