AIMO Docs

AIMO documentation ​

Technical guides for deploying the agent, connecting databases, and operating monitors in your environment. AIMO runs a Docker agent inside your network: it queries your databases locally and returns only aggregates and metadata, never bulk raw rows. The cloud generates the monitors, rolls an expected value forward from each monitor's own history, and opens an episode when the readings build enough suspicion. Larger organizations can run the whole platform on-prem instead.

New here? Start with Getting started, or read What is data quality monitoring? for the concepts behind the product.

Guide ​

  • Getting started: account, agent registration, credentials, analysis, and the tables you start monitoring
  • Architecture: cloud, agent, and database boundaries; how work flows
  • Security: identity, credentials, jobs, and what crosses the network
  • Monitors: the closed set of monitor families, how AIMO assigns them, and how they compile into bounded queries
  • Outlier detection: the expected value, suspicion, the alert budget, and episodes

Agent ​

  • Registration: registration token vs supplying your own public key
  • Agent CLI: register, start, and the connection commands
  • Operations: the fixed set of job types that run on the agent
  • Agent source: the agent's source tree, as shipped

Concepts ​

  • What is data quality monitoring?: the failure modes monitoring catches, common approaches, and how AIMO's AI-generated, privacy-preserving approach works
  • Glossary: plain-language definitions of data quality and observability terms
  • FAQ: short answers on raw-data privacy, AI-generated checks, supported databases, security, alerting, and pricing

See the product site for pricing and positioning.