Scryve. Learn

All guides / How Scryve works

How Scryve is built

The parts Scryve is made of, for readers who want to know what runs behind the pages.

In short#

Scryve is a web app with a server and a database behind it. This page names the parts. It lists no secrets and no private addresses.

The parts#

  • The pages you see. Built with React and Vite. The article editor is TipTap.
  • The server. A Node server written with Express.
  • The database. PostgreSQL, used through Drizzle.
  • Images. Stored in Cloudflare R2. Scryve serves them from its own address.
  • Fonts and pages. Both come from Scryve itself.
  • Sign-in. A JoyID passkey wallet, or a link sent by email. See Sign in.
  • Payments. Checked on the chains themselves: CKB, Ethereum and Bitcoin. Scryve looks the transaction up before it records a tip or starts a plan.
  • Sealed articles. Your wallet signs the article's fingerprint. The seal can be recorded on CKB. A permanent copy goes to Arweave through ArDrive Turbo. See What a seal is.
  • Languages. The interface is in English and Portuguese.

How a change reaches you#

The code is in a private repository. Pushing to it does not publish anything. Two copies of the app run side by side, one for the live site and one for the test site. A change goes to the test copy first, is looked at there, and only then goes to the live site. Each copy has its own database and its own secrets. See The live site and the test site.

The network and the feature switches are read when the app starts. Changing one means a restart, not a rebuild.

Good to know#

  • Everything on this page describes 2026-11-16.

If something goes wrong#

  • Buy Crypto is not set up on the test site. See Buy crypto.

Checked: 2026-11-16