VRDexWeb + Convex runtime path

Profiles, communities, and scene presence for VRChat.

VRDex now has the first submit-to-public-profile path: signed-in community members can seed unclaimed people and communities, and published profiles render at their canonical URLs.

World discovery

Worlds hosting events soon

Event-derived venue cards use confirmed VRDex event-world links. They are not live VRChat popularity, private presence, or scraped attendance.

No confirmed upcoming venues yet.

Start the local backend to read active world data, or use fixture mode during visual review.

Now in place

Public profile routes

Person pages live under /p/<slug>, community pages live under /c/<slug>, and both render shared identity, presentation, and trust state.

Deliberately deferred

Owner authority still separate

Community submissions create unclaimed profiles only. Rich claim, auth-provider setup, billing posture, and moderation workflows stay in their own follow-on issues.

Initial readiness

Hosted previews first

Before deeper product discovery, VRDex needs live Vercel previews, auth wiring, and stronger validation loops so each change can be checked outside a local workstation.