EmberForge

Tools for communities that deserve better than “good enough.”

We build practical community software shaped by the problems we’ve actually had to solve ourselves. Useful first. Human always. Slightly unreasonable amounts of tinkering included.

Explore Ember Vault See what we're building
Built by people who actually have to run communities.
Built in the Forge Useful tools.
Human decisions.

Built, tested, refined, and occasionally argued with. Then improved again when reality finds a weird corner case.

Workshop status: behaving
Built in the Forge

Meet the first tool.

Every EmberForge product shares the same foundation, then develops a personality of its own. The shape language, interaction patterns, and design discipline stay in the family while each tool becomes something distinct.

EmberForge Product 01

Ember Vault

A configurable Discord economy platform for communities that want wallets, marketplaces, rewards, vouchers, role income, and administration without rebuilding the entire machine themselves.

Guild-isolated Configurable Community-first Built to grow
Explore Ember Vault Follow development
EVEmber Vault
All systems behaving
Community balance ✦ 12,450 Credits
Shop listings18 active
Reward rules5 configured
Role income3 running
Manager access2 members
How we build

Practical before impressive.

EmberForge projects start with the problem somebody is actually having. The shiny bits come later, after the thing works, makes sense, and does not require handing out Administrator because someone needed to edit a shop listing.

01 / USEFUL FIRST

Solve the actual problem.

Features earn their place by making community work easier, clearer, or less repetitive. “It looks cool” is not an architecture.

02 / COMMUNITY TESTED

Built from real use.

The workflows come from communities we actually operate, which means the weird edge cases tend to arrive before the marketing department invents them.

03 / MADE TO GROW

Start simple. Leave room.

A useful first version should not become tomorrow’s trap. We build systems that can be refined instead of replaced every time the project grows teeth.

Why EmberForge exists

Most projects start with one dangerous question.

We run into a problem while actually managing a community, discover the existing answer does not quite fit, and eventually somebody asks whether we could just build the thing ourselves.

Apparently the answer keeps being yes.

Behind the Forge

We show our work.

Development updates, things we refined, occasional known weirdness, and the decisions behind the tools. Some people only want the release notes. Some people desperately want to know why there is suddenly a composite database index. We respect both species.

See what changed