Reference pages for people running, joining or extending Polari. The index below is
generated from one manifest (assets/docs.json); every page listed here exists.
What Polari is and how its projects fit together.
How Polari fits togetherThe four projects, the suite at a glance, what each is for.Demo termsWhat using a public demonstration instance means: no personal information, nothing is private or kept, demo accounts only, no warranty.Standing up an isle, installing without internet, and reaching Polari from your own devices.
Download PolariThe install bundle and platform debs, served by this site's own instance; per-app debs built on demand; the apt repository at apt.<domain>.Setting up a production serverpol prod guide: domain, certificate (auto-generated or provider-issued and auto-approved), logins, modules, installers — then it deploys the lean swarm profile.Install an isleThe Isle-Mesh getting-started: from a fresh machine to a running isle.Offline and air-gapped installThe offline medium: its sections, how it is built, and how an install refuses instead of fetching.Reaching Polari on your home networkOff-isle access over the LAN and what to expect from phones and laptops.pol and isle: both deployment routes from a terminal, by skill level and use — people, testers, developers, operators, AI assistants.
The Polari command lineTwo tools, two deployment routes, and what each kind of person — average user, tester, researcher, developer, operator, AI assistant — actually runs.pol CLI quick referenceEvery pol module and verb on one page.pol CLI architectureHow the suite CLI is put together.Extending the pol CLIAdding a module script to the suite CLI.isle CLI referenceThe isle command index.isle discoverScanning for isles, devices and apps.The isle, the archipelago and the mesh: what each level is, what crosses it, and who is in charge.
The networking and topology modelIsle, archipelago, mesh; the exposure ladder; measured paths; authority and consent.Isle VPNTwo providers, ten kinds, three placements; how it stands in for a managed overlay; why not Tailscale or Headscale.Which VPN app do I install?The ten kinds in plain words, the rule of thumb, and where each one runs.How devices join and get namesmDNS discovery, .local and .isle names, and the router's DNS.Dual-domain accessServing the same app under .local and .isle at once.Availability modesAlways-available by default, on-demand as the keystone for the rest.Fully open source, layer by layer: the operating system (DAC and MAC), the proxy, the firewall, the network — and what each depends on.
Security in PolariThe property we are after, the layers, how policy is declared and applied, every dependency with its licence.OS securityWho runs as whom (DAC) and what a process may touch (AppArmor, seccomp, sVirt), rendered per scenario and per app.Proxy securityOne nginx per world: the isle agent's ingress and the suite's edge — TLS, certificates, headers, doors.Firewall securityThe host firewall, docker's user chain, the isle router's zones, swarm ports — per scenario.Network securityContainment on the isle, the exposure ladder, Reticulum, VPN kinds and relays, encrypted overlays, known gaps.The parts of Isle-Mesh, the router, the agent, and taking an isle down again.
How Isle-Mesh is put togetherThe project's parts and how they relate.The isle routerThe OpenWrt router VM: images, VLAN, DHCP, DNS, firewall, the config library.The isle agentWhat runs on every member device: registration, the nginx ingress, the join daemon.UninstallingTaking apps, devices and a whole isle down cleanly.For developers: the standard app format, the dev loop, scaffolding, the frontend, testing.
The standard module and app formatpolari-app.json, the file conventions, objects one per file, the pol project loop, the registrar.Developer getting startedClone, build images, build debs, stand up an isle, run a node directly.Build, run and test the suitePrerequisites, environment tiers, the pol CLI, gotchas.Scaffolding a mesh appTurning a compose app into a mesh app that weaves itself into an isle.Mesh-app scaffolding referenceThe scaffolding package in detail.Mesh apps in DockerNetworks, DNS and lifecycle for containerized mesh apps.The shell bridge contractWhat the native app shells expose to the web frontend.The frontendThe Angular platform: displays as data, the no-code editor, CRUDE, live updates.Testing the frameworkTest suites, how to run them in containers, coverage.Lookup, not reading: remote access, environment configuration, the AI-facing surface.
Remote accessReaching a node from outside: the one-peer tunnel, DDNS notes.Environment configurationEvery environment variable the node reads, by tier.The MCP surface for AI agentsWhat an AI agent can read and propose through the Polari MCP server.Diagrams on this page are rendered client-side with Mermaid — an open-source, text-to-diagram tool — so the docs stay cheap to host and easy to edit. For the deep, interactive tools, follow the links into the full apps.
Three concrete projects plus the map that indexes them. The mesh is the fabric the others can run across; the baseline (OSEB) is where each capability is catalogued as a runnable module.
Everything sits behind one reverse proxy. This site (pol-hub) is the lightweight front
door; the heavier apps have their own frontends and backends.
No-code research and simulation: agroforestry, hydroponics, materials science, multi-scale simulation (FEM, DFT, MD), and FPGA/hardware — all as configurable objects.
Evidence-first scoring of policy, legislation, judicial decisions, and groups, with every score traceable to its sources and the scoring rules in the open.
Local-first mesh networking that keeps nodes connected without depending on centralized infrastructure.
A generalizable tech tree of the knowledge and tools an open economy needs — each node a working module, not just a description.
Polari