JNJSOFT

Technical content that engineers forward to each other.

I write comparison pages, tutorials and explainers for developer-tool and AI-infrastructure startups. Built from your docs, code tested, and aimed at what developers actually search.

keep-api-keys-away-from-ai-agents.md
  1. Use a secrets manager to keep your API keys safe from AI agents.
  2. A secrets manager fixes storage.
  3. The agent's process still fetches the key into its own memory.
  4. The credential it fetches with is available to the agent too.
  5. So a prompt injection can make the same fetch. Better storage, same exposure.
  6. Here's the fix, in about 40 lines of mitmproxy…

Most content in this space is the red line. Your buyers have read it a dozen times. I write the green lines.

Read a sample first

How to keep API keys away from AI agents (and still let them call your APIs) A 2,000-word tutorial: a live prompt-injection leak, a working credential-injection proxy, and an honest section on where the do-it-yourself version breaks. Publishing here shortly. Email me for the draft.

That's the standard for every piece: a real problem, working code, and no claims I can't point to a source for.

What you get each month

In-depth articles
6 tutorials or explainers
Comparison pages
4 "alternative to" or "X vs Y" pages
LinkedIn posts
12, written for a founder's profile
SEO basics
Keyword, title, meta description, slug

$3,500 a month

Three-month minimum, because search takes that long to show results. Not ready to commit? I'll write three article briefs for your company first, for free.

How it works

  1. A 30-minute onboarding callYour product, your buyers, your voice, and what we must never claim.
  2. Briefs you approveEach piece starts as a brief: the search it targets, the angle, the outline. Nothing gets written until you say yes.
  3. Drafts, checked and testedEvery claim checked against your docs or a public source. Code run before you see it.
  4. Your review, then publishQuestions only your team can answer come back marked, not guessed. You approve every piece before it goes live.

Yes, I use AI

Research and first drafts run through an AI pipeline. That's how I keep this affordable for a seed-stage budget.

What it doesn't do is decide what's true. A separate review pass fact-checks each draft against sources, anything only you can confirm comes back as a question like [[NEEDS CLIENT: exact error for a blocked host]], and I read, edit and test every piece myself before you see it.

Who you'd work with

I'm Jesudas Lobo, a software solution architect at JNJSOFT. My day-to-day work is custom integrations and data-analytics pipelines for enterprise platforms like Salesforce, Pega and Oracle Cloud, mostly in Python, Node.js and Clojure.

That's why the content reads like an engineer wrote it: I know what your buyers have already tried, and what makes them close the tab. I work with a small number of seed to Series A companies at a time.

Want three free briefs for your company?

Send me your company name and I'll send back three article briefs based on what your buyers search for. Keep them either way.

Email me your company name

Or write to jesudas.lobo@jnjsoft.co.uk.