Why FireworkOS Was Built
FireworkOS did not start with the question, “What software can we sell to fireworks companies?” It started with a much more frustrating question: Why are we still doing this like this?
Founder Story · 4 min read · Updated August 2026
After 27 years around professional fireworks operations, the same problems kept showing up in different companies. Different logo. Different crews. Different magazines. Same operational mess.
Inventory in spreadsheets. Magazine logs on paper. Crew documents in folders. Bills of Lading recreated for every show. Show information moving through text messages. Returned product waiting for somebody to figure out what it was and where it belonged. None of those systems were completely broken. That was actually the problem. They worked just enough to survive.
The industry adapted general tools to a very specific workflow
Professional fireworks is a strange business operationally. Product arrives in cases but gets consumed by unit. A case can leave full and come back partial. Inventory can be physically on the property but already committed to another show.
Material leaves a magazine, travels under hazardous-material transportation requirements, goes to a temporary show site and sometimes comes back the same night. Crew roles and qualifications matter. Documents expire. The office needs one set of information, the truck another, the lead something different again.
Generic warehouse software, scheduling software and shared drives were never built for that.
Workarounds become invisible when you live with them long enough
Ask why the company prints a spreadsheet, writes on it, photographs it, emails the photo and then types changes back into another spreadsheet. The answer is usually, “That is how we have always done it.”
FireworkOS exists because that answer is not good enough. The goal was not to digitize each piece of paper individually. That would just create digital paper. The goal was to connect the workflow so information only has to be captured once whenever possible.
The show became the center
A display company does not really run on inventory. It runs on shows. Inventory supports the show. Crew supports the show. Transportation supports the show. Documents support the show. Returns happen because of the show. Reconciliation closes the show.
Once you think of the operation that way, the architecture becomes clearer: the show is the thread connecting the modules.
The magazine needed its own clean job
Magazine is for ATF magazine and log recordkeeping. That is serious enough on its own. Crew assignments, training and employee documents do not belong there. Those records belong with the people they describe.
Clear boundaries make the system easier to use and easier to trust.
Mobile had to be first-class
A fireworks operation does not live at a desk. It lives at the magazine door, truck, show site and midnight return. A system that only works well on a 27-inch monitor is not an operations system.
FireworkOS is designed around phone and tablet workflows as well as office use. The person doing the work should be able to record the work where it happens.
The best feature is not having to remember
The biggest operational risk in a paper-and-spreadsheet company is institutional memory. One person knows where the BOLs are. One knows which partial case is open. One remembers which driver credential is expiring. One remembers why inventory was adjusted.
FireworkOS is built so the answer belongs to the company instead of one employee’s memory. Everything you need should be where it should be.
This is still the standard
FireworkOS is not trying to make professional fireworks simple. The work is complicated because the work is complicated. The goal is to stop making it harder with disconnected administration.
The finale should be chaotic. Your operation shouldn’t be.
Firework OS supports operational recordkeeping and documentation. It does not guarantee compliance or provide legal advice. Your company remains responsible for meeting applicable ATF, DOT, state, and local requirements.
Review the feature detail, compare packages, or book a demo to walk through the workflow with your operation.