Aimeterly icon

Aimeterly

Aimeterly is a managed SaaS for Claude Code usage analytics, estimated cost tracking, productivity metrics, and optional audit logs.

Aimeterly

Overview

Aimeterly is a managed SaaS for tracking Claude Code usage, estimated cost, productivity, and audit data across an organization. It is designed for admins and engineering managers who want a shared dashboard instead of piecing together telemetry from separate tools.

The product works by having an organization administrator distribute one configuration snippet to Claude Code. Aimeterly then receives telemetry at a dedicated endpoint and shows usage data, cost estimates, productivity signals, and, when enabled, content-capture audit logs within a few minutes.

Key features

Usage analytics by organization, user, and model

Track DAU, WAU, MAU, sessions, and tokens by model at the organization and user level so you can see adoption depth instead of only aggregate totals.

Estimated cost visibility

View estimated cost by user and model using API-equivalent pricing, with period-over-period comparison to identify heavy users and changing spend patterns.

Productivity metrics

Follow lines of code, commits, pull requests, and suggestion acceptance rate over time to connect Claude Code use with engineering output signals.

Optional audit log and content search

Capture prompts, responses, and tool input/output only when your organization opts in, with keyword, user, and capture-type search across the retained data.

Managed setup and deployment

Start from a single configuration snippet that can be delivered through the Claude Team / Enterprise admin console or as managed-settings.json, with no extra development required.

Fast time to first data

See new telemetry appear on the dashboard within minutes after the settings are distributed and Claude Code is used.

Common use cases

  • Measure organization-wide adoption

    Use DAU, WAU, MAU, sessions, and token usage to see whether Claude Code is being adopted across teams or concentrated in a few users.

  • Track AI spend by user and model

    Rank users by estimated cost and compare models to identify heavy spenders before budgets or usage patterns drift too far.

  • Connect usage to productivity signals

    Review lines of code, commits, pull requests, and acceptance rate alongside usage to discuss whether Claude Code is contributing to engineering output.

  • Review captured content for governance

    When content capture is enabled, search prompts and file edits by keyword, user, or capture type to review records that match an internal rule or question.

  • Deploy monitoring with minimal setup

    Roll out Claude Code telemetry with a single settings snippet through the admin console or managed-settings.json, then check the dashboard after members start using the tool.

Pros and Cons

Pros

  • No extra development is required to get started; the setup flow is a configuration rollout rather than a code integration.
  • Data appears within minutes, which makes adoption and usage visible soon after rollout.
  • The dashboard combines usage, cost, productivity, and optional audit views in one place.
  • Default collection is limited to usage metadata, with prompt and response content excluded unless content capture is enabled.
  • The product offers a free tier and a trial, which lowers the barrier to evaluation.

Cons

  • Cost figures are estimates derived from telemetry and may differ from actual bills from Anthropic or cloud providers.
  • Audit log content capture is optional and requires explicit enablement, so the product does not capture prompts and edits by default.
  • Some distribution paths depend on organization-level administration in Claude Team / Enterprise or device management with managed-settings.json.

FAQ

How do you connect Claude Code to Aimeterly?

It appears to work in two supported distribution paths: an organization administrator can paste the settings snippet into the Claude Team / Enterprise admin console, or deploy a managed-settings.json file on each machine. In both cases, Claude Code then sends telemetry to Aimeterly's dedicated endpoint and the dashboard updates within a few minutes, usually within about five minutes.

What data is collected by default?

By default, Aimeterly receives usage metadata such as user identifiers, team attributes, model names, token counts, and estimated cost. Prompt, response, and tool input/output content are not sent unless your organization explicitly enables the corresponding capture type.

Which Claude Code environments are supported?

The setup guide says the service works where you can distribute settings through the Claude Team / Enterprise admin console or via managed-settings.json. It also notes that server-managed settings are not delivered when using third-party providers such as Amazon Bedrock, Google Cloud, or Microsoft Foundry.

Does Aimeterly support content capture?

Yes. The setup guide says content capture is optional and off by default, and that enabling it requires the Pro plan or above, including the trial period. The pricing page also lists content capture on Pro and Enterprise, while Free includes usage and cost dashboards and an audit log without content capture.

Are the cost figures the same as my bill?

No. The site says the costs shown in Aimeterly are estimates derived from telemetry at API-equivalent pricing and may differ from billing by Anthropic or cloud providers. They are intended for comparison and trend analysis rather than exact invoice matching.

Quick Facts

Category
Claude Code analytics
Website
aimeterly.com
Primary users
Admins and engineering managers
Setup time
About 5 minutes
Deployment model
Managed SaaS
Pricing
Free tier, Pro, and Enterprise