You are not a database row.
Your Synapsis identity is anchored by a decentralized identifier and your signing keys. It can be exported, carried, and verified across the network.
A social network that belongs to the people running it. Sovereign identity, portable media, encrypted conversations, and independent nodes moving as one.
The network, reconfigured
Synapsis replaces the single social silo with a swarm of independent communities. Each node sets its own culture and rules. The network carries identity, discovery, and signed interactions between them.
You can join a node or operate your own. Either way, you aren’t renting a corner of somebody else’s audience. Your identity is based on cryptographic keys, your media stays portable through Stuffbox, and your connections reach beyond one server.
Built differently at the root
Your Synapsis identity is anchored by a decentralized identifier and your signing keys. It can be exported, carried, and verified across the network.
Synapsis uses Stuffbox as its portable media layer. Your photos and files live separately from your social node, keeping the same durable URLs when you move between nodes.
One-to-one text messages use client-side end-to-end encryption, with a separate recovery PIN for bringing your identity to a new device.
Nodes discover one another through the Swarm. Follows, reactions, reposts, and profiles cross boundaries as signed, verifiable interactions.
Operators control their node’s identity, moderation, registrations, and culture—without cutting their members off from the wider network.
The difference
For node operators
Synapsis runs as a native Node.js service with an embedded database. No Docker. No separate database server. Automatic updates keep every node moving with the network.
Deploy a production Synapsis node on this server.
Domain: [YOUR DOMAIN]
Admin email(s): [YOUR EMAIL]
Use the official source repository:
https://githop.xyz/GnosysLabs/Synapsis
Read README.md and deploy/ first, then use the project’s supported production installation path.
Configure Synapsis for the provided domain with HTTPS behind the existing reverse proxy, secure generated secrets, the embedded database, Stuffbox media, its systemd service, and automatic updates. Preserve existing services and data, and detect conflicts before modifying them.
Complete and troubleshoot the deployment until it is healthy. Verify the systemd service, public HTTPS site, /api/version, and update timer. Then report the live URL, important configuration/data/backup paths, services changed, and secrets the operator must retain.
Ask only when a required value cannot be inferred or a choice could risk existing services or data.
The signal is already moving
Join a node. Start a node. Bring your identity.