What is my private file database for?

The Database section holds your own ECU (engine control unit) reads and WinOLS projects, uploaded so the platform recognises them. When one of your dealers uploads an original read, the analyser compares it against the shared file library and against yours, and prefers a match from your own database over an equally good shared one. The effect is a better vehicle and ECU match on the order form, for your dealers only.

The files are yours alone. They are isolated from the shared library and from every other tuner's database — nobody else's dealers ever match against them, and you never match against theirs.

The private file database is a paid capability. On plans that do not include it, the section is locked and the lock names the tier that carries it.

Is this the same as Workspace → Files?

No, and the navigation is genuinely confusing here: both entries are labelled Files. They are different pages for different jobs.

• Database → Files (this page, titled Database) — ECU reads and WinOLS projects that feed file matching. Never shown to anyone.
• Workspace → Files — customer-facing PDFs such as your terms, shared by link. See sharing-documents.

Nothing you upload to the Database is published, linked or sent to a dealer.

How do I add files?

The Upload tab takes single files or whole archives. Drag and drop onto the dashed area, or use Browse files or Browse folder. Supported extensions are .ols, .bin, .bak, .frf, .kp and .zip archives — a zip is unpacked for you, so uploading a folder of projects as one archive is the fast path.

Uploading and processing are two steps, and the Processing card shows both: Sources uploaded counts your files arriving, Items processed counts them being read and fingerprinted afterwards. Individual items end as Done, Skipped (already in your database — re-uploading the same read is harmless) or Failed. Retry failed re-runs only the failures.

Uploading the same file twice never creates a duplicate: an item is matched on the content of the read, within your database.

How do I see what is in there?

The Library tab lists everything that has been ingested. Search across ECU number, software and hardware numbers, part numbers, VIN (vehicle identification number) and your own labels, and narrow with the Family, Vehicle, ECU type and Status filters — each filter carries its own counts, and active filters show as chips you can clear individually or with Clear all.

Each row shows the file, its family, the vehicle, its status and when it was added. Open a row to add a Label ("Golf 7 GTI Stage 1") and a Comment, or to delete the file. A label is worth the ten seconds: it is searchable, and it is what makes a row recognisable a year later.

Until you have uploaded anything, the Library says so and points you at the Upload tab.

What should I upload?

Original reads you already have, and the projects behind them — the more of your own real work the database holds, the more often a dealer's upload is recognised straight away instead of being identified by hand. There is no benefit to uploading files you did not produce or read yourself: matching quality comes from coverage of the vehicles you actually work on.

If a file will not process

A Failed item usually means the bytes are not a read the analyser can parse — a partial download, a tool-encrypted container, or a project file saved in a format not in the supported list. Press Retry failed once in case the failure was transient. If the same file fails again, open a support ticket with the filename, its extension and the tool that produced it, and attach the file if you can share it.