Graph.oneβeta

About Us

Mission Statement

To build an open, neutral social graph layer for the internet that lowers switching costs for users and entry costs for builders, so products compete on quality instead of lock-in.

The Problem: Social graphs became moats, not infrastructure

Over the last decades, the internet’s social infrastructure has been captured by a few platforms. Facebook, LinkedIn, X and others once exposed their graphs through APIs; then, as they grew, they shut them down and began blocking or litigating against anyone trying to build on top.

This raised both switching and entry costs:

  • Users can’t leave without losing their network and history.
  • Builders can’t create new products because they can’t bootstrap on existing graphs.
  • Identity and context are fragmented across silos, destroying relationship history and producing endless duplicates.

With high exit costs and no competitive pressure, the normal mechanism that drives better products breaks down.

The Idea: A neutral social graph layer

Graph.one is building an open, neutral social graph layer for the internet.

We treat the social graph as shared infrastructure, not a proprietary asset:

  • Canonical IDs unify email, calendar, contacts, and socials into one identity per person/org.
  • Rich context (edges, attributes, events) captures how people are connected, with provenance and visibility.
  • API-first design lets developers embed social context without rebuilding the graph from scratch.
  • A data marketplace coordinates providers and buyers with transparency and predictable economics.

Anyone can plug into this layer:

  • Developers building apps
  • Companies unifying their network across tools
  • Individuals wanting their network to move with them

The Commitment: Portability, sovereignty, aligned incentives

Our model competes on utility, not lock-in.

  • Portability: Users and teams can export their graph – identities, relationships, provenance, history – at any time.
  • Interoperability: New signals and products slot into the same canonical layer without breaking schemas.
  • Aligned incentives: Lower switching and entry costs restore competition; better products actually win.