Team

The people behind DataDam.

Founder-led. Customer-pull category. The proxy is the wedge; the team is the why.

Why we built DataDam

Govern the path. Not the people.

Every regulated enterprise we talked to was hitting the same wall at the same time. AI agents (coding agents, research agents, IDE assistants) read enterprise data through whatever connection string the developer happened to wire up. No policy layer, no audit log, no PII masking, no record of who saw what. The governance work the company had spent years putting in front of analysts and BI tools simply did not exist for agents.

We built DataDam because the answer was obvious in retrospect and missing in practice: govern the path the agent takes to data, not the people writing prompts. Put a proxy in the customer environment. Authenticate every request. Evaluate it against a deterministic policy. Mask fields per role. Write the decision to an immutable audit log. Do all of it without making the agent's developer change one line of code.

The proxy is the wedge. Once it sits between agents and data, every other piece (trust scoring, anomaly detection, compliance blueprints, the MCP gateway) composes on top.

Headshot of Josh Tepen, Founder at DataDam

Founder

Josh Tepen

The architect behind DataDam.

The architect behind DataDam's entire technical stack, from AWS infrastructure and security to the policy engine and admin console. Joshua built DataDam to solve a problem he saw firsthand: enterprises need a tool they can trust, not another black box.

Headshot of Phil Komarny, Founder at DataDam

Founder

Phil Komarny

Technology executive with a track record of building and scaling enterprise platforms.

Technology executive with a track record of building and scaling enterprise platforms. Phil's experience spans blockchain, infrastructure, and digital transformation across Fortune 500 companies, bringing operational rigor to DataDam's growth strategy.