Start now
Menu

Superbrain · Free to Start

Connect Your Entire Online World Into a Single, Organic, AI-Powered Superbrain.

Whether you use Federated Computer or any other internet service, create an AI-powered overview of your world in a Superbrain that’s simple to understand and use.

Sign Up Free Get the Code

What It Is

A Bookmark Workspace for Everything You Use

Federated Superbrain is a bookmark workspace. Mix URLs from any application with Markdown notes, then add useful metadata: tags, calendar dates, kanban boards and contact associations. Preview your bookmarks, share them, and gather important signals.

Open Source

Free to Use. Free to Run Anywhere.

Your Superbrain holds the map of your online world: the links, notes, contacts and dates that tie everything together. Something that personal shouldn’t be locked inside someone else’s product. So Superbrain is free to use and fully open source.

Start in minutes. Sign up and start building your Superbrain for free. Just add your first bookmarks and notes and watch your world come together.

Run it wherever you want. Prefer to keep everything on your own hardware? The complete source code is yours to download and run on a laptop, a home server or your own cloud. Your Superbrain goes where you go, and you never have to ask permission.

Better with Federated Core. Superbrain works seamlessly with Federated Core, so it sits right alongside your Federated apps and makes it easy to connect services like Nextcloud and your email.

Help shape what comes next. Superbrain is built in the open. Read the code, report issues, suggest ideas or contribute improvements. Every contribution makes it better for everyone.

Sign Up Free Get the Code on Gitea

Features and Integrations

Everything in Your Superbrain

  • Bookmarks— create, edit and delete bookmarks with tags, contacts, previews, calendar dates, alerts, Markdown downloads and public read-only links. Bookmark collections use cursor pagination, and the UI follows every page, so collections larger than 200 stay visible on all organization screens.
  • Notion-style workspace— a Quick Find command palette (Ctrl/Cmd+K) jumps to any page, bookmark, tag or view and runs commands (new page, add bookmark, theme toggle). The slim top bar shows a breadcrumb path (workspace / section / page), sidebar sections collapse, and page rows expose hover actions (pin, inline rename, delete).
  • Pages— Markdown editing with autosave, a Notion-style slash-command block menu (type / for headings, to-dos, lists, quotes, dividers and code) and the [] + space to-do shortcut, plus link collections, pinning, reordering and export. Saves are queued per page. Unsaved drafts are kept in the current browser tab for recovery after a failed save, along with the server version they were based on, and page switching waits for pending saves. When another tab or device saved first, autosave pauses in an explicit conflict state: the editor offers overwrite, save-as-copy and discard, and typing alone never overwrites the newer version.
  • Kanban— custom columns, card moves and reordering. Deleting a column moves its cards.
  • Collections— per-project workflow state over your existing bookmarks. The same link can join many collections without duplication, each with its own typed properties (text, number, select, multi-select, date, checkbox, URL), saved table and board views, server-side filters with typed operator allowlists, and manual ordering. Membership adds context but never owns or publishes the bookmark: removing an item or a whole collection keeps the bookmark, and a bookmark whose share was revoked disappears from collections everywhere. Every change carries an expected version, so concurrent editors get a conflict instead of a silent overwrite. Reordering and property deletion advance the affected items’ and views’ revisions too, and deletions are idempotent.
  • Sharing— share bookmarks, tags and calendar dates. Recipients can read shared content, and owners can revoke shares. Shared tags and dates expose the associated URLs. Tag sharing is group-wide: every recipient of a tag sees all bookmarks carrying it, including ones other recipients add. Shared readers get only the link and its reader-facing content, never the owner’s contact record, the other recipients, alerts or mailbox watches.
  • Public links— public bookmark links deliberately publish the title, description, notes, due date, tags and preview. Contacts, alerts, mailbox watches and the owner’s identity stay private, and the share panel says so before you turn sharing on.
  • Privacy-conscious previews— remote preview images and favicons load in your browser directly from the third-party host with referrerPolicy="no-referrer", so the app URL isn’t disclosed (opening a page can still let those hosts observe the request). Server-side fetches for previews, CardDAV and IMAP never touch private network ranges, including 6to4, Teredo and NAT64-wrapped addresses. Previews are pinned to HTTP/HTTPS ports 80 and 443, mailbox connections to IMAP ports 143 and 993, and CardDAV uses its explicitly configured HTTPS port.
  • Sensible limits— text fields have per-field caps on top of the request-size limit, so an oversized bookmark title, tag name, note or page body is rejected instead of bloating every list and search.
  • Alerts— browser notifications and in-app dismissal, checked every five minutes.
  • Nextcloud— contact sync over CardDAV using each user’s app password. Credentials are used only for that request, never stored, and never sent in plaintext: the Nextcloud URL must use HTTPS, and redirects aren’t followed.
  • Email (IMAP)— encrypted per-user settings, real login tests, sender and subject searches, email watchers, and Message-ID deduplication. Verified TLS is required, so plaintext mailbox logins are rejected. Watchers ingest mail incrementally, using a saved checkpoint per mailbox to work through new messages in bounded batches instead of re-scanning old ones. Set up integrations in Settings, then check watchers from any bookmark. Enabled email watchers run every five minutes, with bounded concurrency, per-user backoff on failures, and a database-backed lease so extra instances never check the same mailbox twice.