Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.leedab.com/llms.txt

Use this file to discover all available pages before exploring further.

A local AI brain — running on a spare Mac, Windows PC, or Linux box in your office — that powers Artificial Beings. ABs watch the systems your team already uses, take the next step, route approvals, and close loops automatically. Five ABs ship in-box; custom ABs in 1–2 weeks.
Any operations, logistics, finance, or back-office team still running repetitive cross-tool workflows by hand — 3PLs, manufacturers, freight forwarders, distributors, and companies where work bounces between five tools before it closes.
Inside the appliance in your office, behind your firewall. Nothing goes to a LeedAB cloud — there isn’t one. In air-gap mode, internet egress is physically blocked.
On-device models and, where you allow it, frontier models accessed under your own contract. Model choice is made at deployment — including all-local for export-controlled customers.
Yes. In air-gap mode, models are pre-baked and the brain never calls out. Every classification and memo is produced on-device.
The hardware boundary is the security model. Most teams use a Mac Mini (8 GB RAM).
14 days. Day 0 is the appliance arriving. Days 1–3 are surface enrollment. By day 14, first reports shipped and first commit chased.
No. Chat is one interface — WhatsApp, Telegram, Slack, Teams, or email. LeedAB is built to run workflows: monitor systems, reconcile data, draft artifacts, update tools, escalate exceptions, and close the loop.
No. LeedAB works through browser portals, inboxes, spreadsheets, PDFs, and app screens the same way your team does. APIs help when available, but are never required.
We don’t replace them — those are systems of record. LeedAB is the operator that does the work between them.

Contact

Book a call

30 minutes with a solutions engineer.