Ordinary web apps: pages, data and simulations that run on your isle's Polari.
10 app(s) match in Polari Apps.
appstore polari-app
Polari App Store (appstore-1): installable native shells over the polariapps content layer — catalog/identity, one-time enrollment tokens (hashed at rest), overlaid Gradle source archives + prebuilt binaries from MinIO.
hardwareapps library
Hardware apps as rows: KVM guests the isle defines (relay, guest network, …) and extension apps pushed into them; pure renderers for the libvirt domain XML (the router template generalised) and OpenWrt UCI profiles (hw-app-1, 2026-09-08).
hwmap polari-app
Hardware map: an on-device scanner (usb, pci + IOMMU groups, serial by-id, nics, kvm/libvirt facts) pushes a snapshot; Polari keeps ports and slots as rows and answers what can be mapped to a potential KVM (usb hostdev, pci vfio, nic macvtap) with reasons, and which hardware apps each port satisfies (hwm-1, 2026-09-08).
islemesh polari-app
isle-mesh convergence (mac-1): the polari-side acceptor for isle-mesh data — devices/uplinks/mesh-apps/protocol-permits ingested from the isle agent's registry.json + nginx fragments (isle stays authoritative over networking); mock ingests carry mock_network=true, surfaced as a banner. Feeds /display/isle-mesh and the mac-10 console.
iso polari-app
Get Polari and Ubuntu onto a new computer: probe a device from a USB stick, derive Ubuntu compatibility, plan its role, build an unattended installer ISO with Polari inside, install from the same Ventoy stick.
polariapps polari-app
Polari-Apps: module configurations per use-case, plan-first + exportable.
resources polari-app
Node resource inventory, module profiles, admission advisor. Moves in wave 5; core still imports it statically (drop refuses).
suiteapps library
Suite apps: purpose-oriented compositions of apps of every kind (Polari modules, isle containers, hardware KVM guests, extension apps) with the object contracts between parts and a placement plan across devices (sa-1, 2026-09-08).
terms polari-app
Terms of service: versioned documents (global or per app) and the append-only acceptance ledger
testing polari-app
Accountability spine (opt-in: registers only on test builds / explicit POLARI_MODULES).
The standard installer format on Ubuntu and other Debian-family Linux — the equivalent of a setup file on other systems. Your computer's own Software Install app reads it, shows what will be installed, and asks for your password through the system dialog. Nothing runs until you approve it.
Online is small: it carries the app itself, and the libraries it needs are fetched from the internet when the app is set up — each card lists those libraries and their measured sizes, so nothing downloads invisibly. Offline carries the pip libraries INSIDE the deb (bigger, slower to generate — wheels are fetched at build time), for machines that will have no internet. System engines (e.g. a SPICE simulator) can never ride inside an app deb — they come from the distro's packages or the offline install media, and each card names them.
These debs are not kept on the server — each one is packaged fresh at the moment you ask (analyze shared payload → package module files → write manifest → assemble deb → stream to you), then kept at least three slow-connection downloads long, then only evicted when room is needed, and freed after a day untouched. The wait shown on each card is the median of that app's recorded generation times — measured, never invented.
Pre-prepped files are built ahead of time and sit ready on this server, so the download starts instantly. Generated on demand files are packaged fresh at the moment you ask for them — you wait briefly while the server builds your copy, and the server deletes its copy after delivery instead of keeping a duplicate on disk. Each item on these pages says which kind it is.
When two apps contain identical files, those files are factored into one shared deb both apps depend on, so the content installs exactly once — the installer enforces it. Install the shared deb first; each app card links it when it applies.
Installing an app deb stages its code and data under /var/lib/polari/apps/. The running instance admits staged apps through the dynamic-modules machinery, which is still in review — until it lands, an administrator has to admit the module on the instance manually. This page will say so until that changes; nothing happens invisibly.
Programs install into the system software areas (/usr, /opt) and app data lives under /var/lib/polari. The .deb file you downloaded is only the delivery vehicle — once the install finishes it is safe to delete from your Downloads folder.
← Install Polari itself: the platform installers, online and offline, and the USB stick.