doona
doona documentation
Demo
English
doona documentation

doona documentation

doona is a static web UI for the native API that the daeuniverse engines share: honk today, dae once it implements the same contract. honk is a Rust transparent-proxy engine for Linux gateways; it serves doona itself at /ui/, or any web server can. doona shows what the engine is doing and manages nodes, groups, routing rules and configuration files.

Try the demo with sample data.

The activity page

Native API status

doona needs honk's native API, which exists only in builds from the feat/native-api branch of Glassyiris/honk and its rolling debug release. On that branch, native-api is opt-in; release and debug builds, including those attached to doona 0.1.0-beta.12, include it. Builds of daeuniverse/honk main reject every native_api setting as unknown experimental setting; /api and /ui/ answer 404. A build from feat/native-api without the feature stops with native-api feature is required when native_api is enabled. These pages were checked against debug.2026.9.30.native-api.5 (commit 25377686). Keys and defaults may change before upstream honk releases the API.

Pages

For a new gateway, read Requirements and the install page for your system, then the First run pages in order: Minimal configuration, Service management and First sign-in. After the first sign-in, continue with the Interface tour in Guides.

  1. Requirements: the kernel, the honk build, browsers and build tools.
  2. Install doona and honk-core on Debian or Ubuntu, Fedora or RHEL, Arch Linux, Gentoo, OpenWrt or another system.
  3. Installation details: the manual installation in one page, doona on another origin, distribution packages and updates.
  4. Minimal configuration: the smallest configuration that serves doona, and how to check it.
  5. Service management: run honk as a systemd or procd service; start, stop, reload and read the log.
  6. First sign-in: create the administrator and check the overview.
  7. Interface tour: pages, the top bar, panels and how changes are held, applied or saved.
  8. Watching traffic: Activity, System status, Connections, Routing log, DNS, Logs and Events.
  9. Routing, nodes and rules: policy groups, nodes and subscriptions, rules and Trace.
  10. Config and settings: the Configuration and Settings pages.
  11. Common tasks: step-by-step procedures for frequent changes.
  12. Configuration: an example honk configuration with the native API, and what each native_api field enables.
  13. Features: check each doona feature against the settings it needs, the resources each page reads, and the settings doona keeps in the browser.
  14. Troubleshooting: startup errors, the state database, a missing native API, sign-in and read-only sources.
  15. Development: build and test doona, the source layout and the API contract.
doona

doona documentation

English
doona documentationdoona is a static web UI for the native API that the daeuniverse engines share: honk today, dae once it implements the same contract. Requirements Install on Debian or UbuntuThis page installs doona from its .deb package and honk-core from the same doona release on Debian, Ubuntu and other APT-based systems. Install on Fedora or RHELThis page installs doona from its .rpm package and honk-core from the same doona release on Fedora, RHEL and other DNF-based systems. Install on Arch LinuxThis page installs doona from its .pkg.tar.zst package and honk-core from the same doona release on Arch Linux and other pacman-based systems. Install on GentooThis page installs doona with Portage from the ebuild in doona’s repository, and honk-core from the same doona release. Install on OpenWrtThis page installs doona and honk-core on OpenWrt 25.12 from the release archives. Install on other systemsThis page installs doona and honk-core from the release archives on a Linux system without a doona package, such as Alpine Linux. Installation detailsInstall honk, write its configuration, then install doona and start honk. Minimal configurationThis page writes the smallest honk configuration that starts honk and serves doona, then checks it by starting honk by hand. Service managementThis page runs honk as a systemd or OpenWrt procd service: it creates the service once, then lists the commands that start, stop, restart and reload honk and read its log. First sign-inThis page opens doona in a browser, creates the administrator account and checks that doona shows the running honk. Interface tourThis page shows where things are in doona after you sign in: the four navigation sections, the top bar, and the tabs, detail panels and action menus inside a page. Watching trafficThis page covers the Activity hub (Activity and System status) and the Monitor hub (Connections, Routing log, DNS, Logs and Events). Routing, nodes and rulesThis page covers the Routing hub: the Policies, Nodes and Rules pages. Config and settingsThis page covers the Configuration page, where you read, validate and apply honk's configuration files. Common tasksThis page collects short procedures for frequent changes to routing, traffic inspection and honk maintenance. ConfigurationThe configuration is two files. FeaturesFirst confirm that the gateway carries traffic. Troubleshooting DevelopmentRead CONTRIBUTING.md before opening a pull request.