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#1

    Cost-control proxy for high-volume AI agent API usage

    Build a lightweight usage metering and cost-control proxy for AI agents that sits between autonomous agents and the APIs/SaaS tools they call (CRMs, email, data stores). It tracks per-call volume, flags anomalous spend before vendors introduce agent-specific pricing tiers, and recommends cheaper self-hosted or direct alternatives (like swapping a managed service for a $5 Postgres instance). Target solo builders and small teams running high-call-volume AI agents who want to avoid surprise six-figure vendor quotes.

    Demand
    5/10
    est.
    Buildability
    8/10
    est.
    Competition
    10/10
    est.
    via SaaStr
    0No named competitors
  • Developer tools#5

    Shared memory layer for multi-agent coding workflows

    Build a shared memory and coordination layer for people running multiple AI coding agents (Claude Code, Cursor, Codex, OpenCode) at once, so decisions, rules and task context persist across sessions and tools instead of being re-explained every time. A Windows/Linux equivalent, a team-focused paid tier, or a lighter single-purpose plugin (just the decision ledger, or just cross-agent memory) are all underserved angles since the example tool is free, individual-only and macOS-exclusive.

    Demand
    5/10
    est.
    Buildability
    6/10
    est.
    Competition
    10/10
    est.
    via Reddit
    0No named competitors
  • Developer tools#4

    Hosted API wrapper for structured PDF extraction

    Wrap this lightweight PDF parser (layout, tables, formulas, bounding boxes) into a hosted API or no-code upload tool for developers building RAG pipelines, document QA bots, and data extraction workflows who need structured output from messy PDFs like academic papers, invoices, and financial filings. Target solo devs and small teams who don't want to self-host a heavy parsing stack.

    Demand
    4/10
    measured
    Buildability
    8/10
    est.
    Competition
    5/10
    est.
    via Hacker News
    44 competitors
Tooling layer for Rust-based GPU kernel development — Nichr