Team

Founder

Jeremy Bouedo, Founder

Jeremy is an engineer with two decades of experience across software and systems engineering and technical and security audit work. That combination is the reason NexArt exists.

NexArt began with deterministic rendering, where computational work produced outputs that needed to be attributable, reproducible, and provably the result of a specific run. Working on that surfaced a much bigger problem: across the wider AI ecosystem, there is no standard way to prove what actually executed. Logs describe events. Observability describes performance. Neither produces a verifiable, portable record of the run itself.

Two decades of audit work made the gap impossible to ignore. Auditors do not want narratives, they want artefacts: tamper-evident, independently verifiable, designed to outlive the system that produced them. The early work sharpened the focus. NexArt today is verifiable AI execution infrastructure, applied to the general problem that early work first exposed.

Senior Architecture

Betty Martinez, Senior Architect (Product & Protocol)

Betty is a senior architect contributing to NexArt's product and protocol design. Her work focuses on execution architecture, system boundaries, and ensuring the integrity model holds under real-world constraints.

She works directly on core technical decisions around how execution is captured, sealed, and verified, helping shape the system beyond a single-founder perspective.

This is a hands-on role tied to the architecture of the protocol and the product surface, not an advisory position.

How the work gets done

NexArt is built and run by one founder today, with help from a deliberate set of contributors. The work is structured so it does not depend on headcount:

• Protocol over product. The Certified Execution Record specification is open and independently verifiable. Anyone can implement against it without going through us.
• Independent verification. Verification does not require trusting NexArt. It requires trusting math and the published spec.
• External contributors. Specific workstreams, including cryptographic review, core architecture, client libraries, and language-specific integrations, are handled by named external engineers and senior contributors on a contract basis.
• Attestation node operators. The verification network is designed to be operated by independent parties, not by NexArt alone.
• Design partners. A small group of early customers shapes the roadmap. They are credited on the customers page when they choose to be public.

Advisors and collaborators

NexArt works with a small group of advisors and technical collaborators across cryptography, distributed systems, and AI safety. Names are listed publicly only with their consent. If you would like to be introduced to one of them as part of evaluation or diligence, get in touch.

Operating principles

• Stay small until small stops working. Every hire has to make the protocol stronger or the verification network more independent. Headcount is not a goal.
• Write things down. Specifications, decisions, and trade-offs live in public documentation, not in private chat.
• Independence by design. No single party, including NexArt, should be able to silently change what a record means.
• Auditability is not a feature. It is the product.

Hiring and collaboration

We are not running an open hiring process. We are open to the following:

• Cryptography and protocol review (paid engagement).
• Independent attestation node operators.
• Client library maintainers for specific languages or runtimes.
• Design partners running AI workloads where execution proof is a hard requirement, not a nice-to-have.

Contact

For partnership, advisory, or collaboration enquiries: get in touch.