The Riptides Team

We are a small founding team with deep experience in security infrastructure, distributed systems, and AI deployment. We built Riptides because we ran into the problem ourselves.

01

Founders


Márton Sereg - CEO & Co-Founder

Márton Sereg

CEO & Co-Founder


Márton spent eight years in security infrastructure at large-scale distributed systems environments before founding Riptides. He has hands-on experience with identity systems, policy engines, and the operational realities of securing workloads at scale. He led the technical investigation that identified the identity gap in AI agent deployments.

hello@riptidesio.com

Dr. Sarah Okonkwo - CTO & Co-Founder

Dr. Sarah Okonkwo

CTO & Co-Founder


Sarah holds a PhD in distributed systems and previously led the runtime security team at a cloud infrastructure company. She designed Riptides' cryptographic attestation protocol and oversees the core engine that issues and validates runtime identities. Her research on workload identity has been cited in multiple security conference proceedings.

Marcus Delgado - VP Engineering

Marcus Delgado

VP Engineering


Marcus joined as the third member of the founding team after a decade building developer tooling and security instrumentation at enterprise software companies. He leads the platform engineering team and owns the integration architecture that allows Riptides to deploy alongside any AI framework without requiring code changes to existing agents.

02

How We Work


We are a distributed team based primarily in Seattle. We ship fast, document decisions, and hold each other accountable to the same security standards we ask of our customers.

Build to Last

Security infrastructure is not a feature you ship once. We build with longevity in mind, and our internal review bar is higher than what we ship to customers.

Customer Context First

Every feature decision starts with a real deployment scenario from a customer or prospect. We do not build for imagined future use cases before solving the problems in front of us.

Open Discussions

Technical decisions are made in the open, documented in writing, and revisitable. We disagree productively and move forward with clarity rather than false consensus.

We are building the team

If you have a background in security infrastructure, distributed systems, or developer tooling and you want to work on a genuinely hard problem, get in touch.

Get in Touch