The design workbench for physical games
Loruna holds the compendium, the rules, the cards and the playtest log as a single source. Change an entry once — the card, the rulebook and the sell sheet are already correct.
Contract · Meridian
Deliver Silk for 8 Prestige.
Why it exists
The rules sit in a doc a few revisions behind the print-and-play. A card still lists what a good used to cost. A playtester quotes a rule nobody can find, and last Tuesday's fix never made it back into anything. The game is fine — its record fell out of sync with itself.
You write an entry once — a card, a rule, a house, a hazard. The rulebook, the promo sheet and every diagram are generated from that entry, not authored beside it. Change a number and it's correct everywhere, the moment you change it.
What's inside
Not six apps stitched together — one place where your game's facts live, and several views compiled from them.
Compendium
Every concept, port, house and rule gets a page — a tagline, an infobox, and cross-links to everything it touches. It reads like a wiki because that's what it is: the one place your game's facts actually live.
Rules Manager · Rulebook
Keep rules as individual, categorized entries instead of one wall of PDF text. The Rulebook view assembles them into chapters in the order you set — fix a rule and the compiled book is already right.
Component Studio · Deckbuilder
Design a component once, then let it pull its fields straight from the entry. Build and version decks against the same data, so a card's text and its stats are never two edits away from disagreeing.
Playtest Log · Findings
Log playtests against your own schema — phases, scores, whatever your game tracks — and raise findings against the exact rule or card in question, so nothing gets fixed from memory.
Timeline · Lineage
Chart your setting's chronology on a Timeline and its bloodlines and dynasties as Lineage diagrams — rendered from your entries and droppable into the Rulebook or Promo output as live embeds.
Wiki Health
A dashboard reads your whole compendium at a glance — coverage meters, entry counts, and how each category is filling in — so you catch the thin corners of your game before a playtest, not during one.
See it move
This is Silk Commission, a real contract from Meridian. Follow it from a wiki edit to a print-ready sell sheet — the same 8 Prestige the whole way.
Contract · Meridian
Deliver Silk for 8 Prestige.
Write the fact once. It's a wiki page — a tagline, a body, and an infobox of fields. No spreadsheet, no separate "card data" file to keep in step.
Silk Commission
Deliver Silk for Prestige.
Component Studio reads the card's layout straight from the entry's fields — Requires, Pays, Copies. The 8 is the same value; there's no second file where an old number can keep hiding.
Chapter IV
Fulfil a contract by delivering the required goods to any port on your routes, then discard it and score at once.
Silk Commission pays 8 Prestige for 5 Silk — one of twelve contracts in the deck, ranging from a single point to a crown's ransom.
The Rulebook view compiles every Contract entry into its chapter, in the order you've set. The 8 Prestige reads correctly here too — because it's the same value, not a retyped copy.
A trade epic for 2–4
Cross the Meridian before the Monsoon does.
The same entries, laid out as a Promo sheet — for a crowdfunding page, a convention demo, or the back of the box. Nothing here was retyped from anywhere.
How it thinks
Loruna documents and tracks your physical game. It doesn't simulate turns or enforce rules — that's still the table's job.
The Rulebook, Promo and diagrams are views of your data — never separate files that can quietly disagree.
Nothing to install. Open it at your desk, at the table, or mid-playtest, and start writing.
Sign in and your compendium follows you — across sessions and machines, without exporting a single file.
Bring your own game, or open Meridian and see the whole pipeline with real content already in place.
Open Loruna →
LORUNA