sharedgraph.

For builders of the next social web

One social network.
Many applications.

SharedGraph is being built to connect independent apps through one public identity, relationships, and conversation.

Join the builder waitlist Read the developer docs

Pilot · Public reads open · Apps by reviewed registration

Continuity, by design

The app changes.
The thread stays.

Imagine one person posts through a project app. Someone replies through a different app. Both see the same public conversation, and the same people remain themselves across each view.

01

Mira publishes in Fieldnotes.

02

Leo replies from Commonroom.

03

One conversation, seen through either app.

Illustrative concept. These apps and posts are examples, not live products or integrations.

VIEW THE SAME THREAD IN
Fieldnotes A place for working notes

A note from the field

Mira Chen@mira
2h ago

Small tools make room for new ways of working. What are you building this week?

Leo Park@leo
from Commonroom

A quieter space for project updates. This thread is exactly the kind of thing I want it to keep.

Shared public conversationMira and Leo stay the same people ↗
Different interfacesSame people & replies

Own the experience

Build your corner.
Share the commons.

Give people a distinctive experience while keeping the relationships they build on SharedGraph.

01

Your interface. Make a focused experience for the people you serve.

02

Your business. Keep your own brand, code, and business model.

03

A shared public layer. Build around planned common identities, relationships, posts, and replies.

Try it now · No key needed 

curl https://api.sharedgraph.com/api/feed

The public feed answers anonymously. Everything else starts in the developer docs.

Read the quickstart

App-specific data, purchases, drafts, and private workflows remain with the app. Private information would require appropriate authorization.

Many ways in

Room for
different ideas.

The first apps could feel entirely unlike one another. The connective tissue is the public social layer they choose to share.

A

Project updates

A team shares what it’s building. People following them in other apps can reply.

B

Article reader

Share a link worth reading. Friends using other apps join the same discussion.

C

Book club

Discuss a book while keeping the people and conversations you follow elsewhere.

Illustrations of what builders might create, not announced apps or launch partners.

An honest starting point

Start with the
public web.

The planned first release is for browser-based apps and public text and link conversations. SharedGraph is prelaunch, and the network is still being built.

Native apps, media hosting, private groups, and direct messages are beyond this initial scope. Changing SharedGraph apps is a different view of the same network, not a migration to another one.

A few useful answers

Good questions,
early answers.

Is SharedGraph live?

As a pilot. Public content can be read today, and registered apps can act for people who consent. Joining the waitlist does not create an account or grant access.

Does every part of an app carry over?

No. The planned shared layer is public identity, relationships, and public conversations. An app’s drafts, purchases, and private workflows remain its own.

Can I build an app now?

Yes, within the pilot. Anyone can read public content without credentials. A signed-in app needs an operator-reviewed registration, described in the developer docs. Still exploring an idea? Join the builder waitlist and tell us what you hope to make.

When will it launch?

We have not announced a date. We will share meaningful progress with people on the waitlist.

An invitation to shape what comes next

Let’s make room
for more apps.

Building something? We’d like to hear from you. Just curious? We’ll keep you posted as SharedGraph develops.

I’m here to...

We’ll use your email for SharedGraph access and launch updates. No confirmation email is sent.