Unified Corpus · data stays at Source

One place to find your data. No place you have to surrender it.

Your email, files, photos, notes, messages, records, and work are scattered across devices and services. reBe Corpus gives you one governed view and lets reBe Flow and RAG work across it—while authoritative data stays where you keep it.

Start locally for free Join the $9 founding pilot

No managed storage quota. No automatic upload. Paid pilots are human-assisted; self-serve checkout is not presented as live.

EmailFilesNotesPhotosMessagesCalendarFinanceHealthDevelopmentCustom
Source ContractsLocal indexesGranted evidence
reBe answer

Evidence from 4 Sources · 3 current · 1 unavailable

Source truth, projection, and inference remain visibly distinct.
Source-residentAuthoritative bytes stay with their Source.
UnifiedOne catalog and query path across scattered data.
DistributedCompute and search move toward the data.

How it works

A Corpus is an addressability plane, not another vault.

It knows what exists, where it is authoritative, which local indexes exist, what a grant permits, and what evidence can leave.

01

Connect Sources

Register the mailboxes, folders, drives, apps, devices, and services you choose. A Source Contract records what exists and what may be done.

02

Index beside the data

Text, vectors, metadata, graph edges, and freshness stay in your browser, on your device, or inside your Realm wherever practical.

03

Ask once

Corpus plans the query across eligible Sources and returns the smallest permitted evidence with citations, freshness, and boundaries.

04

Put it to work

reBe and Flow can summarize, compare, notify, or propose action. A product entitlement never replaces the grant required to read your data.

One contract · four runtime boundaries

Begin in a browser. Expand only when it creates value.

Runtime tiers describe where work can run. They are not commercial plans and they do not form a cloud-promotion ladder.

T0Source implemented

Browser

Encrypted OPFS, local indexes, WASM/WebGPU, and user-selected Sources.

T1Founding pilot

Your devices

cyos-node, local files and mail, watchers, SQLite/vector search, and local models.

T2Design-partner pilot

Your Realm

Private query planning, heavier indexes, Flow, optional owner-approved replicas, and backup.

T3Contract source

theCy

Public Application delivery, consented evidence, federation rendezvous, and bounded caches. No private raw Corpus.

Freemium plus paid founding pilots · CAD

Pay for reach, automation, and support—not for surrendering custody.

These launch offers are independent of runtime tier. Every data read still requires its own Agency grant.

Local

Free

forever
Available in source

Start in one browser. Build a useful local Corpus without an account or a vendor storage bill.

T0
  • Encrypted browser-local Corpus
  • Up to 3 user-selected Sources
  • Local lexical and vector indexes where supported
  • Search, export, purge, and basic Flow templates
Start locally

Personal

$9

CAD / month · $90 annually
Founding pilot

Unify Sources across the phones and computers you already own. Your devices do the storage and work.

T0T1
  • Everything in Local
  • Up to 5 owner devices and 12 Source connectors
  • cyos-node adapters, watchers, local embeddings, and RAG
  • Cross-device catalog and founding-pilot onboarding
Join the paid pilot

Realm

$39

CAD / month · owner infrastructure
Design-partner pilot

Add an owner-controlled private Realm for a household or professional practice.

T0T1T2
  • Everything in Personal
  • Up to 6 people and 25 devices
  • Private Realm query, vector, Flow, and derived-index backup
  • Purpose-scoped grants and design-partner onboarding
Become a design partner

Organization

$18

CAD / person / month · 5-person minimum
Design-partner pilot

Connect organization knowledge without building a central employee-surveillance copy.

T0T1T2T3
  • Corporate and personal Source ownership stays separate
  • Organization Source Contracts and purpose-scoped grants
  • Source-local RAG, roving compute, evidence, and revocation
  • T3 public/consented projection rendezvous—not raw data hosting
Discuss a pilot

The T3 boundary

theCy can host the Corpus Application. It does not become your Corpus.

T3 may carry

Public Application artifacts, signed Source Contract projections, consented evidence, bounded caches, entitlement state, and route evidence.

T3 may not carry by default

Private raw email, files, health or finance payloads, Realm NFS, source databases, owner keys, or an owner control plane.