Mission
Make product risk visible and actionable - so growing software companies can release with confidence without gambling with customer trust.
About Mithril Guard
Mithril Guard was created to help software teams replace release guesswork with a controlled, explainable quality system - one where every testing decision can be traced back to a business risk.
Mission
Make product risk visible and actionable - so growing software companies can release with confidence without gambling with customer trust.
Vision
A world where QA is measured by better decisions and protected business value, not by the number of test cases written.
Why Mithril Guard exists
Traditional QA counts tests and green dashboards. Mithril Guard focuses on what could break, what it would cost, and what to protect first.
More tests do not automatically create more confidence.
Quality means asking hard questions and standing behind release decisions.
Technical work should translate into decisions a business can understand.
Personal story
QA Automation Consultant · The person behind Mithril Guard
My route into quality engineering did not begin with code. It began with customers, responsibility and learning how to understand the real problem before offering a solution.
Childhood
My grandfather taught me to work from an early age. I started by helping him with the simple things and eventually found myself selling cabbages and produce beside him. Without calling it sales, he was slowly teaching me how business actually works: earn trust, do the work properly and treat every customer with respect.
First sales lessons
One lesson stayed with me more than anything else: listen to people before trying to sell them something. Understand what they actually need, solve that problem and don't push what doesn't help. His logic was simple - if people know you're trying to get their job done, they'll come back to you.
Handy Tel & Auto Plus
Handy Tel introduced me to professional sales, contracts, financing, institutions and the responsibility that comes with handling a customer's real problem. Auto Plus took that further - working across multiple teams, suppliers and departments to get the right outcome for the client. I learned that good service rarely ends with 'my part is done'.
The transition
Moving into IT meant starting again from the bottom. New tools, new language and problems I couldn't solve with experience from my previous career. It was difficult by design and taught me to keep learning, question my assumptions and stay with a problem until I genuinely understand it.
App Streams
At App Streams I was fortunate to learn from great mentors and colleagues while working across real products, teams and industries. Step by step, I learned not only how to test software, automate flows and work with APIs and CI, but how to recognise where products become fragile, ask better questions and think beyond whether a test simply passes or fails.
Today
Mithril Guard brings those threads together: customer understanding, technical quality and clear responsibility for business risk.
Where to next
See the evidence behind the words, or start with a conversation.