Arch Linux
Arch, EndeavourOS & compatible systems
.pkg.tar.zstsudo pacman -U ./aula-studio-0.5.0-1-x86_64.pkg.tar.zstLINUX KEYBOARD SOFTWARE
A native Linux configurator
for the original AULA F75.
01 / INSTALLATION
No Node.js or Rust needed for a binary package. Install once, then launch AULA Studio from your application menu.
x86_64 packages. GNU/Linux with GTK 3 and WebKitGTK 4.1. Requirements & other architectures ↗
Arch, EndeavourOS & compatible systems
.pkg.tar.zstsudo pacman -U ./aula-studio-0.5.0-1-x86_64.pkg.tar.zstDebian 12+, Ubuntu 24.04+, compatible Mint releases
.deb / amd64sudo apt install ./aula-studio_0.5.0_amd64.debFedora with WebKitGTK 4.1
.rpm / x86_64sudo dnf install ./aula-studio-0.5.0-1.x86_64.rpmExtract and run; system GTK/WebKitGTK libraries required
.tar.gz / x86_64./aula-studio-0.5.0-linux-x86_64/bin/aula-studioVerify checksumsManual updates · No automatic hardware configuration
Requires Rust, Node/npm and native libraries. See the distribution-specific prerequisites.
git clone https://github.com/Dahuum/aula-studio.git
cd aula-studio
npm --prefix app ci
npm --prefix app run build
cargo build --locked --release -p aula-studio -p aula-cli
./target/release/aula-studio02 / HARDWARE SUPPORT
Current configuration support is for the original ANSI F75 in wired mode. F75 Pro, Max, ISO layouts and other revisions are not assumed compatible.
USB 258a:010c / interface 1
Full compatibility matrix ↗
New in0.5: local workspaces for F87 variants, F108, H108, S75 Pro, S99 Pro, F108 Pro and F98 Pro. These are offline editors; their hardware controls remain disabled. Models & research status ↗
| Operation | Status |
|---|---|
| Detection & configuration reads | Hardware verified |
| Theme switching | Owner confirmed |
| Brightness change & restoration | Hardware verified¹ |
| Per-key RGB, remapping, media, sleep | Validation pending |
| Onboard macros & wireless configuration | Unavailable |
| Power-cycle persistence & other revisions | Unverified |
¹ Brightness 6 → 5 → 6. Both writes read back; all five configuration banks restored exactly. Software tests are separate from physical validation. Test record ↗
03 / THE APPLICATION
Explore the actual editors in demo mode before connecting a keyboard. The application runs locally, without Wine, a browser configurator or a privileged service.
Effects, brightness, speed and custom colors. Unvalidated write scopes are documented.
Focused recording, editing and offline preview. Onboard macro uploading is unavailable.
04 / DEVICE CHANGES
Startup, reconnection and profile saving do not change your keyboard. Supported writes require a backup and a separate confirmation.
Profiles stay on your computer until you explicitly apply them.
Check the device, affected settings and saved before-state.
Success requires matching readback. Failures are unconfirmed, without automatic retry.
05 / QUESTIONS
Not yet. Hardware coverage and the original UI recreation are incomplete. Onboard macro uploads, wireless configuration and several device settings remain unavailable or under investigation.
No npm package, AUR entry or Flathub listing is published. Use a native package above. npm is only needed when building the frontend from source. A reviewed AUR recipe is available in the repository; a recipe is not a published AUR package.
No single binary covers all Linux systems. The downloads target x86_64 GNU/Linux with GTK 3, WebKitGTK 4.1 and glibc 2.36 or newer. The installation guide distinguishes tested distributions from compatible but untested derivatives. Alpine/musl, ARM binaries and older distributions are not covered by these packages.
Run the app as your normal desktop user. Packages include a narrow uaccess rule for the wired F75. Reconnect after installation. The app does not replace drivers or install a privileged background service.
Yes. Choose Enter demo mode in the app. Demo changes stay in memory; local profiles and macro preview do not configure hardware or inject input into other applications.
Static analysis can recover protocols, layouts and formats from their Windows software. Communication, hardware revisions and safe persistence still need physical validation. Researched models must be labeled separately from hardware-verified models. Expansion policy ↗