Your data doesn't become our dataset.
Brutus is built to validate the file you provide during an active session, return the result, and avoid turning uploaded file content into a permanent data collection.
Keep the validation explicit. Keep the data lifecycle short.
Brutus does not need to learn from your file to validate it. The rules you choose determine what passes and what fails.
In-session processing
Uploaded file content is handled as part of the active Brutus session rather than being kept as a permanent uploaded dataset.
30-minute session lifetime
Brutus sessions are intentionally short-lived and configured with a 30-minute lifetime.
Rule-based, not AI-based
The validation result comes from explicit rules selected by the user. Brutus does not require an AI model to decide whether a value is valid.
Microsoft Entra ID authentication
User authentication is handled through Microsoft Entra ID rather than a custom password system built into Brutus.
Separate account functionality from uploaded data.
Brutus uses application infrastructure for account and product functionality, including PostgreSQL and Redis-backed sessions. That is different from building a permanent repository of the spreadsheets and CSV files users upload for validation.
Reusable validation templates store the validation configuration needed to apply rules again. They are not a copy of the uploaded dataset.
Brutus validates data. It isn't a place to archive it.
That boundary is intentional. For questions about a particular security, procurement, or data-handling requirement, contact IRONFEL before using Brutus for that workload.
Contact IRONFEL →