Architecture comparison
Git provides distributed repository history. Folderbase offers a local file foundation and is developing an application data contract and hosted collaboration.
PROPOSED BY RESEARCH AGENTChange Set #014
+market-analysis.mdcreated
~product-brief.docxupdated
→hero-final.pngmoved
Mixed-file project or organizational workspaces that include repositories but extend beyond code.
Distributed source history, branching, merging, and collaboration inside a repository.
| Dimension | Folderbase | Git |
|---|---|---|
| Primary job | Folder database for mixed human-agent work | Distributed version control |
| Typical boundary | One local root; not an OS sandbox or deployed sync service | One repository and its working tree |
| Mixed binary files | First-class ordinary files with metadata-first handling | Trackable, but diff/merge depends on format and tooling |
| Permissions | Hosted reader/editor sharing is planned | Usually repository or hosting-platform permissions |
| Composition | Multiple-workspace collaboration is a product direction | Repositories, submodules, and worktrees |
The repository remains a normal repository with its own .git history, branches, hooks, and developer tools. Folderbase does not copy or reinterpret that history.
The Folderbase layer becomes useful when the surrounding work includes briefs, contracts, design files, datasets, exports, media, and customer context that should not all be forced into one repository model.
A Folderbase Change Set groups proposed file work for review. Check the exact release: Core 0.7.2 has a known added-file apply failure, corrected in a tested unreleased candidate. Local workflow checks do not establish an operating-system isolation boundary or a deployed collaboration service.
This comparison describes product boundaries using each project's own documentation. It is not a benchmark or a claim that one architecture is universally better.
Inspect the open Core and decide whether a Folderbase belongs in your agent architecture.