FAQ

This page is a work in progress. More questions and answers are coming.

Is Direct just another RPC endpoint?

No. Direct speaks plain JSON-RPC so it drops into your app like any endpoint, but behind it is a peer-to-peer network of RPC nodes and a client that routes each request across many nodes at once.

Do I have to change my code?

No. The client exposes everything as ordinary JSON-RPC. It’s two lines in the browser, or a local endpoint from the CLI — your existing requests work unchanged.

What happens if a provider goes down?

Requests fail over to other nodes in the network automatically, so there’s no single point of failure.

Can I use Direct in the browser and on the backend?

Yes. The Browser SDK covers frontend apps and the CLI client covers backend services. See Using Direct.

What is local-first syncing?

The client keeps commonly requested data in sync locally, so many reads return instantly instead of making a network round trip.

What is quorum data integrity?

The client can send the same request to several providers in parallel and compare the responses before trusting the result. See Using Direct.