GuildEngine

Multiplayer software building

Perfection
is a team.

One Game Master sets the direction. The engine breaks it into assets. Every expert plays their class through their own AI agent — all at the same time, on the same living product.

No tickets. No queue. No waiting for review.

Claim your seat See how a raid runs
  • Bring your own agent
  • Claude Code
  • Codex
  • OpenCode
  • Pi
Raid log — project: tavern-pos illustration
GM
Game Master
Ar
Architect
De
Designer
Dv
Developer
Op
DevOps
    live — everyone sees finished work the moment it lands
    ◆

    The quest chain

    How a raid runs

    Five steps. They all happen at once, forever, until the product is right.

    1. I

      The Game Master one-shots the direction

      Describe the product to your agent. Out comes a first mockup: every page, rough but working. That's the direction — not the finished thing.

    2. II

      The engine turns it into assets

      A page. A button. A database. A deployment. Everything in the project becomes an asset with four sides: look, behaviour, architecture, operations.

    3. III

      Assets drop into each class's bucket

      Every class sees only what's theirs: what's new, what changed, what needs attention. The designer gets every visible thing. DevOps gets where it all runs.

    4. IV

      Everyone improves their side — now

      You direct your agent on your side of each asset. Your work goes in straight away and shows up for the whole party. Nobody is blocked by anybody.

    5. V

      The GM approves without stopping the fight

      Finished work is already live. When the Game Master likes it, it becomes the official direction. If not, it goes back with a steer — and everything else carries on.

    Character creation

    Choose your class

    Builders own one side of every asset. Challengers own nothing and roam everywhere. One person can play several — or run the whole raid solo.

    Challenger alerts arrive after the first version; the builder classes and the Game Master are playable today in the guild hall.

    Try it

    Stay in your lane. Reach across politely.

    Every asset has four sides, each with one owning class. Pick a class, then try to change a side.

    Play as
    Asset · page

    Checkout

    "Pay in two taps."

    guild> Pick a side of the asset to change.

    Nobody waits

    Work inside your own side goes in immediately and syncs to everyone. The project moves at the speed of its fastest player, not its slowest review.

    Nothing collides

    Reach into someone else's side and your change becomes a suggestion. The owner previews it, then takes it or leaves it.

    Nothing is lost

    When the direction changes, new assets appear and changed ones are flagged — work people already improved is never wiped.

    Coming to the realm

    Looking for group

    A board where projects find the class they're missing and experts find a raid worth joining. This is what it will look like.

    LFMClinic booking appneeds Architect, Security3 / 5
    LFMIndie game storefrontneeds Designer4 / 5
    LFGDevOps, 9 yrs, loves boring deploysseeks a Game Master with a plansolo
    LFMTavern point-of-saleneeds QA Tester5 / 6

    Example listings. The board opens after the first guilds have run.

    The summoning stone

    Claim your seat

    GuildEngine is in its first playable version. Leave your name at the stone and you'll be called when seats open.

    Already have a founder key? Enter the guild hall →