Convex targets both developers and vibe coders — and shows GitHub stars as social proof

The Tactic

Convex's homepage presents two distinct entry points in a single hero section: a traditional developer path centered on npm create convex and an AI-assisted path through their "Chef" AI builder. Above both, the navigation bar displays their GitHub star count (7,138) as a persistent trust signal.

This is a dual-persona strategy that acknowledges a fundamental shift in the developer tools market: the audience is bifurcating. Traditional developers want CLI commands, documentation, and full control. A growing segment of "vibe coders" — people building with AI assistance who may not consider themselves developers — want guided, visual, AI-powered creation flows.

Most companies pick one audience. Convex serves both from the same homepage without making either feel secondary.

The Dual Persona Architecture

The structural choice here is worth studying in detail. The hero doesn't compromise by finding a middle ground between the two audiences — it separates them explicitly. The npm install path signals: "You know what you're doing, here's the fastest way in." The Chef AI path signals: "You have an idea, we'll help you build it."

This separation works because the two personas have fundamentally different evaluation criteria. A traditional developer looks for performance benchmarks, API design quality, and type safety. A vibe coder looks for speed, simplicity, and whether the tool can handle the thinking for them. Trying to address both with a single message would satisfy neither.

The visual hierarchy subtly prioritizes the developer audience — the npm command is more prominent — while giving the vibe coder path enough visibility to be discoverable. This tells you where Convex's primary revenue comes from while acknowledging where growth is heading.

GitHub Stars as Navigation Social Proof

The placement of "7,138" GitHub stars in the navigation bar is a deliberate architectural choice, not a vanity metric. In the navigation, the star count is visible on every page of the site, creating persistent social proof that reinforces credibility throughout the entire evaluation journey.

GitHub stars convert differently than other forms of social proof because they represent a specific type of validation: other developers found this interesting enough to bookmark it. Unlike customer logos (which prove enterprise adoption) or testimonials (which prove satisfaction), GitHub stars prove developer interest — which is the leading indicator for open-source adoption.

The specific number matters too. 7,138 is large enough to signal genuine community adoption but specific enough to feel real. Rounded numbers ("7,000+") feel like marketing. Exact counts feel like data.

For developer tools built on open source, the GitHub star count is the single most credible trust signal available. Placing it in the navigation — rather than burying it in a "Community" section — maximizes its impact across the entire site visit.

Why This Matters for B2D

The vibe coding trend represents a fundamental expansion of the developer tools TAM. Products that can serve both traditional developers and AI-assisted builders will capture a larger market, but only if their marketing doesn't alienate either group.

Convex's approach shows how to do this structurally. The key is that each persona gets their own interaction pattern. The developer gets npm create convex — a command they can copy-paste into a terminal immediately. The vibe coder gets Chef — an AI assistant that asks what they want to build. Neither path requires understanding the other.

This dual-entry strategy also creates a natural upgrade path. Vibe coders who outgrow the AI-assisted flow will eventually want the full CLI experience. By the time they do, they're already on Convex's platform.

FAQ

At what GitHub star count should you display stars in the navigation?

Display stars once you cross roughly 1,000. Below that, the number can signal early-stage risk rather than adoption. Between 1,000-5,000, it shows meaningful traction. Above 5,000, it's a strong trust signal. Above 20,000, it becomes a competitive moat. If you're below 1,000, focus on growing the count before displaying it prominently.

How do you serve two personas without confusing the page?

Spatial separation and visual hierarchy. Put the primary persona's CTA in the most prominent position, and give the secondary persona a clearly labeled alternative path. Use language that each persona self-identifies with — developers recognize CLI commands instantly, while non-developers recognize AI chat interfaces. The two groups will self-select.

Is the vibe coder audience worth investing in for developer infrastructure?

Yes, but with caveats. Vibe coders generate lower immediate revenue per user than professional developers, but they represent a massive growth vector. Many will become paying customers as their projects scale. The strategic value is in market expansion — capturing users who would never have evaluated a backend-as-a-service product without an AI-assisted entry point.