Skip to content
Developer toolsNew techTop 15% of today's analysed ideas

Tooling layer for Rust-based GPU kernel development

Build developer tooling around Enki (GPU compute kernels in pure stable Rust): starter templates, CI/build integrations, benchmarking dashboards, or a hosted playground that lets ML/graphics engineers write and test GPU kernels in Rust without CUDA toolchain setup. Package it as a paid dev-tool add-on (e.g. kernel profiling-as-a-service or a template marketplace) targeted at Rust devs moving into GPU compute.

Original post

What to build

A starter-kit for Enki: a cargo-generate template plus a ready-made GitHub Action that builds, tests, and benchmarks GPU kernels written in stable Rust, aimed at individual Rust developers who want to try GPU compute without setting up CUDA or nightly toolchains.

Enki's Show HN proves there's curiosity about writing GPU kernels in stable Rust, but the project itself is too early to monetize directly — the opportunity is the glue layer (templates, CI, benchmarking) that makes it usable day one.

Demand

Rust developers and graphics/ML engineers who want GPU compute but are blocked by CUDA toolchain friction or nightly-only Rust GPU crates are the audience; timing is driven by the fresh Show HN post putting Enki in front of that exact crowd right now.

  • Hacker News (Show HN)News

    Show HN: Enki – Write GPU compute kernels in pure stable Rust — 9 points, 1 comment on HN.

Stack

  • Enki
  • cargo-generate
  • GitHub Actions
  • Docker (GPU-enabled runner)
  • Supabase (benchmark result storage)
  • Cloudflare Pages (docs/playground site)

Solo + AI difficulty

The template and CI Action are a weekend build for one person with AI help — mostly config and docs work. The hard, slow part is a hosted playground: it needs real GPU-backed infrastructure to execute untrusted kernels safely, which is costly and non-trivial for a solo builder, so MVP should skip hosting and ship template+CI first (roughly 1-2 weeks), treating the playground as a stretch goal once Enki itself shows retained usage.

Entry threshold
Low capital barrier, but requires genuine Rust and GPU/compute knowledge to build credible tooling; a weekend MVP (templates, docs site) is feasible, but a differentiated paid product likely takes a few weeks of focused work.
Window
6-12 months

Where to find first users

  • Comment and follow up directly on the Enki Show HN thread and GitHub repo
  • r/rust and r/GraphicsProgramming
  • Rust GPU / compute Discord and Zulip channels
  • A second, narrower Show HN post once the template+CI tool has its own repo

Counter-signals & risks

  • GPU compute tooling is dominated by mature ecosystems (CUDA, wgpu, rust-gpu, Vulkan compute) with large existing user bases, making adoption of a new niche framework like Enki uncertain.

  • Show HN traction alone (9 points, 1 comment) does not establish sustained developer demand or willingness to pay for add-on tooling; many Show HN projects see a one-time spike and no retention.

  • Building a paid layer (profiling-as-a-service, template marketplace) requires Enki itself to reach critical mass and stability first, and the underlying project's long-term maintenance/roadmap is unverified from this signal alone.

Original title: Show HN: Enki – Write GPU compute kernels in pure stable Rust

  • Developer tools#4

    MCP Connector Library for AI Coding Agents

    Build a ready-made MCP (Model Context Protocol) server or toolkit that connects Claude, Cursor, and Codex to popular third-party APIs and services, enabling AI coding agents to automate integrations without manual glue code. Package it as a hosted service or CLI tool targeting solo developers and small teams who use AI-first IDEs. Monetize via subscription access to a growing library of pre-built MCP connectors.

    Demand
    7/10
    est.
    Buildability
    7/10
    est.
    Competition
    7/10
    est.
    via Product Hunt
    22 competitors
  • Developer tools#7

    Plan State Persistence Layer for Claude Code Re-Runs

    Build a lightweight plan persistence and idempotency layer for Claude Code that tracks executed plan steps, stores state between runs, and prevents duplicate actions on re-runs. Target solo developers and small teams using Claude Code for multi-step agentic workflows who lose progress when sessions restart or plans re-execute from scratch.

    Demand
    6/10
    est.
    Buildability
    8/10
    est.
    Competition
    8/10
    est.
    via Product Hunt
    11 competitor
  • Developer tools#8

    Developer Context Save and Restore Tool as Micro-SaaS

    Build a lightweight SaaS or CLI-plus-web-app called something like Park that lets developers save and restore full work context — open files, terminal state, branch, notes, clipboard snippets — across multiple repos and machines. Sell it as a subscription to solo developers and small teams who constantly context-switch and lose their train of thought. Integrate with VS Code and JetBrains as a plugin for frictionless adoption.

    Demand
    1/10
    measured
    Buildability
    7/10
    est.
    Competition
    6/10
    est.
    via Hacker News
    33 competitors
Tooling layer for Rust-based GPU kernel development — Nichr