← Both open calls

The City of KinspireDM Tool Playtest

Founding testers - first beta

Break it before anyone else can

We're looking for game masters willing to run real games on an unfinished tool and tell us exactly what's wrong with it. Small group, direct line to the people building it, and genuine influence over where this goes.

Who we want
GMs at any level, first-timers to twenty-year veterans
Cost
Free
What you get
First beta access and founding-tester perks
What we want back
Honest feedback, including the harsh kind

What you're signing up for

You'd get hands-on access to the game master tool before it opens up, and you'd be running actual sessions with it rather than clicking through a demo. Expect rough edges, things that break mid-session, and features that change under you between builds.

In exchange: founding-tester status and perks, and a standing line to the people writing the thing. When testers tell us a design decision is wrong, that has changed our minds before, and we'd rather hear it early and bluntly than politely and too late.

Experience level genuinely doesn't filter anyone out. A GM running their fourth session ever catches things a twenty-year veteran has long since learned to work around.

Exactly what the AI does

This is the branch where the AI lives, so here is the whole of it. It reads what a player types, works out what they're trying to do, and decides which table or rule applies. That is the job. A parser sitting on top of a rules engine.

It does not generate art. It does not write your setting, your NPCs, or your prose. It runs during play and nowhere else, and it does not touch the bazaar, the marketplace, or anything social on the platform.

No artist's work goes into it without that artist's consent and a contract saying so, and every AI feature on Kinspire is optional to use. Those limits are set by working artists, which is the whole reason they sit where they do.

Our reach has edges and we'd rather name them: we can't undo what other companies trained on, and we don't control what third-party platforms do with anything posted to them. What we control is what we build and what we agree to.

Playtest application

Fields marked with a red dot are the ones we need. This one's shorter than it looks - most of it is contact details.

Who you are

Whatever you'd like us to call you. A handle on its own is fine.
If it's different from the name above, or if it's how you're known at a table.

How to reach you

Optional. Only used for build drop-offs and session scheduling, and only if you list one.
Discord, Matrix, wherever you actually read messages.
Best way to reach you •

Time at the table

How would you describe your experience as a GM? • Either measure counts - pick whichever fits you better. This shapes what we ask you to test, not whether you get in.
Systems, settings, and whether your tables are in person, online, or both.

Consent and what you're agreeing to

Plain language, no fine print. Each of these is a real commitment, so read them rather than clicking through.

Access needs, scheduling constraints, what you're hoping this tool will do for your table, or what you suspect it'll get wrong.

We read every application and reply to everyone, accepted or not.