Y

Yaroslav Vikhariev

Founder · Editor-in-chief
Pronounshe/him
Based inBelgrade
LanguagesEN · RU · DE
Published74 pieces
Tested4,200+ runs
FOUNDER EDITORIAL LEAD PRICING DESK AGENT TESTING

Yaroslav Vikhariev

Founder and editor-in-chief at AI//COST. Twelve years building software before AI tooling — last role engineering lead at two YC-backed companies. Now runs the pricing parsers, leads agent testing methodology, and signs off on every editorial ranking before publication.

Pieces published
74
Test runs
4,200+
Corrections issued
3
Years in software
12
§ 01

Background.

Editorial role →
Born1990 · Russia
CurrentlyBelgrade, RS
EducationBSc CS · 2012
Career start2013 · backend eng.
YC alumni2× founding eng.
Joined AI//COSTMarch 2025
StatusFounder · 100%

Yaroslav started AI//COST in March 2025 after spending three months unable to find a single trustworthy comparison of Claude Code, Cursor, and Aider for his own evaluation. Every existing source was either vendor-marketing or single-author blog posts running 3-5 prompts and calling it a review. The gap was obvious; the project was the answer.

Before AI//COST he spent twelve years in software engineering — last as founding engineer at two YC-backed companies (one B2B SaaS, one developer tools), before that as backend lead at a fintech in Berlin, before that as full-stack engineer at startups in St. Petersburg. The technical depth shows up in the methodology: he writes the pricing parsers himself rather than outsourcing to a freelancer, runs SWE-bench reproductions on his own hardware, and has personally installed every coding agent in the directory.

He's not an AI researcher. The site doesn't pretend otherwise. The expertise here is the practitioner kind — what 4,200+ test runs and 12 years of engineering judgment produce, not what an ML PhD produces. That distinction matters for what we cover: tool-use questions, cost economics, real-world workflow fit, agent reliability, integration patterns. Not architecture papers or training-method critiques.

On the editorial side he is editor-in-chief — final sign-off on rankings, corrections approval, methodology versioning. The 3-reviewer panel for editorial rankings includes him plus M. Krause and A. Park. When the panel disagrees, joint re-review is logged. He can be overruled by panel consensus and has been (twice — once on Cursor's #1 ranking in 2025, once on the τ-bench leader call in early 2026; both logged in corrections).

When he's not running the desk, he's contributing to open-source agent tools (aider contributor since 2024) and writing about testing AI tools without becoming one of those people who just runs ChatGPT through a five-question gauntlet and calls it a benchmark.

§ 02

Coverage areas.

PRIMARY · 38 PIECES

Coding agents

Claude Code, Cursor, Aider, Windsurf, Devin. Reviews, comparisons, install guides, migration paths. Personally tested every agent in the directory.

PRIMARY · 21 PIECES

Pricing economics

Cost-per-task math, blended rates, prompt caching impact. Owns the pricing parser pipeline. Calculator math reviewed by him.

SECONDARY · 9 PIECES

Benchmark methodology

SWE-bench reproductions, τ-bench setups. Co-leads benchmark page maintenance with A. Park; runs the actual reproductions himself.

SECONDARY · 4 PIECES

Open-source tools

Aider contributor, OpenCodex tester, Continue extensions. Writes about OSS coding agents and where they actually beat commercial.

OPINION · 2 PIECES

Industry analysis

Long-form takes on the agent ecosystem. Used sparingly — when the take is genuinely his and not synthesized from coverage.

DOES NOT COVER

Image & video gen

He doesn't write about Midjourney, DALL-E, Runway, etc. — that's M. Krause's desk. Stays in his lane.

Out of scope
§ 03

Credentials + work.

LinkedIn →
2025–
Founder + Editor-in-chief at AI//COST
CURRENT
2024–2025
Founding engineer at YC-backed B2B SaaS (developer-tools)
YC W24
2022–2024
Founding engineer at YC-backed dev-tools startup · Series A 2023
YC S22
2018–2022
Backend lead · fintech in Berlin (~30 engineers)
LEAD
2013–2018
Full-stack engineer · two startups in St. Petersburg
IC
2024–
Open-source · Aider contributor (12 merged PRs); OpenCodex beta tester
OSS
APR 2026
Speaker · "Reproducing SWE-bench in 14 hours" · AI Engineer Summit, San Francisco
TALK
FEB 2026
Cited in The Information · "How indie pricing trackers reshape AI buying"
PRESS
NOV 2025
Speaker · "Cost-per-task economics for AI agents" · LocalAI Conference, Berlin
TALK
2012
BSc Computer Science · ITMO University, St. Petersburg
DEGREE
§ 04

Recent filings.

§ 06

Editorial accountability.

Corrections process →

What he can't accept

  • Vendor-paid coverage. Sponsored content is not written by editorial staff.
  • Free product samples conditional on positive reviews.
  • Speaking fees from companies whose tools we rank.
  • Equity in any AI tool company we cover.
  • OK: press passes to AI Engineer Summit, NeurIPS, etc. (declared in coverage).
  • OK: open-source contributions to tools we cover (declared on profile pages).

Conflicts of interest

Currently none beyond the open-source contributor status to Aider (12 merged PRs, no compensation). Disclosed on every Aider-related profile and ranking. He recused himself from one Aider-vs-Continue ranking decision in March 2026 — full log at /corrections/.

He holds no equity in any AI tool company. Has been pitched 6-figure equity grants to leave editorial work; turned them down to maintain editorial independence. The desk is funded by display ads + non-influencing affiliate links + sponsored slots quarantined per our sponsorship policy.

Get in touch.

Story tips, corrections, sourcing questions. Direct contact preferred over DMs.

Editorial [email protected]For story tips, fact corrections, or methodology questions. Replies within 5 business days.
Press [email protected]For citations, interviews, podcast bookings. Send full brief upfront.
Vendor outreach [email protected]Goes to the editorial inbox, not direct. Methodology applies regardless of who's asking.
Public @yaroslav on 𝕏 · github.com/yaroslav · LinkedInDMs open but slower than email. Don't pitch via DM — use editorial@.