No products in the cart.
NEW Your WinOLS Lua bot, ready to install
Your file service, on autopilot.
MyTuningBot is the WinOLS Lua bot that turns your tuning shop into a 24/7 automatic file service. It reads incoming files straight from your portal, matches them against your own .ols database, applies the right solutions and ships the tuned file back to the customer typically inside 60s.
Runs on your PCYour own database60-second turnaround24/7, no nights offUnlimited files included
mytuningbot · winols lua bridgeLIVE
[14:02:08] ▶ bot online · waiting for tickets…
[14:02:14] new ticket #41827 · VW Golf 2.0 TDI · CFGB
[14:02:14] → requested: Stage 1 + DPF off + EGR off
[14:02:15] → decrypting source .mmf via MMS API · ok
[14:02:15] → matching against your tuned database
[14:02:16] ✓ match · version selected from 412 candidates
[14:02:17] → applying patch · 1,184 difference bytes
[14:02:18] → checksum: repaired (Bosch EDC17)
[14:02:18] → re-encrypting tuned .mmf via MMS API · ok
[14:02:19] → export: tuned_41827.mmf (1,048,576 B)
[14:02:19] ✓ delivered to portal · ticket closed · 11s total
[14:02:23] push notification sent to customer
[14:02:31] new ticket #41828 · waiting
60sAvg. file turnaround
24/7No coffee breaks
∞Unlimited files
€249Flat monthly · all-in
How the automatic fileservice bot works
From upload to delivery in five steps.
MyTuningBot lives on the same PC as your WinOLS installation. A thin local relay listens for tickets from your portal, dispatches them to a Lua script inside WinOLS, and pushes the tuned file straight back. The portal API does the talking. WinOLS does the tuning. You do nothing.
1
Customer uploads
A .bin / .ori / .mod / .zip / .rar lands in your tuning portal with the tuning options the customer picked.
// portal2
Bot claims the ticket
The relay polls the ticket-server, locks the file (so two bots can't grab it twice) and pushes the request into WinOLS.
// relay3
BOT matches your DB
BOT reads your .ols database, runs case-insensitive keyword + exclude rules, finds the right version.
// winols lua4
Patch + checksum
The difference bytes from the matched version are applied to the customer's original, and the ECU checksum is recalculated.
// winols5
Delivered
Tuned file uploaded back to the portal, customer notified by email + push, credits/invoice settled automatically.
// portal01 · SPEED
60-second average
Most tickets close in under a minute: file in, file out, customer notified. Complex multi-option requests rarely cross the two-minute mark.
02 · SAFETY
Your DB never leaves your PC
The .ols database stays on your machine. The bot only sends the tuned customer file back to the portal. Never your maps, never your IP.
03 · SAFETY NET
Falls back to humans
If no version matches the request (unusual combo, missing keyword), the bot quietly hands it to your manual queue. Customer never sees an error.
Tunings out of the box
Anything you can name in WinOLS, the bot can ship.
MyTuningBot doesn't decide what's a Stage 1 or a DPF off. You do, in your .ols database. The bot matches whatever you've labelled (free-form: STAGE1, Stage 1, Stage1 Vmax, DPF EGR…) and ships it. Out of the box it handles the full menu most shops sell:
Stage 1
Performance map matched by Stage1 keyword, excluding combo versions.
Stage 2 / Stage 3
Same matching pattern, separate Lua rules for hardware-required stages.
// hardware tunesDPF off
Diesel particulate filter removal. Works standalone or combined with EGR.
// dieselEGR off
EGR delete with optional hysteresis ("EGR ISTERESI") and DTC mask.
// dieselAdBlue / SCR off
SCR shutdown for compatible ECUs. DCU and main-controller variants.
// dieselDTC removal
Code-by-code removal (e.g. P0476, P04XX) or full DTC mask.
VMAX off
Top-speed limiter delete, matched separately so it can be combined.
// petrol / dieselPop & Bang
Crackle / decel map matched against your custom version label.
// petrolHardcut limiter
Rev-limit hardcut with selectable RPM, exposed as a tuning option.
// petrolLaunch control
2-step launch with configurable RPM, matched to your stored map.
// petrolLambda off
O2 sensor removal. Pairs with cat-off or pure performance maps.
// petrolKAT / cat off
Catalytic-converter-off mapping for race / off-road builds.
// petrolTVA / Flaps
Intake-flap and TVA disable, matched by your free-form version name.
// petrolTorque unlock
OEM torque-limit removal for performance and tow setups.
// performanceClear / virgin
Wipe-to-stock matched against your CLEAR versions for rollback tickets.
Any combo
UNION of keywords across the ticket's main + options. "DPF + EGR" needs both substrings in the same version.
// combos Under the hood
Built like infrastructure, not a macro.
MyTuningBot isn't a recorded keystroke macro that breaks the first time WinOLS pops a dialog. It's a proper bot: a Lua script inside WinOLS, a signed local relay, and a queue-aware ticket server. Here's the surface map.
01
WinOLS Lua engine
The bot runs as a Lua script inside WinOLS itself. No screen-scraping, no fragile UI automation. It uses the official Lua API to load projects, query versions and export tuned files.
02
Your own .ols database
Point the bot at DB_QT25_VW.ols, DB_QT25_BMW.ols: your own tuning files. The bot iterates versions and matches against the ticket request. Your maps stay on your PC.
03
Smart version matching
Case-insensitive keyword AND exclude rules. Stage 1 matches STAGE1, Stage 1 and Stage1 … but skips Stage1 Vmax unless Vmax was also requested. No prefix-only matching nonsense.
04
MMS decrypt · checksum · re-encrypt
Customer uploads a protected .mmf? The bot decrypts it natively via the MMS API, applies the tune, repairs the checksum (EDC15/16/17, MED9/17, SID807, SIMOS, MEVD17, Magneti Marelli, Delphi, Denso) and re-encrypts it automatically before sending it back. Your customer gets a flashable file in the same format they uploaded.
05
Signed ticket relay
HMAC-SHA256 signed requests between portal ↔ relay, 5-minute replay window. The bot's PC initiates the connection: no inbound ports, no firewall holes, no exposed services.
06
Per-bot tuning map JSON
The matching rules live in tuning_map.json: keywords and excludes per tuning option, editable in any text editor. Tweak how a new tuning option matches without touching code.
07
Multi-bot orchestration
Run one bot per WinOLS PC: diesel team, petrol team, agriculture team. Routing rules on the ticket-server send the right files to the right bot. Each one shows a live heartbeat.
08
Failover & retry
WinOLS hiccup? Lost connection? The ticket isn't lost. The relay retries with backoff, and if the bot stays down past your SLA, the ticket gracefully reroutes to the manual queue.
09
Push, email & Pushover
Every state change (new ticket, bot tuning, delivered, fallback) fires a notification through your portal. Pushover for instant phone alerts. Email for customers. Audit log for everything.
10
Auto credits & invoicing
The portal deducts the customer's credits, charges their card or sends them an invoice the moment the file ships. The bot stays focused on tuning. Money is the portal's job.
11
Live admin dashboard
See every bot, every queue, every in-flight file. Median turnaround, hit rate, fallback rate, per-bot uptime, last 24 h heartbeats. Built into the MyTuningPortal admin.
12
Dry-run / staging mode
Test new tuning rules against past tickets before sending to live customers. The bot replays archived tickets in WinOLS, shows you which version it would have picked, no actual delivery.
Admin panel
Everything from the admin panel.
Configure each tuning, point it at the versions in your database, save. The bot picks up the rules instantly. No code, no config files.
MyTuningBot Admin · Tuning Map Editor// Tunings
Tunings
Stage 1
core mapperformance+ vmax+ add
3 matching versions found in your database
Honest comparison
MyTuningBot vs doing it by hand.
A skilled tuner can do everything the bot does. Just slower, only during office hours, and one ticket at a time. Here's how it compares.
| Manual tuner | MyTuningBot | Generic macro recorder | |
|---|---|---|---|
| Average file turnaround | 15 – 120 minutes | ~60 seconds | 3 – 5 minutes |
| Available 24 / 7 | ✕ | ✓ | requires PC unlocked |
| Uses your own .ols database | ✓ | ✓ | ✕ |
| Keyword + exclude matching (combo-aware) | by hand | automatic | prefix only |
| Graceful fallback to humans | n/a | ✓ | breaks & stops |
| Parallel files at once | 1 | unlimited (multi-bot) | 1 |
| Survives WinOLS dialog popups | n/a | ✓ | ✕ |
| HMAC-signed portal ↔ bot link | n/a | ✓ | ✕ |
| Push / email / Pushover alerts | manual | ✓ | ✕ |
| Auto credit deduction + invoicing | manual | ✓ | ✕ |
| Cost | 1 full-time tuner | €249 / month · unlimited | €20 + your time fixing it |
Pricing
One bot. One fair price.
No tiers. No ticket caps. No surprise overages.
€249 per month, everything included: unlimited files, multi-bot orchestration, all features, all updates, all support. The same price whether you ship 50 files this month or 5,000.
UNLIMITED FILES · FLAT MONTHLY · NO FINE PRINT
MYTUNINGBOT · MONTHLY
The complete automatic file service
€249/ month · Unlimited files. Forever.
- Unlimited tickets / month ship 50 or 50,000, same price
- Multi-bot orchestration unlimited bot instances
- All tuning rules Stage 1/2/3, DPF, EGR, AdBlue, DTC, VMAX, pop & bang, hardcut, launch, lambda, KAT, TVA, torque unlock, clear
- Custom mapping rules edit how the bot matches your maps
- Graceful fallback to your manual queue, never a lost file
- Live admin dashboard with per-bot metrics + hit rate
- Push, email and Pushover notifications
- Multi-currency auto-invoicing in your portal
- Dry-run / staging mode for testing new rules safely
- White-label customer notifications
- Priority WhatsApp + email support
- All future updates included for life
- Cancel anytime no contract, no setup fee
Common questions
Asked & answered.
Is it really unlimited files for €249?
Yes, really unlimited. Ship 50 files this month or 5,000, the price stays €249. Heavy users who hit 10,000+ files a month sometimes graduate to a dedicated-relay setup (still flat-price, just on its own infrastructure so you don't share the queue), but that conversation is rare and friendly. There is no usage-based billing and no overage fee.
Do I need WinOLS to run MyTuningBot?
Yes. MyTuningBot is a WinOLS bot. It runs as a software WinOLS installation and uses the official WinOLS Lua API to load projects, query your tuning versions and export tuned files. You need a licensed WinOLS on a Windows PC that stays online while the bot is working. If you don't have WinOLS, talk to us first and we'll help you set it up.
Does my .ols database get uploaded to your servers?
No. Your .ols database, your intellectual property, stays on your PC. The bot only sends the tuned customer file back to your portal. Your maps, your years of work, your competitive edge never leave the machine. The portal ↔ relay link is HMAC-SHA256 signed and only carries customer files in both directions.
What if a customer requests a tuning I don't have in my database?
The bot falls back gracefully. If the keyword + exclude rules don't find a matching version in your .ols database, the ticket is automatically rerouted to your manual queue, exactly as if a customer had submitted a manual-only request. The customer sees "engineer is on it" instead of an error. No lost files, no awkward emails.
How does the bot pick the right version when version names are inconsistent?
This is the part most macro-recorder bots get wrong. Tuners label versions however they want: STAGE1, Stage 1, Stage1 Vmax, Stage1 DPF EGR. From your admin panel you point each tuning option at the right family of versions and tell it which to skip, then the bot does the rest. For combo requests (e.g. Stage 1 + DPF off) the bot combines the rules across every option in the ticket so the cleanest matching version is always picked. No code, no config files, everything from the dashboard.
What happens if WinOLS crashes or my PC reboots?
The ticket isn't lost. The relay retries with exponential backoff. If the bot stays offline past your configured SLA (default: 5 minutes), the ticket gracefully reroutes to your manual queue and the customer gets the same "engineer is on it" message. When WinOLS comes back, the bot resumes the queue automatically.
How long does setup take?
About 2 hours, done together over WhatsApp screen-share. We install the software on your computer, configure the relay, hook it to your portal, import a starter tuning_map.json, run the first dry-run against archive tickets to make sure matches look sane, and switch it live. You start shipping automated files the same day. There is no setup fee.
Can I cancel any time?
Yes. No contract, no minimum term, no cancellation fee. Cancel from the admin panel or by email. The bot keeps running until the end of your current billing period, then we shut it down cleanly. Your .ols database was always on your PC anyway, so there's nothing to "get back".
Ready to stop typing?
Let the bot do the keystrokes.
No slide deck. €249/month, unlimited files, cancel anytime.