One orchestrator, a few leads, and workers that do the repetitive work. Every consequential decision waits for you. Four short surveys and you are set up.
Tell Layan what it is working with. Nothing here is guessed later.
Pick the numbers that matter. Layan shows each one only when it is observed from a connected source. Until then it says unknown.
Choose departments and the workers under them. Amber is the default colour. Every gated action waits for a person unless you say otherwise.
Upload what your agents should know. Text, Markdown, CSV and JSON are read and indexed into key points here in your browser. PDFs are listed as assets until a backend reads them.
Key points become company memory. Corrections stay scoped to a project unless you promote them. Choose where memory lives.
Layan's Hermes answers by default and spends credits. Your own Hermes spends nothing. Keys stay in this browser and travel only with your own requests.
1. Paste this into your Hermes CLI. It switches on Hermes' API server for this site and answers with the details Layan needs.
2. Paste Hermes' one-line answer here.
On this machine (127.0.0.1) the browser talks to Hermes directly and every call is written to your usage ledger at 0 credits. A public address (a tunnel to your Hermes) is called by Layan's server instead. Private LAN addresses are refused by both. Your Hermes can run on any provider you like, including the Claude subscription plugin; that stays on your machine and is never shared.
The key never leaves this device in this preview. In production it goes to the server-side secret manager, never into model context.
What Layan will set up, and what it will not claim yet.
Your answers are attached so nobody asks you twice.