The register connects each platform profile to official material, states the support it provides and identifies the scope that needs a demonstration.
Product material supports a description of a published offering. Framework references provide context for analytical and evaluation practices. The editorial questions are our synthesis; a source listing does not establish a hands-on test.
A documented five-part workflow connecting monitoring, assessment, people intelligence, research and response.
Confirm the proposed modules, exact source access, retained versions, exports and service commitments.
Return to the profile ↗A named narrative-intelligence product family with dashboard, feed, API and research-related routes.
Separate the dashboard, feed, API and service package. Request the exact output and access conditions.
Return to the profile ↗A public narrative-intelligence offering focused on story development, amplification and organizational response.
Validate the configuration and service scope against a representative issue rather than a generic product tour.
Return to the profile ↗Dedicated product descriptions for authenticity, coordination, amplification and narrative alerting.
Test ambiguous examples and request evidence, confidence and alternative explanations for classifications.
Return to the profile ↗Artemis product information describes warning, coordination analysis, API access and incident support.
Scope Artemis, other products, API use and incident services separately where required.
Return to the profile ↗Public descriptions of collection, network mapping, momentum detection and analyst-validated intelligence.
Agree the meaning of relationships, the role of agents, human review and exportable supporting material.
Return to the profile ↗An explicit distinction between standard public-source SaaS and a custom proof-of-concept-led system.
Keep the two products’ inputs, deployment assumptions, timelines and deliverables explicit.
Return to the profile ↗Public product positioning names continuous monitoring, mapping and several technical or managed delivery routes.
Validate source access, deployment options, integration formats and the included service separately.
Return to the profile ↗A current solutions page distinguishes Nebula, Echo and Janus and their respective roles.
Do not treat a broad platform description as the scope of every product or engagement.
Return to the profile ↗The Red Framework supplies a shared vocabulary for documenting influence operations. It is used here as context for describing behavior; it does not establish that a classification or attribution is correct in a particular case.
Read the framework ↗Voluntary guidance on trustworthiness in AI design, use and evaluation provides context for the guide on reviewing automated summaries. A reference to the framework is not a vendor certification.
Read the AI RMF overview ↗