CP-05Roadmap & titles

The publishing route, and everything we have announced

This page holds two things: the seven checkpoints a title passes through with us, and the titles that have actually reached them. Nothing appears in the second list before an agreement is signed and the studio has approved the announcement.

//catalogueTitles

No announced titles yet

Checkpoint Nomad opened for submissions in its first year of operation. We publish a title on this page once an agreement is signed and the studio has agreed to the announcement — not before. Nothing here is a placeholder for a game that does not exist.

Two rules make that promise checkable rather than decorative: a release date can only exist on a title marked released, and an age rating only appears once a rating board has issued one. Both are enforced in the code and in the database, not left to whoever writes the copy.

Submit your demo and you could be the first entry on this page.

//routeSeven checkpoints

What happens between your submission and a live storefront

No timelines are promised here, because platform certification queues are not ours to schedule. What is promised is the order of events and who decides what.

  1. CP-00

    Signal

    You submit

    A build or vertical slice, a short design document and the honest state of the project. Playable beats polished — we would rather see a rough loop that works than a trailer that hides one.

  2. CP-01

    Evaluation

    We play it

    Two people play the build and write the assessment: what the game is, who it is for, what it still needs. You get the written answer either way, including a no.

  3. CP-02

    Terms

    We agree in writing

    Scope, milestones, revenue split, rights, territories and term. Nothing is a deal until both signatures exist, and the studio keeps its IP.

  4. CP-03

    Production

    We co-drive

    Milestone reviews, funding released on acceptance, QA passes running alongside the build instead of after it, and localisation planned before the text is frozen.

  5. CP-04

    Certification

    We handle platforms

    Store setup, technical requirement checklists, rating questionnaires and submission to each platform holder. Approval is theirs to give; the preparation is ours.

  6. CP-05

    Launch

    We run the campaign

    Announcement, press and creator outreach, festival slots, paid media where it earns its place, and the community channels staffed on release day.

  7. CP-06

    Live

    We keep going

    Patch and DLC scheduling, storefront upkeep, seasonal beats and revenue reporting to the studio for as long as the agreement runs.

//criteriaSelection

What we look for

A loop we can play

An executable build beats a document. Ten minutes that hold up is the strongest thing you can send.

A team that has shipped something

A game jam entry, a mod, a small release. Evidence you finish things matters more than studio size.

A market we can reach

We are honest when a genre is outside what we know how to sell. A no from us is not a verdict on your game.

A realistic remaining scope

What is left to build, in months and money, with the risks named rather than smoothed over.

Publishing outcomes depend on the game, the market and the launch window. We do not promise sales, revenue, wishlists, chart positions, platform approval or store featuring.