Every claim on this site, with its evidence.
Every factual number on argos-os.com is written into the page as a claim id, not as text. That id has to exist in one file — src/data/claims.json — with a status, a scope, the evidence behind it, and a link to a third party where a third party can check it. This page is that file, rendered. If the evidence is removed from the ledger, the number disappears from the site. If a page cites an id the ledger does not contain, the build refuses to compile and nothing ships. We made the honesty structural rather than cultural, because culture does not survive a launch deadline.
22 claims · 4 independently verifiable · 2 marked unfinished · last verified 2026-07-27
Three statuses. No fourth one that flatters us.
There is a fourth status in the file. It is called red, it means do not ship, and the build treats it as a fatal error: a page carrying a red-listed claim will not compile. It is there so that a claim we have stopped being able to defend can be revoked in one place, by one line, without anyone needing to remember which pages it appeared on.
The scope column is the part most vendors leave out. A number without a scope is not a measurement — it is a mood. We have zero• Argos OS customers today, so every operational figure below comes from our own practice, and says so.
All 22 claims, in ledger order.
Rows appear in the order they exist in the file. We do not re-sort to lead with our strongest evidence. Every row is addressable — the footnote marker beside any number on this site links straight to its row here, for example /proof.html#audit-rows.
| Claim | Status | Scope | Evidence | Verify |
|---|---|---|---|---|
| 165,000+ hash-chained audit records | AMBER | our own environment | Argos Kernel public.audit_log = 165,815 rows at time of verification. Rounded down and expressed as a floor so the published figure cannot go stale in the wrong direction. | our own environment |
| The database refuses to alter its own audit log | AMBER | our own environment | public.audit_log carries three enforcement triggers (audit_log_no_update, audit_log_no_delete, audit_log_no_truncate). The application role holds INSERT and SELECT only. A live UPDATE attempt returns: ERROR: audit_log is append-only: UPDATE is not permitted. Ask us to run it against your own tenant on day one and watch the output. | reproduce it yourself, day one |
| Our audit chain head is anchored in Bitcoin block 959874 | GREEN | independently verifiable | Overwatch audit chain head 6c33de7d657cbc55afc3427b8da20dbedf67372f669c68e84270e7929fde641c was stamped via OpenTimestamps at 19:05 UTC on 2026-07-27 and confirmed in Bitcoin block 959874 at 22:52 UTC the same day. We do not control the Bitcoin blockchain, which is the entire point. | mempool.space ↗ |
| 164,356 events emitted, 100% delivered | AMBER | our own environment | Argos Kernel public.event_outbox: 164,356 rows total, 164,356 published, 0 unpublished. Every write is captured in the same transaction as the data it describes, so an event cannot be lost without losing the write. | our own environment |
| 84 self-hosted source repositories | AMBER | our own environment | Our self-hosted Forgejo instance reports 84 repositories. We self-host the expensive substrate — identity, source control, secrets, timestamping — so no per-seat license tax flows through to your bill. This describes our infrastructure, not yours; Argos is hosted by us for you. | our own environment |
| 26 client companies run on it today | AMBER | our own environment, not customer scale | Argos Service t_intelamation.clients = 26. These are the clients of our own managed-services practice. We have zero external Argos OS customers today — this is the MSP we run ourselves, not fleet traction. | our own environment |
| 1,301 tickets resolved end to end | AMBER | our own environment | Argos Service t_intelamation.tickets: 1,277 closed + 24 resolved of 1,303 total. Our real lifetime number is higher — we ran on SyncroMSP and Freshdesk before this and that history did not come with us when we left. We cannot prove it, so we do not count it. | our own environment |
| 18 compliance frameworks | AMBER | our own environment | Argos GRC framework library, distinct frameworks mapped once and reused across tenants. Counted as distinct names, not rows. | our own environment |
| 300 monitors | AMBER | our own environment | Argos Watch public.monitors = 300 across our own estate, with live uptime published publicly. | watch.intelamation.net ↗ |
| 27 products — 19 live, 4 in beta, 4 still in build | AMBER | our own catalog | 27 products in the catalog: 19 carrying a live badge (including 4 free public tools), 4 beta, 4 in build. We publish the breakdown rather than a single flattering total, and the ones marked in-build are real code we are not ready to put in front of you yet. | our own catalog |
| Running our own MSP since 2013 | AMBER | our own environment | Intelligent Automation, LLC has operated as a managed services provider since 2013, in Fairfield, NJ. Argos OS is the platform we built to run it. | our own environment |
| Zero Argos OS customers today | AMBER | stated plainly | Argos OS soft-launches in September 2026. Every operational number on this site comes from the MSP we run ourselves. When that changes, this page will say so. | our own statement |
| Containment takes two human approvals | AMBER | our own environment | Argos Overwatch requires 2-of-2 distinct approvers before the control plane will sign an isolate_host command. The single exception is confidence-tiered break-glass on endpoints you have explicitly enrolled: critical confidence isolates after 60 seconds, high after 180 seconds, medium and low never auto-act. Isolation is reversible network containment — nothing is deleted. | our own environment |
| Overwatch containment is built and dry-run verified, not yet proven in production | ROADMAP | not finished | The detection to alert to PSA-ticket path is live. The control plane, cross-platform agent and isolate_host command are built and verified end to end in dry-run only — we have not yet applied a live firewall lockdown on a production endpoint. We would rather tell you that than demo something that falls over. | not finished |
| ConnectWise ScreenConnect authentication bypass, CVSS 10.0 | GREEN | public record | CVE-2024-1709, CVSS v3.1 base score 10.0 CRITICAL, CWE-288 authentication bypass, affecting ScreenConnect 23.9.7 and prior. Mass-exploited in 2024. | nvd.nist.gov ↗ |
| ConnectWise disclosed a nation-state breach in May 2025 | GREEN | public record | On 28 May 2025 ConnectWise disclosed that a sophisticated nation-state actor had breached its environment, reaching a small number of cloud ScreenConnect customers. Linked to CVE-2025-3935 (7.2 NIST / 8.1 CNA, HIGH), patched 24 April 2025. Google Mandiant engaged. Scope stated as ConnectWise reported it. | nvd.nist.gov ↗ |
| Kaseya’s own RMM was the ransomware vector in 2021 | GREEN | public record | The July 2021 REvil supply-chain attack against Kaseya VSA reached roughly 60 MSPs and an estimated 1,000–1,500 downstream businesses, via the remote-monitoring product those MSPs had installed to protect them. | cisa.gov ↗ |
| The whole platform, white-labeled, free for 30 days | AMBER | our published offer | At soft launch in September 2026 we stand up a completely white-labeled Argos instance for you, at no cost, and you run it for 30 days. No card, no onboarding fee, no annual or multi-year contract. | our published offer |
| Pricing published at launch | ROADMAP | not published yet | Our CEO is setting the numbers. They go on this page the day we open — not behind a call. We would rather show you an empty price field than a fake one. | not published yet |
| Managed Cybersecurity Service Provider | AMBER | our own descriptor, not a certification | MCSP describes the space between an MSP and an MSSP: we manage our customers’ cybersecurity, but we do not claim to be an MSSP. No governing body issues it. It is what we do, not a credential anyone awarded us. | our own descriptor |
| Halcyon’s ransomware warranty | AMBER | partner-provided, terms set by Halcyon | Anti-ransomware in Argos is powered by Halcyon, which offers a ransomware warranty toward expert incident-response and recovery services after a covered incident. The warranty is provided by Halcyon, not by Intelligent Automation, and is subject to Halcyon’s own conditions and eligibility — confirmed at onboarding. | halcyon.ai ↗ |
| Cyber warranty through Cork | AMBER | partner-provided, terms set by Cork | The cyber warranty available under Argos is provided by Cork Protection, Inc., a warranty provider built for MSPs, with underwriting via DataStream. Cork states coverage options from $25K to $500K, an average payout time under one hour for initial funds, and a 14-day full reimbursement window for covered events. Those are Cork’s stated figures. Eligibility, covered events and terms are set by Cork and confirmed during onboarding. Intelligent Automation is neither the insurer nor a broker. | corkinc.com ↗ |
22 rows · ledger order preserved · last verified 2026-07-27
What would make us change a number.
A ledger is only worth reading if it is capable of moving against the person who publishes it. Ours has three rules, and they are the same three rules regardless of which direction the number goes.
The third rule has already cost us the most flattering number we own. We report 1,301• tickets resolved end to end. Our real lifetime figure is considerably higher — we ran on SyncroMSP and Freshdesk before this, and that history did not come with us when we left. We cannot prove it, so we do not count it.
That is not a humility exercise. It is the origin of a product decision: Argos exports everything you put into it, any day, in a format you can read without us, at no cost. We have been the customer standing there holding the empty box, and we built the export because of it.
If you find a claim on this site that you believe the evidence does not support, tell us and we will either produce the evidence or remove the claim. [email protected] — Intelligent Automation, LLC, 336 US Highway 46, Fairfield, NJ 07004.
Don’t trust us. Check us.