Introduction

Autter has three complementary products:

• Autter platform reviews proposed changes before merge.
• Autter CLI records AI authorship as developers and coding agents edit code.
• Autter Runtime tracks errors and usage in your app after that code ships.

You can use any product independently, or connect them for team-level attribution and analytics.

​

Autter platform

The Autter platform is an AI code review product for pull requests and merge requests. It uses the current diff, codebase context, team rules, linked work items, and scanner output to find issues before merge. The platform can help you:

• find bugs, edge cases, and security risks
• apply team standards written in natural language
• summarize a pull request and its architectural impact
• suggest concrete fixes
• run linters, security scanners, and pre-merge checks
• measure review cycle time and team activity

Autter works alongside human review. It handles repeatable checks and surfaces context so reviewers can focus on architecture, product behavior, and risk.

​

Autter CLI

The open source Autter CLI records explicit AI authorship. Coding agents report which lines they changed, so Autter does not need to guess whether code was written by AI. The CLI links AI-authored lines to the coding agent, model, and prompt context. You can inspect that information with commands such as autter blame and autter stats.

​

Autter Runtime

Autter Runtime is an open source, lightweight runtime telemetry system — a dependency-free browser error and usage tracker paired with a curated Node OpenTelemetry setup, both funneling into a self-hostable ingester. The Runtime can help you:

• capture unhandled and handled errors from the browser and the server
• trace requests with standard OpenTelemetry on the backend
• see per-route usage and error rollups, grouped per repository
• self-host the ingester, or use Autter’s hosted endpoint

​

How the products fit together

​

Next steps