2
5 Comments

Built PromptBrake: AI APIsecurity testing for teamsshipping LLM features (live now)

Howdy,

I’m building PromptBrake, an AI API security testing product for teams at any stage, from founders and security leaders to engineers shipping production systems.

PromptBrake is now live and ready to use: https://promptbrake.com

What it does today:

  • Tests AI API endpoints with a fixed library of real attack patterns
  • Covers prompt injection, indirect injection, data leakage, tool misuse, and safety bypass behavior
  • Returns pass/warn/fail results with evidence and remediation context

How teams use it:

  • Pre-release: catch issues before launch
  • Post-release: re-test after model, prompt, tool, or config changes

Current scope (MVP):

  • Endpoint-focused security testing
  • Manual runs
  • We’re actively hardening and maintaining reliability

Why I built it:

I kept seeing teams ship AI features fast, but security checks were inconsistent, hard to repeat, or too heavy for day-to-day engineering workflows.

Would value blunt feedback:

  • Which failure modes are most painful in your environment?
  • What’s the minimum needed for this to fit your release/security process?
  • What would block you from trying it first?

Thanks.

posted to Icon for group Startups
Startups
on February 25, 2026
  1. 1

    yoo this is super relevant rn. we ship AI features in a couple of our apps (one does personlized horoscope podcasts generated by AI, another converts artciles to audio with AI voices) and honestly security tesitng is always the thing we push to "later" which is terrible

    the prompt injection stuff is what scares me most. like when ur generating content for thousnads of users daily u cant manually review every output. having somethign automated that catches the weird edge cases before they hit production would be huge

    to answer ur questions - the biggest failure mode for us is output consistency. sometimes the AI just goes off script and generates somethign totally unrelated. not a security issue per se but defintely a trust issue

    whats the pricing model gonna look like? per-endpoint or flat fee? for smaller teams shipping 2-3 AI features this matters alot

  2. 1

    This is a great idea! I second the demo video, I would love to see it in action.

    1. 1

      Really helpful feedback, thank you!
      You’re right that clarity is everything when it comes to security tools. I’m publishing a 60–90s walkthrough this week that shows one real attack scenario, PromptBrake’s evidence output, and the end-to-end remediation flow.
      Live demo is already up here: [https://promptbrake.com/demo]. I’ll drop the video in this thread as soon as it’s live.

  3. 1

    Security products live or die on clarity.

    Right now your value is strong — but a 60–90 sec walkthrough showing a real attack scenario and how PromptBrake catches it could massively increase adoption.

    Seeing the evidence output + remediation context in action would reduce hesitation.

    If you’re open to it, I create conversion-focused SaaS demos for technical products like this. Happy to collaborate.

    1. 1

      Really helpful feedback, thank you!
      You’re right that clarity is everything when it comes to security tools. I’m publishing a 60–90s walkthrough this week that shows one real attack scenario, PromptBrake’s evidence output, and the end-to-end remediation flow.
      Live demo is already up here: [https://promptbrake.com/demo]. I’ll drop the video in this thread as soon as it’s live.

Trending on Indie Hackers
Why Indie Founders Fail: The Uncomfortable Truths Beyond "Build in Public" User Avatar 133 comments Your AI Product Is Not A Real Business User Avatar 81 comments $0 to $10K MRR in 12 Months: 3 Things That Actually Moved the Needle for My Design Agency User Avatar 77 comments I got tired of "opaque" flight pricing →built anonymous group demand →1,000+ users User Avatar 47 comments A tweet about my AI dev tool hit 250K views. I didn't even have a product yet. User Avatar 44 comments The Clarity Trap: Why “Pretty” Pages Kill Profits (And What To Do Instead) User Avatar 32 comments