The problem is not “another CMDB SaaS.” The problem is on-prem Windows vs AWS lift-and-shift
(or any two SDLC inventories) and whether software, services, tasks, certs, firewall, IIS, disks,
network, and OS actually match. Run Invoke-ServerInventory.ps1 as Administrator, upload
the ZIP/JSON (magic-byte check, 50 MB, filename de-dupe). Profiles pair a baseline with targets.
Engine: 26 categories, ranked critical/warning/info. AWS-native exclusions,
per-profile ignored rules, global path exclusions. HTML/PDF plus remediation, executive, trends,
fleet views. Registry: 28 seeded hostnames, 5 environments; auto-register unknown names; baseline
per env. Haiku writes a short executive summary. Scheduled compare endpoints exist but are
not in Kronos today — manual unless you wire them. Collector overview pages are
login because they show vuln-shaped data. EUPM’s server picker reads this registry.
Agentless collector. Comparison is in Postgres JSONB per module, not a live WinRM session from Flask.
Not AWS Console. Not a Qualys screenshot.
IIS, certs, firewall, tasks, SQL instances, drivers…
Not in meltuc-pipeline or kronos_jobs. Manual or you wire it. Telegram+Herald summaries if you do.
Decommission/reactivate. Drift history per host. Collector marketing pages are behind login.
Will not WinRM from gunicorn. Public landing lists no hostnames.
Parity audits. Not a vulnerability scanner (that is PCRM/Nessus).
No invented AWS Config recorder.
Login for /secp/app. This page is not your fleet.
Open SECPRequires a MelTuc account. Create one free.
Validate parity between on-premise Windows servers and AWS lift-and-shift counterparts. Health stays cheap. If this page disagrees with the signed-in app, trust the app — the product contract and tests enforce that rule.