01 / PCR
Run the community.
Real players, real staff, real workflows, real edge cases. The kind of environment where “simple” features learn humility.
Meet the Creator
Hi, I’m Katie.
I built EmberForge after spending years on the other side of community tools: running the community, solving the problems, and discovering exactly how quickly “this should be simple” can become an entire evening.
Where it started
Before EmberForge, there was PCR.
Phoenix Clan Rising is where the problems showed up first. EmberForge is where I started turning those problems into tools.
EmberForge did not begin as a software company. It started inside Phoenix Clan Rising, the gaming community I was already running.
Like most community owners, I kept running into little problems that existing tools either did not solve, solved awkwardly, or wanted me to reshape my whole workflow around.
So I started creating bots for myself.
At first they were practical tools for PCR: moderation, economy features, community systems, staff coordination, automation, and the odd little jobs that appear when a community grows enough moving parts.
“Wait... could I just build this?”
That question kept coming back. One bot became another. Individual tools started becoming systems. Systems started becoming something I could refine, reuse, and make better.
Eventually, one of those projects became Ember Vault. That was the moment the idea started stretching beyond my own community.
I realized the tools I was building because I needed them might be useful to other community owners too.
The path here
A community became a workshop.
02 / BUILD
Make what was missing.
Bots started as internal tools built for the things PCR actually needed, not hypothetical feature lists.
03 / EMBERFORGE
Build beyond one community.
EmberForge became the place to turn those lessons into tools that other communities can shape around themselves.
How I build
Founder fingerprints, not founder wallpaper.
EmberForge carries my curiosity, practicality, community experience, and occasional refusal to accept that a clumsy workflow is “just how it works.” But the goal is to build products that can grow well beyond one person.
Start with the person doing the work.
Community owners, moderators, admins, event teams, and staff are usually juggling more than the software realizes. The tool should respect that.
Build from reality.
If a feature looks perfect on paper but becomes annoying in daily use, reality wins. We change the feature.
Keep it human.
Software can be professional without sounding like it was assembled by a committee inside a spreadsheet.
Leave room to grow.
Today's useful tool should not become tomorrow's trap. EmberForge is built to be refined as the problems get bigger.
What comes next
Still building.
Ember Vault is the first public EmberForge product, not the finish line. The Forge exists for the next useful thing somebody wishes worked better.