Diogenes Research

The systems behind private intelligence

Privacy is easy to market and difficult to engineer.

Diogenes Research explores the models, memory systems, agent architectures, and privacy infrastructure shaping what we're building. No vague claims.

The actual mechanics.

Research areas

Six questions we keep returning to

  1. Privacy

    What does “private AI” actually mean?

    Where does plaintext exist? What gets retained? What can an infrastructure provider see? What changes when inference runs inside confidential hardware?

    We research the boundaries behind the word private so they can be understood rather than assumed.

    Explore Privacy Research
  2. Models

    The best model isn't just the highest benchmark score.

    Diogenes Research compares open-weight and privacy-compatible models across capability, cost, speed, deployment options, and privacy characteristics.

    Because the right model for a private workflow depends on more than how well it answers a benchmark.

    Explore Model Research
  3. Agents

    An agent's capabilities matter. So do its boundaries.

    Agents can read, research, browse, write, communicate, and eventually act. That makes permission architecture as important as intelligence.

    We research how agents can become more useful without automatically gaining access to everything around them.

    Explore Agent Research
  4. Knowledge & memory

    Memory should make AI more useful without making the user less private.

    Persistent knowledge gives agents continuity. It also creates new questions around ownership, retrieval, provenance, portability, and what should be remembered in the first place.

    Diogenes Research explores how long-term AI context can remain explicit, inspectable, and controlled by the people who created it.

    Explore Knowledge Research
  5. Confidential compute

    Privacy you can verify changes the trust model.

    Trusted execution environments and remote attestation can protect sensitive inference in ways ordinary cloud promises cannot. They also have limitations.

    We research both sides: what confidential compute genuinely protects and what it does not.

    Explore Confidential Compute
  6. Crypto-native identity

    Crypto should solve a product problem.

    Wallets can provide identity, authorization, payments, and pseudonymous access without recreating the traditional SaaS account stack.

    We research where crypto meaningfully improves private AI, and where it simply adds complexity.

    Explore Crypto-Native Identity

Understand what we're building underneath the interface