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.

Built by people who actually have to run communities.
Built in the Forge Useful tools.
Human decisions.

Built, tested, refined, and occasionally argued with. Ember Vault is operational on dedicated EmberForge infrastructure, Nexus ARK has its foundation and architecture locked, and EmberForge HQ is officially open for humans.

Workshop status: actively building
Built in the Forge

The workshop got bigger.

Every EmberForge product starts with a real problem and shares the same foundation: practical design, community experience, room to grow, and zero interest in making setup somebody's second job. The tools stay in the same family without becoming clones of each other.

EmberForge Product 01

Ember Vault

Operational · active development · beta preparation

A configurable Discord economy platform with guild-isolated wallets, transactions, shops, reward categories, vouchers, role income, delegated management, and per-server settings. Now running independently with monitored services, automatic recovery, and restore-tested application backups.

Multi-tenant Guild-isolated Permission-safe Configurable Restore-tested
Ember Vault Independent runtime
Community wallet 12,345 Credits
EmberForge Product 02

Ember Nexus

Nexus ARK foundation & architecture locked · pre-production

The connection layer around game communities. Nexus starts with ARK cross-chat between servers and Discord, then expands through monitoring, automation, safe RCON controls, and community insights.

ARK-first Cross-chat Discord Agent + RCON
ARK A
ARK B
ARK C
Agent
Discord
Dashboard
EMBER
NEXUS
How we build

Useful before impressive.

EmberForge builds from lived community problems rather than abstract feature lists. The goal is not to collect products. It is to make tools worth keeping around.

01 / PRACTICAL FIRST

Make it earn its place.

Every feature should solve something real. “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 are building the machinery too.

EmberForge now runs on dedicated application infrastructure with isolated service identities, local and external monitoring, automatic recovery for critical services, restore-tested application backups, and authenticated self-hosted business mail. The public Discord is where announcements, changelogs, support, feedback, and future beta testing live.

Join EmberForge HQ