Appport is a software catalog for Relution-managed Windows 11 PCs. Users can find applications they have permission to install on their assigned device and request installs or updates. Relution handles the deployment.
Claude was used to polish and proof-read the code and documentation of this repository.
Status and limitations
Project status: Appport is an independent experimental project for software requests on Relution-managed Windows PCs. Developed independently alongside my main professional work. The work-in-progress alpha is a design reference for evaluation, not a ready-to-use deployment product. Windows builds are unsigned, and live Relution behavior still needs qualification in the intended environment.
Disclaimer. A catalog entry or successful local check is not deployment approval. Operators must validate permissions, device matching and installation outcomes. Reuse or adaptation requires appropriate licensing permission; this repository currently grants none.
Browser demo · Run locally · Documentation
Try the interface in your browser without an account. The demo uses fictional software, users, and devices; its actions install nothing and reset when you reload the page. If the hosted demo is unavailable, use the local commands below or see GitHub Pages setup.
The Windows client follows this flow; the browser demo simulates it:
flowchart LR
User["User on an assigned PC"] --> Appport["Appport: permitted software"]
Appport --> Request["Install or update request"]
Request --> Relution["Relution deploys the application"]
Relution --> Result["Appport checks device inventory for the result"]
These screenshots show the running browser demo in Chromium. The demo and Windows client use separate code, so the tour illustrates the interface rather than native Windows behavior.
Available lists software to install. Search by name or publisher, or filter by package source. The examples include a failed request you can retry and an unresolved request that stays locked for review.
Updates puts the installed and target versions next to each other. The demo follows your system's light or dark theme.
Install and Update ask for confirmation. In the demo, confirming starts a short simulation on the four-stage request track: Queued, Verifying installation, then Succeeded.
Expand Demo support details to see the fictional user, PC, and Windows information. The Windows client can also create a local support ZIP after the user confirms; the browser demo creates no files.
See screenshot notes for capture settings and refresh instructions.
The current version is 0.1.0-alpha.4. This alpha is intended for testing; Windows
builds are unsigned and not ready for distribution.
Known issues lists what testers should expect, and
Operations covers the Windows and live Relution checks.
Each Windows build is configured for one Relution organization, with its server origin, organization UUID, and Appport application UUID set at build time. The source can be configured for different organizations; the running client cannot switch between them. Appport specifically targets Relution and Windows.
The project does not yet have a license permitting reuse or redistribution.
Install Node.js 26.5.x and pnpm 11.6.0, then run these commands from the repository root:
pnpm install --frozen-lockfile
pnpm demo:build
pnpm --dir apps/web-demo exec vite preview --host 127.0.0.1Open the address printed by Vite. This serves the same browser build used for GitHub Pages. You do not need Windows, Rust, or a Relution account to try it.
Run the demo's checks with:
pnpm demo:verifyThe desktop app uses React, Tauri 2, and Rust. React renders the interface. Rust handles personal-token sign-in, Relution requests, device matching, Windows integration, and local state. A deployment is reported as successful only after Relution inventory confirms the expected package and version.
Use Rust 1.96.0 with Clippy and rustfmt alongside Node.js and pnpm. Running the native app or building an MSI requires Windows 11 x64 and the MSVC toolchain. Development covers setup and tests; Configuration lists the build inputs.
Run the full source checks with:
pnpm verify:sourceThis checks the desktop frontend, portable Rust code, architecture, documentation,
and build-verification tools. Run pnpm demo:verify separately for the demo.
Windows integration and live Relution testing are covered in
Operations.
| Directory | Contents |
|---|---|
apps/windows-client |
Windows app and command-line qualification utility |
apps/web-demo |
Browser demo with fictional data |
scripts |
Repository checks and qualification evidence tools |
docs |
Architecture, setup, operations, and release notes |
- AppPort design proposal: security basis, Relution comparison, illustrated workflows, and pilot acceptance (editable source)
- Architecture: components and request flow
- Development: setup, commands, and tests
- Configuration: build inputs, credentials, and diagnostics
- Operations: Windows builds and qualification
- Contributing: preparing a pull request
- Security: reporting a vulnerability
- Alpha.4 release notes



