Kristijan
Fe
d
erer

AI Systems Engineer

I build reliable AI systems, agent workflows, and full-stack applications with Python, TypeScript, and React.

About Me

I develop AI agents, automated workflows, and user-focused software with Python and TypeScript.

"Failure is an opportunity to learn and thrive."

Blog

Rethinking Secret Access in AI Agent Architectures
securityaidevtools

Rethinking Secret Access in AI Agent Architectures

Secure secret storage is not enough if an AI agent can still read the credential at runtime. This article examines credential brokering as a way to separate service access from credential possession.

16/09/20267 min read
Building Trustworthy AI Agents Starts with Distrust
ai agentscybersecuritysoftware architecture

Building Trustworthy AI Agents Starts with Distrust

AI agents should not receive authority simply because they appear capable. Trust must be scoped, enforced by architecture, supported by evidence, and remain revocable.

15/07/20268 min read
Prompt Injection: Why Secure AI Agents Must Assume It Will Happen
securityaidevtools

Prompt Injection: Why Secure AI Agents Must Assume It Will Happen

Prompt injection becomes dangerous when AI agents can access tools, data, and external systems. Secure architectures must assume it will happen and limit the damage.

02/07/20267 min read
github repositories as supply-chain entry points
securitysupply-chaindevtools

github repositories as supply-chain entry points

GitHub repositories are no longer just source control. Modern repositories act as software supply-chain entry points, making visibility, governance, SBOMs, and static analysis increasingly important security controls.

04/06/20267 min read
Building AI Agents with LangGraph: A Comprehensive Guide
ailanggraphtechnology

Building AI Agents with LangGraph: A Comprehensive Guide

LangGraph is revolutionizing AI agent development with its graph-based structures that enhance adaptability and integration across various platforms.

13/05/20266 min read
AI didn't break your .env security. Runtime did.
securityaidevtools

AI didn't break your .env security. Runtime did.

AI tools don't need your .env file. Runtime access is enough. That's the shift most developers haven't caught up with yet.

13/04/20265 min read