OneNote
The first campaign notes lived in a familiar place, but the world quickly outgrew loose pages and scattered tabs.
FableRealms Origin
About FableRealms
Built from grief, stories, and one very stubborn idea.
FableRealms began as a personal tool for running a homebrew campaign. It grew into a connected storytelling platform for DMs, players, worlds, sessions and campaign memory.
The Beginning
It started with family.
FableRealms did not start as a product. It started after the death of my older brother.
Like many families, grief made us realise how easy it is to drift, how quickly time passes, and how important it is to actually spend time together. Myself and my two brothers decided we needed to stop being useless at meeting up, so we started talking about playing Dungeons & Dragons.
I took on the role of Dungeon Master.
Almost immediately, I loved the storytelling - and almost immediately, I hated how disconnected everything felt.
Running a campaign meant bouncing between notes, maps, character sheets, subscriptions, random tools, chat apps, VTTs, files, bookmarks and whatever else was needed just to keep a story moving. The more I prepared, the more scattered the world became.
The First Campaign
From OneNote to The Story of Three.
The private tool grew one frustration at a time, each new need pulling the campaign closer to a connected realm.At first, I used OneNote to track my homebrew campaign, The Story of Three. That campaign became the spark.
I wanted a better way to write my world, so I built a simple note-taking app. Then I added Acts, Chapters and Pages, because it felt more natural to write a campaign like a living story.
Then came Characters, NPCs, Monsters, Locations, Factions, Quests, Lore, secrets, choices, outcomes, maps, table tools, player notes, campaign memory, and everything else that kept appearing every time I thought: "There has to be a better way to do this."
The Story of Three
The homebrew campaign became the spark: a family table, a living story, and a need for something more connected.
Acts, Chapters and Pages
Campaign writing started to feel better when it was shaped like a story instead of a pile of notes.
Characters, NPCs and Locations
People, places, lore, quests, secrets, outcomes and maps kept becoming part of the same growing world.
A Connected Realm
Eventually, I realised I was no longer building a note app. I was building a realm.
The Mission
From the first idea to the final roll.
About a year ago, that phrase became the goal: everything connected, everything in one place, and every part of the campaign able to speak to the next.From the first idea to the final roll.
If I found myself needing to leave FableRealms to do something important for my game, that thing went onto the feature list. If a DM needed it, if a player would benefit from it, or if it helped the story feel more alive, it became part of the vision.
That is why FableRealms now includes Tavern, StoryEngine, WorldBuilder, GuildHall, Table, Codex, The Chronicle and Oracle. Each part has its own purpose, but the real power is in the connection between them.
Tavern
StoryEngine
WorldBuilder
GuildHall
Table
Chronicle
Codex
Oracle supports the whole journey.
You can write a story in StoryEngine, prepare a scene in WorldBuilder, gather players in GuildHall, run the session in Table, record what happened in The Chronicle, and reveal the right knowledge to players through Codex.
The campaign does not end when the session ends. It remembers.
The Pivot
From personal tool to shared platform.
For a long time, FableRealms was just my own tool. It was built around how I wanted to run my own world, my own campaign, and my own table.
But over time it became obvious that the problem was not just mine. A lot of DMs are trying to run amazing stories while juggling too many disconnected tools.
So I made the decision to turn FableRealms into something other people could use. That was a bigger pivot than I expected.
Going from a personal app to something ready for real users meant rebuilding, polishing, securing, restructuring, designing onboarding, creating access flows, improving reliability, and turning a passion project into an actual platform.
The last six months have been focused heavily on making FableRealms ready for a userbase. It is now entering Season 1: a working, live version of the realm with many features already in place, and plenty still evolving.
The Platform
Built to grow.
I have over 20 years of experience across development, infrastructure, platform engineering and automation. FableRealms has been built from the ground up with that mindset.Under the surface, the platform is designed to be flexible, modular and scalable. Every major feature is treated like a connected module sitting on top of a shared core platform. That means FableRealms can grow quickly without needing to rebuild everything from scratch each time a new idea appears.
Modular Core
Features are built as connected modules.
Built to Scale
Designed with platform engineering principles.
Always Expanding
New ideas can become new tools quickly.
And there are always new ideas.
Eventually, I want FableRealms to become the go-to home for tabletop storytelling. I want to bring in more people, hire designers, build proper sound and music tools, expand the creative systems, improve accessibility, and one day work on FableRealms full time. That is the dream.
Community
No stupid ideas.
There are no stupid ideas.
Some of the best features come from a tiny frustration, a random comment, or a "wouldn't it be cool if..." moment.
So if you use FableRealms and think of something, please share it. It might be the next thing that DMs and players have been waiting for.
Pull up a chair. The realm is open.
FableRealms was born from loss, built through stories, and shaped by the simple idea that tabletop games should feel connected, memorable and alive.