SolutionsOne engine, every kind of table
Rules are
everywhere.
Wherever people play or practice together by written rules, the same loop applies: write the rules so a machine can check them, play without arguing, and learn from what happened. Here is what that means for four kinds of people.
For creatorsGame designers
Playtest the rules,
not the patience of friends.
“I want to test my mechanic tonight, not after the next print run.”
Designers of card, board and party games spend weeks reprinting prototypes and waiting for a full table to find out a combo is broken.
- Studio create
Paste the rulebook. Studio drafts Rulespec and lists every unclear sentence.
- Table play
Send a link. Fill empty seats with ghost seats that play by the same rules.
- Replay understand
Run thousands of seeded games and fix what the Lab finds before the next print.
What you get: A playable version of your game you can share by link, and thousands of playtests before the first print.
- Card games
- Board games
- Party games
- Prototypes
Live experiencesHosts & organizers
The host runs the show.
MEKYRA runs the rules.
“I want a room full of people hooked for two hours, without a spreadsheet and a tired host.”
Mystery nights, escape rooms, quiz shows and festival games need hidden information, timing and fair reveals: more moving parts than one person can track while also being a great host.
- Studio create
Write phases, roles and reveals as rules, with a host script beside them.
- Table play
Phones are the hands; one screen is the stage. Nobody sees what they shouldn’t.
- Replay understand
After the night, see where groups stalled and which clues landed.
What you get: A night that runs itself: a private role on every phone, a stage screen for the room, and reveals that land fairly and on time.
- Detective nights
- Escape rooms
- Quiz shows
- Multiplayer events
Worlds & campaignsGame masters
A canon
that remembers.
“I want my world, my characters and my house rules to stay straight for months.”
Long campaigns lose track of what was established. Contradictions creep in between sessions, and nobody wants to be the one keeping notes.
- Studio create
Campaign rules, house rules and characters in one place, with sources.
- Table play
Dice stay on the table. MEKYRA records what became canon and who confirmed it.
- Replay understand
Every fact has a session and a timestamp. Amendments are visible, never silent.
What you get: A campaign that remembers: canon with sources, rules that stay consistent, a world that persists between sessions.
- RPG campaigns
- Persistent worlds
- House rules
- Play-by-post
Training & simulationsL&D, safety and ops teams
Your playbook,
as a drill.
“I want realistic practice that runs the same way for every group, and a debrief people actually use.”
Tabletop exercises and classroom scenarios work, but they are slow to write, hard to run the same way twice and their lessons end up in a slide nobody opens.
- Studio create
Studio drafts roles, resources and injects from your playbook; a facilitator reviews them.
- Table play
Teams decide together while the facilitator steers the scenario from one console.
- Replay understand
An after-action report and improvement plan, written from the log, about the process and never a person.
What you get: A drill built from your playbook, with roles, injects and an after-action report written from the log.
- Tabletop exercises
- Team challenges
- Classroom scenarios
- Corporate simulations
Your tableNot on the list?
Bring your rules. We’ll run them.
If people follow it together, turn by turn, it can probably run on MEKYRA. Tell us what you’re building.