Desktop · Architecture

Desktop architecture.

The Axiom desktop app is a Tauri shell wrapping the same operational UI as the web platform, plus a local execution runtime, OS-keychain credential bridge, and an optional workstation mode that disables all outbound telemetry.

Why Tauri

We chose Tauri over Electron for footprint and security: a Tauri app is ~10MB instead of ~150MB, runs in the native OS WebView (no bundled Chromium), and exposes a Rust-side execution boundary that's easier to audit and harden.

01

The four layers

  • WebView layer (TypeScript/React) — same operational UI as the web platform (Command Center, Topology, Memory, Workflows, ReleaseOps). 90%+ component reuse.
  • Tauri shell (Rust) — native shell process, OS integration (notifications, menu bar, tray icon, file system access), and the policy gate for which commands the WebView is allowed to invoke.
  • Local execution runtime (Rust) — invokes terraform CLI and AWS CLI from local PATH using your existing profile. Captures stdout/stderr for the audit log.
  • Sync layer (Rust) — handles bidirectional sync with the Axiom cloud platform when connected. Workstation mode disables this layer entirely.

02 · Execution

Local execution model

The local execution runtime never wraps proprietary binaries — it shells out to the tools you already have:

  • Terraform — found via which terraform; uses your existing CLI and your existing state backend
  • AWS CLI — uses your existing ~/.aws/credentials and ~/.aws/config profiles
  • kubectl — for ArgoCD-related operations (future)
  • git — for ReleaseOps repo introspection (future)

Every shell invocation is logged with full command, arguments (secrets redacted), exit code, and duration. The log is queryable from the local audit panel.

03 · Credentials

Credential bridge

Two credential paths, depending on operation:

  • Axiom session token — for syncing with the cloud platform. Stored in OS keychain. Never written to disk in plaintext.
  • AWS credentials — for local Terraform/CLI execution. Axiom never sees these. They live in ~/.aws/credentials (or your SSO config) and are read directly by the CLIs we shell out to.

04 · Workstation mode

Workstation mode

Workstation mode is for security-strict environments. When enabled:

  • All outbound network from the desktop app is disabled, except direct AWS API traffic
  • Operational memory persists locally only — no cloud sync
  • The Axiom cloud platform marks this connection as "offline"; web dashboard shows last-known state only
  • Audit logs export to local file system for SIEM ingestion
  • Reasoning runs against a local model (downloaded once) — no cloud inference

Workstation mode is part of the Enterprise tier. The local reasoning model is downloaded on first activation (~2GB).

05

Enterprise deployment

  • macOS — MDM/Jamf-managed deployment, signed enterprise pkg, configurable policy plist
  • Windows — MSI bundle with GPO policy, Active Directory authentication path
  • Linux — Ansible role + Debian/RPM packages, systemd service unit for daemon mode
  • Telemetry — opt-out at install time via policy file; workstation mode forces telemetry off
  • Update channels — pinned-version channel available for compliance-strict orgs (no auto-updates)

Trust questions

What does the desktop app do at runtime?

Renders the same operational UI as the web, plus shells out to local terraform/aws CLIs for execution, plus syncs with the cloud platform unless workstation mode is enabled.

Why is it safer than the web?

AWS credentials never leave your machine. Execution runs locally. Audit log persists locally. Workstation mode disables all outbound network.

Is it safe for regulated environments?

Yes — Apple-notarized + Microsoft-signed. Telemetry can be disabled at install time. Workstation mode + local reasoning available on Enterprise tier.

What gets stored locally?

Operational memory (encrypted), audit log, session token (OS keychain), optional local reasoning model. No source code, no AWS credentials.

Can I revoke?

Sign out + uninstall. OS keychain entries are removed on sign-out. Audit log can be exported before removal.

What if the org bans local AWS CLI usage?

Set Tauri policy to disable shell execution. Desktop app falls back to cloud execution path through the Axiom platform — same as web.

Need a human?

Most flows are documented — but we'll help if anything is unclear.

Talk to Vision XIX Labs