[ In-house product ]
AWEB Client
The modular desktop platform by BRATUX: it brings web software to the physical workstation — with an integrated module store for licensing, distribution and updates.
[ The gap between browser and workstation ]
The gap between browser and workstation
Web applications are powerful — but the browser ends at the edge of the screen. Hardware login, document scanners, local files and device interfaces remain out of reach for web apps.
AWEB Client closes exactly this gap: it embeds the web application in a desktop runtime and extends it via modules — controlled, licensable and centrally managed.
[ Two components, one platform ]
Two components, one platform
Client and store belong together: the client extends the web app at the workstation, the store delivers modules licensed and encrypted.
Desktop runtime
AWEB Client
A plugin-first runtime for Windows: the client loads the web app, extends it via modules and provides UI overlays, browser automation and hardware access — governed by a capability system.
- Plugin loader with dependency resolution and version management
- Capability system: modules only get the permissions they declare
- Overlay UI: panels, sidebars, widgets and full-screen views
- Works offline — keeps running even without a store connection
Licensing & distribution platform
AWEB Module Store
The central server manages the module catalog, licenses and rollout. Modules are delivered encrypted and signed per station — including an admin dashboard and a self-service portal for tenants.
- License models per station, user or tenant
- Encrypted, signed module packages per station
- Admin dashboard with role system and audit log
- Self-service: activate and configure modules without IT support
[ Modules in the catalog ]
Modules in the catalog
The client grows through modules — every feature is its own package with declared permissions.
iButton Autologin
User switching via hardware key right at the workstation — in seconds, no password typing.
Roaming Autologin
The session follows the user between stations — work wherever it's needed.
Scan & GDT
WIA/TWAIN scanners and GDT device files wired straight into the web app's workflow.
Send and file emails directly from the workstation context.
Station
Register, name and assign workstations to modules.
Module Manager
Install, update and configure modules — right inside the client.
Client Helpers
Shared workstation utilities that feature modules build on.
Web Bridge
The embedded web app and the workstation exchange actions in both directions.
[ Security & operations ]
Security & operations
Built for production use in sensitive environments.
Signed distribution
Every module package is signed server-side — the client only loads verified modules.
Per-station encryption
Modules are delivered encrypted per station; keys stay bound to the station.
Capability model
Modules declare their permissions explicitly — no implicit full access.
Licensing & audit
Central license management with role system and audit log via the Module Store.
[ In production ]
Running behind AWEB workstations
AWEB Client runs in production at medical practices as the desktop shell around AWEB — the cloud-based practice management software by quentis. How the project came together and what we learned is covered in the case study.
Read the case study[ Contact ]
Bringing web software to the workstation?
Desktop clients, plugin systems or licensing platforms — talk to us.
Contact us