Skip to content
Cohort 10 · Closed Request a seat →

Access

Access is issued per cohort.

topcmesh onboards in cohorts of roughly a dozen teams, because every namespace gets a real engineer through migration. If you already hold a mesh key, use it below. If you don't, the queue is the way in.

Mesh key

Enter your mesh key.

Mesh keys are issued to teams onboarding in an active cohort. They are eight characters in two groups of four — m3kt-9f2a — and are printed on your key card.

Cohort 11

Request a seat in Cohort 11.

We onboard in cohorts of roughly a dozen teams. Every namespace gets an engineer through migration, which is the entire reason the queue exists. Tell us what you'd publish and we'll place you.

We read every one of these. We don't send anything else.

What happens next

Four steps, none of them fast.

  1. 01

    Your request is read

    Not triaged by a form router. Someone on the mesh team reads what you'd publish and decides whether the delivery contract actually fits it.

  2. 02

    Cohort 10 finishes migrating

    Fourteen teams, each moving topic by topic. Cohort 11 opens on completion, not on a date — which is why we don't quote one.

  3. 03

    A namespace and a mesh key

    You get a namespace ID, a key card, and a scheduled session with the engineer running your migration.

  4. 04

    One topic at a time

    Nobody cuts over in a weekend. Dual-publish to your existing tier and to a topic, compare the two, then drop the old path.