What isn’t finished yet.
Every vendor in this category has a list like this. We’re the only one that publishes it. Below is what we’ve built but wouldn’t yet put in front of your clients, and exactly why.
13 open items · 3 capability holds · 2 commercial · 4 in beta · 4 in build · last reviewed 2026-07-27
We would rather lose the deal than demo something that falls over.
A roadmap badge is not an apology. It is the reason you can trust the things we do call live. If a vendor never publishes a gap, one of two things is true: the product has no gaps, or the list exists and you are not allowed to see it. You already know which.
So we hold every capability to the same three bars before the word live goes anywhere near it. The bar is not “does the code run.” The code runs on all thirteen items below.
One clarification, because it matters more than the rest of this page. “Unfinished” on this list only ever means polish, breadth, or proof at scale. It never means an unresolved security weakness, an unprotected piece of your data, or a capability we have claimed elsewhere and cannot back. Those are not roadmap items. Those are stop-ship, and they do not appear on a webpage — they appear in a commit that reverts something.
Built, verified, and still not called live.
These three are the ones we would most like to put on the front page. They are the three we are most careful about, for exactly that reason.
Argos Overwatch — containment
Not production-provenThe intended path is: a detection fires, an analyst sees it, two humans approve, and the endpoint is cut off the network before the ransomware finishes enumerating the file share. Most of that path is running today. The last step has never been taken in anger.
Argos Verify — fleet rollout
RoadmapVerify exists to kill the help-desk vishing call — the one where a confident stranger talks your technician into resetting an MFA factor. The mechanism is transaction-bound: the challenge commits to the exact action being approved, so an approval harvested for one thing cannot be spent on another.
Argos Connect — the gateway layer
RoadmapConnect replaces the flat client VPN with identity-gated, per-application access built on an open zero-trust overlay. That much is real and running. What it is not yet is a whole secure-access edge, and we are not going to blur the two.
Two things a prospect is entitled to and cannot have yet.
Pricing
RoadmapThe commercial model is settled and we will state it here in plain language: priced per technician, published openly on this website, no per-feature taxes appearing on a later invoice, no multi-year agreement that quietly auto-renews, and the whole platform white-labeled free for 30• days with no card.
What is not published yet• is the number. David Levin, our CEO, is setting it. It goes on the site the day we open — not behind a discovery call, not behind a form, not behind a rep who quotes you differently depending on how you sound on the phone. We would rather show you an empty price field than a fake one.
our published commitmentCustomers
September 2026We have zero• Argos OS customers today. Every operational metric on this site comes from the MSP we run ourselves — a real practice, operating since 2013•, with real clients who notice when something breaks.
There is a version of this website with a logo wall on it. We could have written “trusted by leading MSPs” and nobody would have audited the sentence. Instead every figure carries a scope tag telling you exactly whose environment it came from, because a number without a scope is not a measurement — it is a mood.
our own environmentWe report 1,301• tickets resolved end to end. Our real number is higher — we ran on SyncroMSP and Freshdesk before this, and that history didn’t come with us when we left. We can’t prove it, so we don’t count it. That’s why Argos exports everything, any day, at no cost. We’ve been the customer holding the empty box.
That is not a humility exercise, and it is not on this page to make us look good. It is the origin of an entire product pillar. The reason you own your data in Argos is that we once did not own ours, and it cost us the most flattering figure we will ever have.
Four products in real use, not yet in front of your clients.
Beta here means what it is supposed to mean: we run it, it works, and we can still name the thing about it that would embarrass you if you resold it tomorrow.
Argos Concierge
BetaWorks — a service desk living in Slack and Teams, with AI triage, deflection and a no-code playbook engine, running against our own desk daily.
Missing — the interface is mid-migration into Argos Vantage, and deflection confidence still needs tuning per tenant, because every MSP’s clients ask the same questions in a different tone.
Why beta — an AI that answers your client confidently and wrongly is worse than no AI at all. The deflection threshold has to be conservative by default, and proving that per tenant takes tenants.
Argos Cadence
BetaWorks — authored templates dispatch as no-login magic-link runs, completed runs file themselves into Compass, and the finished evidence lands in GRC without anybody re-uploading a PDF.
Missing — the AI-assisted authoring pass, and breadth in the prebuilt library. The engine is solid. The shelf is thin.
Why beta — we will not advertise a template library we have not actually written. Onboarding, offboarding and incident runbooks are done; the long tail is not, and a half-written SOP is worse than a blank page because people trust it.
Argos Canaries
BetaWorks — decoys planted across file shares, cloud identities, internal sites and DNS, silent until touched, with every trip triaged by our own SOC rather than dumped into your queue.
Missing — self-serve deployment. Today we place and monitor them for you by hand, which is the right way to do it and the wrong way to scale it.
Why beta — near-zero false positives is the entire value of deception, and it only stays near zero while placement is deliberate. The moment we hand you a self-serve button we inherit the alert fatigue we built this to avoid.
Cyber Warranty
BetaWorks — eligible clients carry a cyber warranty through Cork Protection•, with posture tracked in-portal so coverage strengthens as the score climbs. Anti-ransomware carries Halcyon’s ransomware warranty• alongside it.
Missing — a self-serve eligibility path. Enrollment is a conversation today, not a checkbox.
Why beta — because both warranties are provided by our partners, underwritten by them, and governed by their terms — not ours. Intelligent Automation is neither the insurer nor a broker, and we would rather say that in the product than in a footnote somebody reads after a claim is denied.
Four products that are real code and not yet a promise.
These exist. You can see them. They are counted honestly inside the 27• products in the catalog, which is why we publish the breakdown rather than a single flattering total.
Argos Endorse
In buildWorks — envelopes, the signing flow, certificate-of-completion generation and a hash-chained, tamper-evident evidence bundle we run on our own infrastructure instead of renting a seat from a third party that then holds your executed documents.
Missing — complex multi-party routing at volume, and an adversarial review of the evidence bundle by somebody whose job is to attack it.
Why in build — an e-signature product that fails when a document is challenged costs you more than a DocuSign invoice ever did. Court-ready is a claim you get to make once.
Argos Reports
In buildWorks — report definitions pulling live across the suite — SLA and ticket volume from Service, posture from Red, assets from Compass, control status from GRC — rendered to PDF in your brand, not ours.
Missing — the scheduler, template breadth, and sealing every generated PDF back into Compass as audit evidence. That last part is partially wired and we are not going to describe partially wired as done.
Why in build — a QBR deck is the one artifact your client’s board actually reads. A number that is wrong in that room does not cost us anything. It costs you the account.
Argos Patch
In buildWorks — deployed and running: ringed rollout, maintenance windows, auto-halt and a kill switch, fed by the CVE brain in Argos Red and dispatched through the RMM and directory you already use.
Missing — the safety gates are built but not yet enforced by default, the publish collectors are incomplete, and the operator interface is being rebuilt.
Why in build — patch automation is the fastest way in this entire industry to break a fleet in one click. We prove the brakes before we sell the accelerator, and until the gates are enforced by default rather than by discipline, it is not finished.
Argos Proof
In buildWorks — the flow is wired end to end for enrollment, signing and step-up, wrapping a specialist provider for document and selfie proofing so that no identity document is ever stored by Argos.
Missing — the production vendor account. That is the honest and slightly embarrassing answer: the remaining blocker is a commercial API key, not a line of code.
Why in build — because we are not going to run identity proofing against a sandbox and describe it as live. It stays here until it is verifying real people.
The page is only cheap to write if the list is short and true.
A platform assembled by acquisition cannot put this page on its website. Not because its engineers are worse — many of them are excellent — but because the moment the list is honest it is also long, and the moment it is published it becomes the competitor’s slide. So the list stays internal, the prospect finds out during implementation, and the industry learns one more time that the demo was the product.
We can publish it for a boring reason. We are the ones who have to live in this software on Monday. Everything above is a gap in a tool we use to run our own practice, which means every item on this list is also an item on our own backlog, ranked by how much it annoys us. That is not a moral position. It is just what happens when the vendor is also the operator.
Read this page next to the claim ledger and you have the whole picture: what we assert with evidence attached, and what we have not earned the right to assert yet. There is no third document. That is the entire company, on two pages.
Don’t trust us. Check us.
When something moves off this page, it moves onto the ledger — with the evidence attached.
Not into a launch announcement. Into a row, with a status, a scope, and somewhere a stranger can go to check it without asking us anything. Soft launch is September 2026, and the whole platform is white-labeled and free for the first 30• days — no card, no onboarding fee, no lock-in. We stand it up for you.