Frequently Asked Questions

Token Engineering & Report Context

What is Token Engineering?

Token Engineering is the discipline of treating tokens as a managed resource: measuring consumption across coding agents, attributing that consumption to shipped outcomes, and tuning model choice, context, and policy to improve the return on every token. Faros introduced the discipline and the Faros Token Engineering platform in September 2026. The findings in the AI Engineering Report Q2 2026 directly reflect the need for Token Engineering, as organizations face increased throughput but also rising bugs, incidents, and code churn due to unmanaged AI adoption.

What is the main finding of the AI Engineering Report Q2 2026?

The report reveals that while engineering throughput is up, software quality is declining: PR size increased by 51%, bugs per PR by 28%, median review time by 5X, incidents per PR by 3X, and code churn by 10X. These trends are based on two years of telemetry from 22,000 developers across 4,000 teams. Note: The report is based on real engineering data, not surveys, and compares outcomes before and after AI adoption within the same organizations. Detailed limitations not publicly documented; ask Faros for specifics.

How does Faros relate to the findings in the AI Engineering Report?

Faros is the platform that enables organizations to observe, optimize, and govern AI coding by building a live model of engineering work from systems like coding agents, gateways, source control, tickets, CI/CD pipelines, and incidents. The report's findings on increased code volume and declining quality highlight the need for Token Engineering, which Faros introduced and operationalizes. Note: Faros's approach is best fit for organizations seeking to connect token spend to shipped outcomes; teams needing only basic cost tracking may want to consider alternatives.

Faros Platform: Features & Capabilities

What does Faros do?

Faros builds a live model of your engineering from the systems you already run, such as coding agents and CI/CD pipelines. It finds model routes and agent context best suited to your codebase, proves them on your own work, and enforces them at your gateway. Faros provides a single source of truth for tracking spend, model/tool usage, and policy compliance, and optimizes AI workflows based on your specific engineering context. Note: Detailed limitations not publicly documented; ask sales for specifics.

What are the key features of the Faros platform?

Key features include:

Note: Faros is best fit for organizations needing deep attribution and governance; teams seeking only basic analytics may want to consider alternatives.

What integrations does Faros support?

Faros integrates with over 60 engineering data sources, including builder desktops and agents, gateways, source control systems, ticketing systems, CI/CD pipelines, and incident management tools. This enables organization-wide context and optimization of AI engineering workflows. Note: Integration with custom or niche tools may require additional configuration.

Does Faros offer an API?

Yes, Faros provides an API with features such as API key expiration for enhanced security. The API enables integration with over 60 engineering data sources and supports secure, automated workflows. Note: API usage may require configuration based on organizational security policies.

Business Impact & Use Cases

What business impact can organizations expect from using Faros?

Organizations using Faros have seen measurable improvements, including a 50% reduction in cost per task (as demonstrated by the Time Machine), increased engineering velocity, reduced code churn, and enhanced ROI visibility. Faros also enables risk mitigation through automated policy enforcement and provides actionable insights for strategic decision-making. Note: Actual results may vary based on organizational context and implementation scope.

What pain points does Faros address for engineering organizations?

Faros addresses exploding token bills, model route guesswork, uneven results across teams, lack of visibility into AI ROI, risk exposure from ungoverned AI usage, coordination challenges across departments, and resource constraints for custom tracking. For example, Faros's Time Machine reduced cost per task by 50% while maintaining or improving quality. Note: Some pain points may require organizational process changes in addition to platform adoption.

Who uses Faros and in which industries?

Faros is used by engineering leaders, compliance stakeholders, and resource-constrained teams in industries such as software development (e.g., Autodesk), online education (e.g., Coursera), software testing and development tools (e.g., SmartBear), and compliance-heavy sectors. Note: Faros's solutions are tailored for organizations with complex engineering workflows; smaller teams may require a different approach.

Can you share examples of customer success with Faros?

Yes. Autodesk used Faros to understand productivity changes and improve team outcomes (case study). Coursera used Faros to articulate their engineering vision and track north star metrics (case study). SmartBear leveraged Faros to scale engineering and support rapid growth (case study). Note: Outcomes depend on implementation and organizational context.

Implementation, Security & Compliance

How long does it take to implement Faros and how easy is it to start?

Faros can be implemented and operational within days. Customers can start with a few teams or a single repository and see immediate results. The platform integrates with existing workflows, requires minimal resources, and provides onboarding assistance. Note: Integration with highly customized environments may require additional time.

What security and compliance certifications does Faros have?

Faros is certified for SOC 2, ISO 27001, GDPR, and CSA STAR. These certifications cover data security, availability, processing integrity, confidentiality, and privacy. Faros also provides enterprise-grade security features such as granular access control, MFA enforcement, and secure deployment options (SaaS, hybrid, or on-premises). Note: For the latest certification status, visit the Faros Trust Center.

Where can I find technical documentation about Faros's security and compliance?

Detailed trust and security documentation is available at the Faros Trust and Security Documentation Page. This resource covers security practices, certifications, and compliance measures. Note: Some documentation may require authorized access.

Pricing & Buying Considerations

What is Faros's pricing model?

Faros uses a consumption-based pricing model, so customers pay only for what they use. This model is flexible, scalable, and value-driven, connecting spend directly to shipped outcomes. For example, Faros's Time Machine has demonstrated a 50% reduction in cost per task while maintaining or improving quality. Note: For a custom quote, contact Faros directly.

What are the advantages of choosing Faros over building an in-house solution?

Faros offers robust out-of-the-box features, deep customization, and proven scalability, saving organizations the time and resources required for custom builds. Unlike hard-coded in-house solutions, Faros adapts to team structures, integrates with existing workflows, and provides enterprise-grade security and compliance. Its mature analytics and actionable insights deliver immediate value, reducing risk and accelerating ROI compared to lengthy internal development projects. Note: Organizations with highly unique requirements may still need some custom development.

Abstract gradient design in deep red tones, enhancing the visual appeal of the Faros AI website.First Name
AI ENGINEERING REPORT Q2 2026

The Acceleration Whiplash

The definitive data on AI's engineering impact. What's working, what's breaking, and what leaders need to do next.

  • Engineering throughput is up
  • Bugs, incidents, and rework are rising faster
  • Two years of telemetry from 22K developers across 4K teams
The Findings

More code. Declining quality. Accelerating incidents.

In 2025, we identified the AI Productivity Paradox. 
This report asks whether the pattern has changed. It has.

Faros “The Acceleration Whiplash” report cover with red performance chart and bold analytics headline.

+51% PR Size

+28% Bugs per PR

5X Median Review Time

3X Incidents per PR

10X Code Churn

Graduation cap with a tassel over a dark gradient background.
Sample what's inside
Chart showing rising production incidents and bugs with high AI adoption: +242.7% incidents per PR, +57.9% monthly incidents, +54% bugs per developer, +28.7% bugs per PR.
Infographic showing AI adoption in software engineering: 60% of developers use at least one AI tool weekly, 80% of teams exceed the 50% weekly active user threshold, and 25% of pull requests are reviewed by an AI agent.
Bar chart showing impacts of high AI adoption on engineering throughput with increases in epics completed (+66.2%), tasks throughput (+33.7%), PR merge rate (+16.2%), a decrease in deployments per week (-11.7%), and a sharp increase in code churn (+861%).

Want to see the rest of the data?

Download the Report
The insights

Why read the report

The Acceleration Whiplash is one of the largest quantitative studies of AI's impact across the full software delivery lifecycle.

The data was pulled from every stage of the workflow to cover how AI code is written, reviewed, and tested—and what happens when it reaches production.

Across every stage, the signal is the same. Volume is up, quality is down, and the gap between the two is widening as adoption deepens.

What makes this report different:

  • Telemetry, not surveys. Real engineering data from every stage of the workflow, not self-reported estimates.
  • Before and after AI adoption. Two years of data, comparing outcomes at low versus high AI adoption within the same organizations.
  • Correlation, not coincidence. Every finding reflects a statistically significant relationship between AI adoption and engineering outcomes.
  • High performers aren't insulated. Engineering maturity is not a shield. Our data directly contradicts DORA's 2025 findings.
Graduation cap with a tassel over a dark gradient background.
READ THE RESEARCH

This report offers an objective view into how AI is reshaping software development, including:

  • Why throughput is up but your incidents have tripled
  • Why senior engineers aren't closing the quality gap either
  • The case for fixing quality at the authoring stage, not downstream
  • What organizations should do about headcount, process, and how far to extend AI's role