The public /developers portal — Build on Turtini

Turtini has two distinct developer surfaces, and it's worth knowing which is which:

• **/developers** (this page) — the *public* portal. No login, no module gate, no admin role required. Anyone considering building on Turtini can browse it. This is the front door for partners, pro-code builders, AI agents, and anyone in the "should I build my own SaaS or plug into Turtini" decision.

• **/developer** (singular) — the *gated* partner workspace where org admins actually author, upload, and submit modules to the Marketplace. Covered in "What is the Partner Portal?"

The public portal exists to make Turtini's "stand on each other's shoulders" mission literal. A solo-built tool ships into a network of one; a Turtini module ships into the marketplace of every org on the platform the moment it's approved. Same code effort, very different orbit.

What you'll find on /developers:

1. **Hero + pitch** — Build on Turtini. Ship into the network from day one.

2. **Why plug in, not silo** — a side-by-side contrast: building alone vs building on Turtini. The point is to make the leverage visible before you commit to anything.

3. **Three install cards** — the @turtini/sdk (React hooks + Public API client), the @turtini/cli (create-turtini-module + turtini-dev + publish), and the @turtini/mcp server (wires Claude Code or any MCP client to your live Turtini org so the AI builds with full context). Each card has a one-line npm install snippet and a link to the package page.

4. **Already shipping — Built on Turtini** — a live grid of approved partner modules, refreshed in real time from the marketplace_modules collection. Each card shows the author org with a Verified-by-Turtini trust chip and a "Built on Turtini" pill. Empty state ("no partner modules yet — be the first") nudges you toward the CLI.

5. **Primitives you inherit** — a short menu of what plugging in actually gets you: identity graph, trust fabric, folio bus, Wally, Personal Vault, Marketplace + templates, domain services, unified calendar, image moderation. Each is a one-liner so you can scan it in 20 seconds.

6. **Final CTA** — "Your work, in the neighborhood." Links to /developer for actually starting a module and /partner-program for the partner-program details.

How to actually start building:

The "Start a module →" buttons land you in /developer (the gated workspace). That route requires:
• A Turtini account (sign in if you haven't)
• Admin role in an org
• The Developer module enabled (you can enable it from the Partner Program tab if you're approved)

If you don't have an org yet, click the "Start something" link in the avatar menu — that lands you in /me/start to spin one up. Then activate the Developer module from Settings → Modules and you're in.

"Built on Turtini" badge:

Once your module is approved, every Marketplace card for it carries a small "Built on Turtini" pill next to your seller name + your trust chip. The pill links back to /developers — so users discovering your module can also discover that they can build their own. The network grows on itself.

Where to go from here:

• @turtini/sdk on npm — start with a one-line install
• "Submitting a module" article — the actual 3-step flow inside /developer
• "Submission guidelines" — what the review team is looking for
• Partner Program at /partner-program — application + tier structure