Documentation
How Aevico works
Acquire any data. Build intelligence. Automate actions. Docs cover platform architecture and operator how-tos. Pillars stay under Platform; Cybersecurity Intelligence and Observability Intelligence are application outcomes.
How Aevico works
Architecture
- Platform architecturePillars through governed action and domain applications.Read
- Three intelligence pillarsData Nexus, Threat Intelligence, and Observability—inputs, not apps.Read
- ContextWhere pillar signals become shared situational understanding.Read
- CorrelationRelationships and evidence across pillars.Read
- Knowledge graphEntities, relationships, and temporal linking.Read
- IntelligenceRisk, reasoning, and why a signal matters.Read
- AutomationGoverned action with approvals and auditability.Read
Acquire
- AcquireConnect sources and turn source content into structured items.Read
- SourcesAn external location Aevico polls into your workspace.Read
- Connect a sourceAdd RSS, HTML list, or a news API to the workspace.Read
- RSS sourcesPoll an RSS or Atom URL on an interval.Read
- HTML list sourcesCrawl a listing page; keep or drop article URLs by path.Read
- API sourcesNews-provider HTTP APIs with a stored credential.Read
- Configure ingestionHow Aevico fetches, extracts, and delivers items from a source.Read
- Normalize dataRSS, HTML, and API payloads become one item model.Read
- FeedsCategory streams published from your sources.Read
- Market IntelligenceSix MI capabilities on Acquire sources — ingest and search today; detection later.Read
Build intelligence
- MI source labelsEntity, events, signals, and topics saved on Market Intelligence sources.Read
- Build intelligenceSearch, monitor, and prepare acquired data for action.Read
- SearchPostgres full-text over items you already ingested.Read
- IndexingPostgres full-text index today; semantic search next.Read
- Watches and monitoringMonitor connectors. Same source form, separate list.Read
- SignalsKeyword matches of MI source labels against ingested items.Read
- IntelligenceStructured understanding on top of acquired data — Signals and Knowledge next.Read
Automate actions
- Automate actionsWHEN something happens → IF conditions match → THEN a channel.Read
- Alert rulesKeyword, category, MI detection, or source error → webhook or email.Read
- Alerts vs workflowsMatch-based notify versus generic WHEN → IF → THEN.Read
- WorkflowsItem created (optional delay) or interval → conditions → channel.Read
- Triggers and eventsWhen a workflow starts. Live: item.created and schedule.Read
- Conditions and rulesAND conditions on item fields after the trigger fires.Read
- ActionsWhat runs after trigger and conditions match.Read
- WebhooksHTTPS POST when an alert fires or a workflow runs.Read
- EmailNotify one address from an alert or a workflow.Read
- WhatsAppOfficial Cloud API. Opt-in recipients. Template or 24-hour session.Read
- LinkedInPublish a post through the official Posts API.Read
- Execution historyWorkflow runs, statuses, and provider responses.Read
Applications
- ApplicationsDomain outcomes on one spine—not extra pillars.Read
- News & MediaReal-time news pipelines, category feeds, and optional alerts.Read
- Market IntelligenceCompany and sector signals on MI sources, capabilities, and alerts.Read
- Cybersecurity IntelligenceSecurity outcome on Threat Intelligence + Observability + Context.Read
- Automotive IntelligenceVehicle, ECU, ADAS, and compliance context on the same spine.Read
- Observability IntelligenceOps outcome layer—health, anomalies, root-cause, and SLOs.Read
Developers
Account
47 articles on this site. Engineering notes on GitHub.