Product
Six parts over one folder
Underneath all of it there is a folder on disk that belongs to your company. Search, the graph, the agent, permissions and the usage ledger all work on top of it. Each part has its own page, covering what it does today and what it still does not.
- Files that open in any editor
- One folder per company at mode 0700
- Indexing and search are never charged
-
Company vault
Your knowledge in files you own
- One folder per company at mode 0700, isolated by the filesystem
- Standard Markdown and your original binaries, no proprietary format
- Personal notes stay private even from the company owner
-
AI agent
It works inside your files, not on a copy
- One agent per department that the whole team sees, plus private personal chats
- It hands work to another department's agent and gets the answer back, several running at once
- The work streams live: iteration, tool call, result
-
Search and graph
Finds by meaning and by exact term at once
- Semantic and exact-term search, combined with reciprocal rank fusion
- Company isolation lives in the query itself, not in a post-filter
- Local indexing model: uploading your document history does not count against your plan
-
Departments and permissions
Your org chart, enforced branch by branch
- A department tree with no depth limit
- Company role and per-department role, inheriting downward
- No privilege escalation, and the last owner cannot be removed
-
Teamwork
The conversation, where the work already is
- Direct messages, groups and one thread per department, all access-controlled
- Real time, degrading gracefully when the connection drops
- Browser notifications with a mark-as-read
-
Governance and usage
Who spent what, in which process, on what day
- Per-company meter: budget, spend and the last days in detail
- Billing is idempotent: a retry never charges twice
- Downloadable monthly log, covering text size and never its content
Beta Alongside the six pieces
Your own machine, for the heavy work
Sometimes the work does not fit in what is shared: a process that takes hours, or a system of yours that has to stay up. You can order a machine from inside Vonzay and assign it to a department.
- That department's agent gets the credentials as a secret and works on it
- Billed apart from your plan, the same way image and video generation are
- It is in beta: machines are running already and it still changes, so ask us before you count on it
The idea holding it up
Disk is authoritative
The search index, the link graph and the agent's context are views of the vault. Corrupt them and they rebuild by reading the files. Delete the folder and there is nothing left to rebuild from.
- Taking your information out means copying a directory. There is no export that translates one proprietary format into another, because there was never a proprietary format.
- Rebuilding an index is routine. Swapping the search engine, reindexing from scratch or moving the graph to different storage puts no document at risk.
- What gets backed up is the folder. Daily database dumps and hard-link snapshots of the vault, kept for 14 days.
- Vault on disk your notes and your files
- Ingest hash, chunks, vectors
- Index, graph and context rebuildable