Built on Bugs, Driven by Solutions
Back in early 2018, three developers met at a tech meetup in Bangkok. We'd all spent years fixing other people's code — not because we wanted to, but because software breaks. And when it breaks in production, someone needs to understand why.
We started ignite-glowra because we kept seeing the same pattern. Teams rush features out, skip proper testing, then scramble when users report issues. We wanted to be the team that catches problems before they become disasters.
Seven years later, we're still doing exactly that. Our office in Lampang might not be flashy, but we've worked with over 200 projects across Thailand. Some were small startups, others were established businesses who needed fresh eyes on legacy systems.
What Actually Matters to Us
These aren't wall posters. They're decisions we make every day when we're knee-deep in someone's codebase at 3 PM on a Thursday.
Curiosity Over Assumptions
We don't assume we know why something broke. We dig until we find the actual cause. Sometimes it's obvious, sometimes it takes three days of testing edge cases. Both scenarios happen regularly.
Clear Communication
Technical jargon helps nobody. When we find issues, we explain them in plain terms. If your marketing team needs to understand the bug report, they should be able to read it without a CS degree.
Realistic Timelines
Testing takes time. We've never promised overnight miracles, and we won't start now. If thorough testing needs two weeks, that's what we quote. Rushing just means we'll miss things.
Documentation Matters
Every test we run gets documented. Not because we love paperwork, but because six months from now when a similar issue appears, having records saves everyone hours of confusion.
Team Collaboration
We work alongside your developers, not against them. Finding bugs isn't about pointing fingers. It's about making the product better before customers see the problems.
Continuous Learning
Technology changes constantly. We spend time each month learning new testing frameworks and debugging techniques. Not because it's trendy, but because it helps us catch issues we might have missed with older methods.
How We Got Here
A few milestones that shaped how we work today
2018
Started with three people and a shared workspace. First client was an e-commerce platform that kept crashing during checkout. Took us two weeks to find all the issues.
2020
Expanded to a team of eight. Moved to a proper office in Lampang. Started working with clients across different Thai cities who needed remote testing support during the pandemic shift.
2023
Introduced automated testing workflows. Helped us catch repetitive issues faster while spending more time on complex debugging scenarios that actually need human attention.
2025
Now a team of twelve. Still based in Lampang, still focused on thorough testing. Working with both startups and established companies who value quality over quick releases.
Our Testing Process
We don't follow a rigid checklist. Every project has different weak points. What we do follow is a structured approach that adapts based on what we find.
Most of our work happens in cycles. We test, document issues, discuss with your team, then test again after fixes. This back-and-forth continues until the software behaves as expected under various conditions.
-
Initial Assessment We start by understanding what the software should do. Sounds basic, but misaligned expectations cause most testing failures.
-
Systematic Testing Manual testing for user flows, automated tests for repetitive checks. We use both because they catch different types of problems.
-
Issue Documentation Every bug gets logged with steps to reproduce it. Developers shouldn't have to guess what went wrong or how to trigger the issue.
-
Regression Verification After fixes, we retest everything. Sometimes fixing one issue creates new problems elsewhere. We check for that.