shipwithjev

Blog / Builds & people / FIG. 148

The Jev Discord: Where Builds Surface First

The Jev Discord is TypeSafe AI's official builder server. Where demos surface in Show and Tell, how to post well, and what to take elsewhere.

The Jev Discord is TypeSafe AI's official community server for builders, support, and discussion, per the community lists that index it. If you're building with Jev, the decision model TypeSafe launched in September 2026, it's where demos tend to appear before they reach X threads, GitHub stars, or this directory. We lurk there like everyone else; we don't run it, and this site isn't affiliated with TypeSafe.

How the first week of builds unfolded is the launch-week story; this page is the practical guide to the room.

How to find the real server

Get the invite from official sources: typesafe.ai or docs.typesafe.ai, or the official link in a curated list like awesome-jev. Don't join from a random reply-guy link. Launch-season impersonation servers are a known pattern, and the fake ones always want you to "verify your wallet."

Show and Tell: the channel worth watching

Community listings put it plainly: builder demos live in the Show and Tell channel. That's typesafe show and tell in practice: short clips, repo links, "it works, here's the weird part" posts. It's the closest thing the ecosystem has to a live feed of what's getting built, and it's often the earliest place a pattern appears before it has a name.

Watching it well means reading for three things:

  • The number. Posts that say what it cost, how many items, how long it took are the ones worth following up.
  • The failure. The builder who shares where it broke is teaching more than the one sharing a highlight reel.
  • The repeat. When three unrelated people post the same architecture, that's a pattern forming, which is how cascades and compaction plugins became standard.

Posting your own build

A good Show and Tell post has a one-line claim, a short demo, a link, and one honest number with how you measured it. Skip the "revolutionary" adjectives; this crowd has seen a lot of Doom clips. If the build does something consequential (moderation, money, hiring), say what the human does in the loop, because someone will ask.

Then bring it here: submit the build with its numbers, and it gets a permanent, linkable page with the receipt attached, something a chat channel scrolls past in an afternoon. A Discord-native example already in the catalog: a moderation bot with Jev making the calls, and if you're building one, the Discord moderation recipe covers the pipeline.

What to take elsewhere

Account, billing, and API behavior questions deserve official answers, so check the docs first and use the server's support channels as designed. Don't paste API keys or customer data into a screenshot. And treat any technical claim in chat, including confident ones, as a lead to verify, not a spec. New to what Jev is? Read that before asking the room.

Frequently asked questions

Is there an official Jev Discord?

Yes. Community lists describe an official TypeSafe server for builders, support, and discussion; get the invite from TypeSafe's own site or docs.

Where are builds posted in the Discord?

In the Show and Tell channel, per community listings, which is where builder demos and works in progress surface first.

Is shipwithjev.com part of the Discord?

No. This directory is independent and not affiliated with TypeSafe AI; we catalog builds with receipts, and you can submit yours.

Can I get API support there?

The server includes support discussion, but the ruling source for API behavior is docs.typesafe.ai; treat chat answers as leads.

Numbers throughout are as reported by the build authors, not verified by shipwithjev. Code-shaped examples are pseudocode; the official docs live at docs.typesafe.ai.