AIMO Docs

Appearance

Architecture ​

How the agent talks to AIMO ​

AIMO’s cloud hosts the web UI and coordinates work. The AIMO Agent runs only in your environment, usually as a container you control. There is no network path from AIMO to your database; raw rows do not leave your network.

  • Outbound session — The agent opens the connection from your side (for example TLS). You do not expose databases or the agent to the public internet for normal operation.
  • Job requests — AIMO sends work to the agent as a fixed set of job types (profiling, monitor calculation, validation, and similar—not arbitrary code). See Operations.
  • Aggregates and metadata only — What returns to AIMO are summaries and monitor outputs: counts, distributions, schema fingerprints, check results—not bulk table exports.

Inside your perimeter, the agent connects to your database for profiling and checks; that traffic stays local.

Diagram: AIMO cloud on the left; on the right a secure box containing your database and the AIMO Agent. Arrows show job requests and outbound session between cloud and agent; a green arrow labels aggregates and metadata only. No link exists from the cloud to the database.
Isolation by design: AIMO never connects to your database; only aggregate data crosses to the cloud.

End-to-end flow ​

This matches Getting started step by step:

  1. Sign in — Web UI (hosted with AIMO’s cloud) for agent registration, connections, analysis, and table onboarding.
  2. Register an agent — Pair the agent with your account using a registration token; tooling writes identity material and usually aimo_agent.sh. See Registration.
  3. Add database credentials — Secrets go through the agent, not the browser—typically ./aimo_agent.sh add or python -m aimo.agent.cli with the same environment. Credentials are stored encrypted; the agent decrypts them for jobs. See Agent CLI.
  4. Run the agent process — A long-lived agent process (e.g. ./aimo_agent.sh agent) keeps the outbound channel so AIMO can dispatch Operations jobs when you analyze, calculate monitors, or validate artifacts.
  5. Analyze, select tables, accept — You analyze the connection, choose tables, then accept. AIMO assigns monitor definitions; see Monitors.

After accept, pipeline steps (deeper analysis, time blocks, monitor definitions, historical values, outlier modeling, past alerts) run primarily on AIMO workers, using aggregates and artifacts from the agent—not raw row exports. The agent continues to run only database-facing job types.

See the product site for pricing and positioning.