Your deployment. Your taxonomy. Your name on it.
A co-deployment, not a product. When a client signs an Argus × agreement they get a named instance — Argus × [Client] — with all four modules, every region, a topic framework built around their work, and a dedicated engineer on-site for the first ~30 days.
The IPAC 12-category taxonomy
Everything modular Argus ships, plus what only ships here.
Argus × includes every module, every region, and the whole Argus engine. On top of that it ships a layer of custom, dedicated and co-branded work that does not appear in any modular price list.
Everything modular Argus ships
You lose nothing by going to Argus ×. Every module and every region pack is included by default.
- Argus Core — engine, dashboard, topic universe
- Argus Brief — twice daily, full delivery layer
- Argus Signal — curated legislator coverage (X + Facebook today; more on request), 7 languages
- Argus Trace — the full 10-tab entity dossier
- Argus Investigate — canvas, X-Ray, PDF export
- All three regional packs + Global — Americas, Europe, Indo-Pacific, Global (any parliament with a public record, on request)
- Ghost Pulse + nearby-region alerts — both always on
What only Argus × ships
The layer that never appears in the modular price list. Bespoke, named, co-branded, supported.
- Co-branded interface — Argus × [Client] throughout
- Bespoke dashboard — designed and built with you
- Custom taxonomy — your topic framework, not ours
- Additional markets — MENA, ASEAN, custom jurisdictions
- A dedicated engineer on-site for ~30 days, building with your team
- Custom feature builds against your spec
- A named engineering contact for the life of the deployment
- Hosted in your own cloud or on Argus-provided AWS/GCP · your encryption keys · audit-log mirror
30 days. Five phases. Live before the second sitting week.
Every Argus × engagement is led by a pair of engineers who work alongside your team for the first 30 days. They build to your topic framework and ship a named instance ready for production by the end of it. Custom features keep arriving after launch.
Scoping
Workshop your taxonomy, audiences, jurisdictions and additional markets. The final deployment spec is signed by your sponsor and ours.
Tenant + branding
Your branded Argus × [Client] workspace is stood up — in your own cloud, or on infrastructure Argus provides (AWS or GCP) if you’d rather we run it. Co-branding configured; your taxonomy mapped to the structure.
Dashboard build
A bespoke dashboard designed and shipped to your workflow. Daily reviews with you. Your data, your views.
Hardening
Custom feature builds against any blockers. Audit logging, single sign-on and access tiers configured. Testing against your live workflow.
Cutover
Live. Your named engineering contact takes over. The onboarding pair rotates out; the continuous-build channel stays open.
Your topic framework, shipped to production.
Core ships with a default set of topics. In Argus × you bring your own — nested, multi-language, mapped to the framework your analysts already use. IPAC’s 12-category framework is the reference; yours can be anything.
Sample · client-supplied taxonomy
Sample · mapped to the Argus structure
The institutions where this work is mission-critical.
Argus × clients are governments, ministries, parliamentary alliances, large NGOs, institutional research bodies and defence organisations. The requirements are highly specific. The deployment is co-built.
The full specification.
Every Argus × deployment is co-designed. The list below is the universal floor — most engagements ship additional bespoke work on top.
Built for institutions that need to get it right.
Argus is sold to parliamentary research services, foreign-affairs ministries and accredited civil-society institutions. We do not run self-serve trials — we run a 60-day paid pilot against your real workflow, with a named engineer on the account from day one.