Prismix

Roadmap

What we're building, in what order, and why. Vote on the ones that matter to you — votes shift the priority queue. Got an idea that isn't here? Submit it.

Status: All In progress Planned Idea Shipped
Sort: Popular Recent

Ideas · 6

  • 12
    Idea

    Follow developers whose stack you trust

    See what they bundle, what they review, what they ship with. The asymmetric "follow" model (Twitter-style, not Facebook-style).

  • 9
    Idea

    Browser extension for Claude.ai / ChatGPT / Cursor

    Read your already-visible usage limits (no cookie access), surface them in Prismix. Pair with a per-device token, revocable any time.

  • 7
    Idea

    Public read API (versioned, rate-limited)

    GET /api/v1/servers — paginated, filterable. SDK comes after. Build your own MCP launcher. (The /api/v1/statuses + /api/v1/incidents endpoints for the status hub already follow this pattern.)

  • 6
    Idea

    Anomaly detection on API spend + incident frequency

    Statistical baselines per provider — flag when your daily OpenAI spend is 3σ above last 30 days, or when Anthropic incident count spikes for the week. Email + webhook alert. Pro feature.

  • 4
    Idea

    Affiliate partnerships with Claude Desktop, Cursor, Zed

    "Install via Claude Desktop" buttons that pass attribution. Revenue share goes to maintaining curation.

  • 3
    Idea

    Migrate hot tables KV → D1

    KV is great for write-once-read-many key/value. When the directory + feed cross ~10k items, the trending sort + filtered queries cost too many round-trips. Migrate `mcp:server:*`, `feed:item:*`, and `roadmap:item:*` to D1 while keeping KV for caches + sessions.

Have an idea we missed?

Submit it to the queue. Other users vote — the ones that gain traction get prioritised on the actual build schedule.

Sign in to submit + vote

Free account, 30 seconds. Email code or GitHub one-click. We bring you right back here.

Sign in →