Atlas Cyber Protect — How everything is linked (and what works together) ======================================================================= Date: 2026-08-08 Owner: FN.nology (fn.nology@gmail.com) Funnel: https://atlas-server.taile9cc75.ts.net This file is the ops/sales map of the LIVE product. Do not sell features that are not listed here as working. 1) BIG PICTURE -------------- Customer site Atlas server (Funnel) ----------------- ---------------------- Protect box (LAN) <-------> cyber_protect.sqlite + collab APIs portal :8787 Atlas Connect relay (ports 21115-21119) LAN scan / threats Chat web + APIs local Insights People / Approve / sessions Daily 02:00 Protect backup (NVMe) Windows PCs run "Atlas Cyber Protect Agent 0.4.5" Phones run "Atlas Cyber Chat 0.4.0" (Android) → Chat web Managers/users use ONE company email+password after Approve 2) TWO DIFFERENT LOGINS (important) ----------------------------------- A) Protect BOX login (top of portal) - Local account on that box OR owner fn.nology + Atlas master password - Unlocks Overview, Devices, Threats, Insights, Guardian, etc. on the box B) Atlas COMPANY sign-in (People tab) - Funnel collab Bearer token (acp_people) - Unlocks People list, Approve, Atlas Connect, Chat APIs - Same credentials for: Chat web, Chat APK, Agent account features Self-register from app/chat = pending until a Manager clicks Approve on People. Then the SAME email+password works for Chat + Connect. 3) ROLES -------- Manager = full company access (People, Approve, Connect company PCs, Chat, guest links, revoke-all, WFH approve, overtime) User = company Chat + Connect ONLY to assigned office PC Owner = fn.nology@gmail.com — Factory Guard + unattended Connect + owner tools 4) COMPONENTS AND DOWNLOADS (working) ------------------------------------ Protect portal (on box): http://:8787/ Example home kit: http://192.168.111.141:8787/ Optional Funnel front: https://acp-atlas-cyber-protect.taile9cc75.ts.net/ Living how-to (JSON driven): https://atlas-server.taile9cc75.ts.net/cyber-protect/how-to https://atlas-server.taile9cc75.ts.net/api/cyber-protect/guide Windows Agent 0.4.5: https://atlas-server.taile9cc75.ts.net/releases/public/windows/AtlasCyberProtectAgent-Setup-0.4.5.exe Latest alias: https://atlas-server.taile9cc75.ts.net/releases/public/windows/AtlasCyberProtectAgent-Setup-latest.exe Portable: https://atlas-server.taile9cc75.ts.net/releases/public/windows/AtlasCyberProtectAgent-Portable-0.4.5.exe Index: https://atlas-server.taile9cc75.ts.net/releases/public/windows/ Android Chat 0.4.0: https://atlas-server.taile9cc75.ts.net/releases/public/android/AtlasCyberChat-0.4.0.apk Chat web: https://atlas-server.taile9cc75.ts.net/cyber-protect/chat Atlas Connect API (product name only; secrets when signed in): https://atlas-server.taile9cc75.ts.net/api/cyber-protect/connect Relay host: atlas-server.taile9cc75.ts.net ports TCP 21115-21119 Sales brochure PDF: https://atlas-server.taile9cc75.ts.net/releases/public/marketing/Atlas-Cyber-Protect-Brochure.pdf This TXT: https://atlas-server.taile9cc75.ts.net/releases/public/marketing/Atlas-Cyber-Protect-How-Everything-Links.txt 5) PORTAL TABS — WHAT EACH DOES ------------------------------- Overview Live jobs, guardian feed, recent activity Devices LAN inventory; Install agent on selected Windows PCs PC Agents Paired agent antivirus / programs / version / updates People Company sign-in; Approve; Manager/User; office PC assign Atlas Connect Remote sessions; WFH; guest 15-min; revoke all Chat Company threads + link to full Funnel chat Traffic Side-box bandwidth talkers + services seen Insights Internet/DNS; network gear read-only; link warnings; agents Threats Hunt results; Fine / Neutralize Ask guardian On-box plain-language Q&A How to use Living guide (auto from guide JSON) How it works Side-box truth / limits 6) HOW DATA FLOWS ----------------- 1. Protect box scans LAN → local portal UI 2. Box heartbeats to Funnel (company/site status for Factory Guard owner) 3. Windows Agent pairs to box + reports AV/programs; uses Funnel for Connect/Chat login 4. People / sessions / chat messages live in Funnel cyber_protect.sqlite (company_id isolated) 5. Atlas Connect sessions: consent matrix → grant → client opens Atlas Connect engine 6. Daily 02:00: atlas-cyber-protect-backup.timer snapshots sqlite + people/chat + keys Latest: /mnt/M.2pool/atlas-vault/07-SYSTEM/backups/cyber-protect/daily/LATEST.tgz 7) SECURITY MODEL (short) ------------------------- - Per-company isolation in collab DB and chat media - Users cannot list/manage other staff or Connect to random PCs - Pending accounts cannot use Chat/Connect until Approve - Guest links expire; managers can revoke all remotes - Protect never becomes the customer gateway - Network gear credentials stored on the box (0600); read-only by default - Owner-only path for future mutate of gateways - Funnel HTTPS for APIs; Connect relay uses dedicated ports (not Funnel HTTPS) 8) PACKAGES (API tiers — working catalog) ----------------------------------------- GET /api/cyber-protect/packages/tiers protect = LAN devices/threats/agents/link_guard remote = + Atlas Connect / WFH / guest chat = + company chat (combined / full sold as Protect + Remote + Chat) 9) WHAT IS NOT A PROTECT CUSTOMER SKU ------------------------------------- Do not put these in Protect sales as included features: Atlas Neural app, Atlas Lore studio, Factory Guard (owner only), FN.nology DarkMoon (separate product unless quoted). 10) QUICK HEALTH CHECKS ----------------------- curl -sk https://atlas-server.taile9cc75.ts.net/api/health/ping curl -sk https://atlas-server.taile9cc75.ts.net/api/cyber-protect/guide curl -sk https://atlas-server.taile9cc75.ts.net/api/cyber-protect/connect curl -sS http://:8787/api/status systemctl list-timers atlas-cyber-protect-backup.timer 11) SOURCE FILES (for Cursor / restore) --------------------------------------- Portal: omni/cyber-protect-usb/agent/portal.html + portal_server.py Collab API: omni/cyber_protect_collab.py Core: omni/cyber_protect_core.py Guide: omni/atlas-cyber-protect-guide.json Brochure: omni/marketing/atlas-cyber-protect-brochure.html Backup: /usr/local/bin/atlas-cyber-protect-backup.sh Agent: /mnt/M.2pool/atlas-clients/atlas-cyber-protect-agent/ (0.4.5) END — keep this file updated when Protect features change (same rule as living guide).