Control stays explicit
A ground control station handles consequential actions. UXDuck separates reading from changing, keeps local work local by default and makes the operator's decision visible.
Local-first vehicle connections
Installed UXDuck connects to vehicles from your computer. Browser simulations run in the browser. An account is not required to try a simulation or use the installed ground station.
Read access is not control access
MCP permissions separate reading from configuration and vehicle actions. Tools that can change a vehicle require the relevant permission and can be held for operator approval.
Actions return evidence
Commands report whether UXDuck refused them, the vehicle rejected them or the vehicle acknowledged them. Fresh telemetry and messages remain available to verify what happened next.
Product analytics avoid vehicle data
UXDuck's product analytics use bounded event categories. They do not include vehicle identifiers, parameter names or values, locations, messages, prompts, files or connection details.
Open source
UXDuck Core is open source under Apache 2.0. Read the code, fork it and build on it.
Security documentation will grow with hosted and remote-operation features. Current claims describe the product available today.
Try the working product first
Start a simulation in your browser. Install UXDuck when you are ready to connect hardware.