About Caution

The internet should be open, transparent, and verifiable. Today too much of it still runs on blind trust. We’re here to change that.

Our mission

We believe that the future of compute is verifiable, transparent, and open.

Make verifiable compute the default way to run software.

Our team

We're a small team of engineers who've spent years securing critical systems. Now we're channeling that experience into building infrastructure we wish existed.

Anton Livaja

Anton Livaja

Co-founder, CEO | Keyoxide

Lance Vick

Lance Vick

Co-founder, CTO | Keyoxide

Ryan Heywood

Ryan Heywood

Security Engineer | Keyoxide

Ksenia Lesko

Ksenia Lesko

Strategy & Operations

Our values

Our values shape how we build, and guide every decision we make.

  1. Decentralize trust
  2. Open source everything
  3. Security beyond compliance
  4. Move thoughtfully & improve things
  5. Impact over profit

Our story

Every problem we solve started as a pain we saw firsthand. This is where the idea for Caution began.

Caution is built for teams running security-critical systems where trust alone is not enough. It grew out of our work at Distrust, a security consulting and open source R&D firm founded by Lance and Anton, focused on defending high-risk systems.

Through Distrust, we worked with hedge funds, custodians, Layer 1 and Layer 2 blockchain teams, cloud platforms, and critical grid operators, helping secure systems responsible for more than $100B in assets.

Across these engagements, we saw a general lack of reliable visibility into what software was actually running in production systems, especially in real time. Mission-critical infrastructure was often operated as a black box, with limited ability to independently verify what was executing. That approach did not sit right with us. Verifiable compute offers a new way to use confidential compute with meaningful transparency and proof, especially where trust matters most.

Companies needed better tools. They needed reproducible builds, verifiable deployment, cryptographic proof of running code, and stronger guarantees for enclave workloads.

So we built Caution.