Devin Hummel
Founder, CEO & Principal Investigator
Navy veteran responsible for product direction, quality systems, operations, and turning governed engineering into software teams can understand and use.
Leadership and team
Named roles. Direct responsibility.
Our veteran-led team covers product, mission operations, cybersecurity, data and machine learning, partnerships, and platform architecture—with direct accountability from discovery through delivery.
The core team
The people behind the promise.
These public biographies stay intentionally focused on each person’s responsibility at Serapis. They do not disclose clearances, sponsors, customer access, or unrelated current employment.
Eric Vice
CISO & Electronic Warfare Systems SME
Navy veteran responsible for cybersecurity, security architecture, customer-boundary design, and operational risk across Serapis products and engagements.
Jacob R. Whitney
Chief Data Officer & Machine Learning Lead
Navy veteran leading data and machine-learning work, with an emphasis on measurable evaluation, useful automation, provenance, and evidence that remains meaningful when models change.
Izak Ramirez
Chief Strategy & Partnerships
Navy veteran leading customer discovery, partnerships, and mission alignment so each engagement begins with the operator’s real problem rather than a technology demonstration.
CK
Cody Kuykendall
CTO, Principal Engineer & Chief Architect
Platform engineer and architect responsible for translating the product thesis into reliable systems and keeping the technical path coherent as Serapis grows.
How we work
Direct responsibility from problem to operation.
A small team is an advantage only when ownership is explicit. The engagement should make it clear who can decide, who must review, and who fixes the next problem.
Start with operators
Understand the work, pressure, systems, language, and constraints before shaping a product or technical answer.
Keep owners visible
Product, engineering, security, data, and customer decisions have named responsibility instead of disappearing between functions.
Stay through operation
Deployment, maintenance, correction, model change, rule change, and customer exit are part of the product path.
One team
Bring us the problem as it actually exists.
You will work with the people responsible for understanding it, shaping the proof, and delivering the bounded result.