Two billing models, one result
In both cases the same file with a descriptive name ends up in the folder. The difference lies before that. With the BYOK model you open an account with the AI provider, generate a key, enter it in the tool and are then billed for the analysis by the model provider — usage-based, often down to fractions of a cent. With the included model you pay a fixed monthly amount with a document allowance and have no dealings with the model provider at all. Both are legitimate; which one is cheaper depends purely on your volume.
What speaks for your own keys
At high volume, BYOK is hard to beat. You pay what you consume, without a reseller margin, and benefit immediately when model prices fall. On top of that comes a point that often weighs more in companies than price: you hold your own contract with the AI provider, including your own data processing agreement and your own choice of model. If your IT department already holds such a contract, using it rather than adding another vendor to the chain is the obvious move.
What speaks against your own keys
BYOK shifts effort onto you. Someone has to create the provider account, add a payment method, generate the key, store it securely and rotate it regularly. If the key expires or the balance runs out, renaming stops and at first nobody knows why. Monthly cost is also unpredictable, which is awkward in organisations with budget approvals. For individuals and small offices without an IT owner, this is often the point at which the theoretically cheaper model becomes the more expensive one in practice.
Filery covers both routes
The Starter plan covers 50 documents per month, free and without signup — the analysis is included and you need no key of your own. Business costs 30 € per month with 500 documents, again with the analysis included. If you prefer to use your own provider contract, Custom costs 5 € per month and takes your own API keys; the analysis cost is then settled directly with the model provider. The plan changes nothing about the sequence: the PDF is read on your machine, the extracted content goes encrypted into the AI analysis, the recognised metadata comes back, and the renaming happens again on your device — the files themselves are not stored permanently. That turns the decision from a one-way choice into a plan choice you can revisit whenever your volume changes.
Naming pattern, preview and history in daily use
Whatever the plan, the work looks like this: you define the naming pattern, for example Date_Sender_Type, and set the date format. Filery reads the PDFs in a folder, recognises sender, document date, document type and subject, and shows the suggestion next to the old name — per file or for the whole folder. You confirm, correct or skip. Renamed files then appear in the app's history. For scans without a text layer, OCR can be switched on; that costs time per file and depends on scan quality.
When NameQuick is the better choice
If you process considerably more than a few hundred documents a month and run a provider account anyway, a pure BYOK tool has the cost advantage — an included allowance then does not pay off. The same holds if you need to cover file types beyond PDF, or if a one-time licence fits your procurement process better than a subscription. In those cases our model simply is not the right one, and no amount of preview changes that.
FAQ
Related topics
Download Now
Choose your platform and start with automatic document renaming
Windows
Windows 10 & 11
We are currently working on official code signing for Windows. The download is already available – Windows Defender or SmartScreen may show a warning because the app is not yet certified. Choose “More info” → “Run anyway” to install.
System requirements: macOS 10.14+, Windows 10/11
All downloads are transmitted securely via HTTPS.