Umami

Workflows the agent can manage

• track traffic
• measure events
• review acquisition
• report site performance

Agent operability

Editorial agent-readiness estimate: 4/5. This reflects documented interfaces and proposed workflows, not a successful installation or a support promise. Assessment date not recorded; verify upstream documentation before use.

• REST — Self-hosted API exposes application operations and analytics data; official TypeScript API client covers every API endpoint

Evidence consulted

• Official install docs document Node.js 18.18+, PostgreSQL 12.14+ and supported self-hosting paths. [stated; https://docs.umami.is/docs/install]
• Official API docs state that application operations are available through the API. [stated; https://docs.umami.is/docs/api]

Implementation notes

Use for owned product/site analytics; use PostgreSQL for current v3, change the default admin password before exposure, review current advisories, and expose only the metrics needed for recurring operations.

Licence / edition: MIT repository licence; verify hosted/commercial product terms and branding separately. Upstream also offers a hosted service. Umami v3 standardises self-hosting on PostgreSQL; MySQL is no longer supported in v3.

Resources: light class — Current Umami v3 guidance requires Node.js 18.18+ and PostgreSQL 12.14+ but does not publish a trustworthy RAM/CPU baseline; event volume drives storage and sizing. (inferred)

External prerequisites: websites/applications able to add tracking

Security: Fresh installs create the default login admin / umami; official install guidance says to change the default password immediately after first login. Current upstream advisories include a high-severity advisory published 2026-06-30; inspect the advisory and current patched release before internet exposure. Catalogue qualification is not a security certification; inspect current advisories, supported versions and deployment guidance before setup.