Learn

Any tuning or logging platform that exports CSV. We have optimized normalizers for bootmod3 (BM3), MHD Flasher, EcuTek, COBB Accessport, Hondata, HP Tuners, JB4, and more, but any CSV with standard engine parameters will work. The parser auto-detects your platform from the column headers. Don't see yours? Let us know. We actively add new platforms based on community requests.

We have deep engine profiles for BMW N54, N55, B48, B58, S55, S58, plus expanding support for Toyota/Subaru FA24DIT, Honda K20C1, Nissan VR30DDTT, VW/Audi EA888, and Porsche 9A2 EVO. If your engine isn't profiled yet, the analysis still works. It uses conservative thresholds and notes that engine-specific calibration is pending. We're always adding new engines, so if yours isn't listed, request it and we'll prioritize based on community demand.

The scoring engine uses engine-specific thresholds calibrated by professional tuners and automotive engineers. Each report also includes a confidence band (High / Medium / Low) that reflects how much data was available. More channels, longer WOT pulls, and a higher sample rate all increase confidence. That said, no automated analysis replaces a qualified tuner's judgment. We flag issues and give you data-backed context so you and your tuner can make informed decisions.

Log after every tune revision and after installing new hardware (downpipe, intercooler, injectors, etc.). For track or drag use, logging every session helps catch heat soak trends and wear patterns. Street drivers should log whenever something feels off, or a few times a year to keep an eye on long-term health. If you upload multiple logs, TBK Logs shows score trends across sessions so you can spot gradual changes.

Your use case (Street, Track, Drag, Drift, or Mixed) tells the scoring engine how to weight each category. A street car cares most about Drivetrain and daily drivability. A track car weights Drivetrain (especially partial throttle response for corner exit), Ignition, and Temperatures highly, since sustained load, heat soak, and precise throttle response all matter on circuit. A drag car weights Boost and Fueling because peak power on a single pull is everything. Drift weights Temperatures and Drivetrain because sustained sideways abuse generates massive heat and demands predictable power. Picking the right use case ensures the scores and recommendations match how you actually drive the car.

Yes. Upload multiple logs to the same tune version and TBK Logs will show score trends and delta comparisons. This is especially useful for before/after hardware installs. Upload a log before the upgrade and one after, and you'll see exactly how each scoring category changed.

Your health score is built from 5 categories, each scored 0-100: Boost (is actual boost tracking target?), Fueling (is fuel delivery keeping up under load?), Ignition (is the engine knocking or pulling timing?), Temperatures (is heat building faster than cooling can handle?), and Drivetrain (is the ECU silently cutting power?). Per-category penalties are capped to prevent any single area from dominating your overall score. Categories are then weighted based on your use case (street, spirited, track, drag, daily) to produce the final score. See the "Understanding Your Report" tab for full details.

TBK Logs gives you two types of recommendations. Mod Path is about hardware: physical upgrades like an intercooler, HPFP, downpipe, or injectors. Items are prioritized by impact and include what the data shows, what to upgrade, expected score improvement, and estimated cost. Tune Recommendations are about calibration: changes your tuner can make in the ECU map, like adjusting boost targets, timing tables, fuel trims, or rev limits. Both are based on what your log data actually shows, not generic advice. Always address hardware bottlenecks before asking for more from the tune.

Typically under 30 seconds. The scoring engine parses your CSV, maps channels to canonical names, runs 5 evaluators across your data, computes the mod path, and generates the full report. Larger logs (100K+ rows) may take slightly longer.

Drivers upload and analyze their own logs. Tuners manage multiple client vehicles. Key differences: Tuners get unlimited uploads, a client management dashboard, the ability to upload on behalf of clients, and a unique tuner code. When a driver signs up using your tuner code, they're automatically linked to your account and you earn 70% of their subscription for as long as they stay subscribed and you maintain an active Tuner or Tuner Pro subscription. Referral commissions are subject to our Referral Program Terms. Tuner Pro adds custom branding, higher limits, API access, and priority support. The analysis engine and scoring are identical across all plans.

Absolutely. Keeping track of your car's performance and vitals is always a good thing, stock or modified. A stock car gives you a clean baseline, and if anything starts degrading over time (fuel pump wear, cooling efficiency, timing behavior), you'll catch it early. If you do modify later, you'll have before-and-after data to prove exactly what changed.

A WOT pull (full throttle from ~3,000 RPM to redline, 5+ seconds in 3rd or 4th gear) is ideal for boost, fueling, and knock analysis under peak load. But non-WOT data is equally important. Partial throttle behavior, IAT rise and recovery between pulls, coolant trends, torque delivery at varying loads, and thermal patterns across a session all matter. For track use especially, the partial throttle data (corner exit, braking zones, sustained load) can reveal issues that a single WOT pull never would. Log your full session, not just the pulls.

On any analysis page, click "Share Report" to generate a unique permanent link. Anyone with the link can view the full report without needing an account. You can also export as PDF or HTML from the same page. Shared reports include the full analysis: health score, category breakdown, findings, charts, and recommendations.

Go to Settings in the dashboard. Your subscription status and management options are in the Subscription section. Cancel anytime. Your access continues until the end of your billing period.

Yes. Your logs and analyses are stored securely on Supabase infrastructure with row-level security (RLS) policies, meaning your data is isolated at the database level and only accessible by your authenticated account (and your linked tuner, if you have one). All data is transmitted over HTTPS/TLS encryption. We do not sell, share, or use your data for any purpose beyond your analysis. Shared report links are the only way others can see your data, and you control when to create them. You can delete your account and all associated data at any time from Settings.