Architecture comparison

Folderbase vs. AgentFS

Compare Folderbase’s local file foundation and planned app-data services with AgentFS’s portable SQLite filesystem, isolation and optional Cloud sync.

FOLDERBASE / CONCEPT ILLUSTRATIONFOLDERBASE ANATOMY

ORDINARY FILES / AUTHORITATIVE

Wproduct-brief.docxdocument

Parchitecture.pdfsource

Xforecast.xlsxdataset

Ihero-final.pngasset

ENGINE-MANAGED LAYER.folderbase/

IDENTITYVERSIONSPOLICYPROVENANCEQUERIESRELATIONSHIPS

USE THE RIGHT LAYER

Different jobs, different tools.

FOLDERBASE IS BEST FOR

Durable human-agent workspaces

Evaluating local file workflows where apps, people and agents need ordinary paths, guarded edits and recovery. Application schemas and hosted collaboration are planned.

AGENTFS IS BEST FOR

Its primary job

Isolated, resumable agent execution where the session filesystem is stored in a portable SQLite file.

SIDE-BY-SIDE

Architecture comparison.

Dimension	Folderbase	AgentFS
Primary job	Local file foundation; shared application contract planned	Safe execution filesystem for an agent session
Authoritative data	Ordinary files in the user's Folderbase	SQLite-backed virtual filesystem/session
Human workspace	Designed for people and agents using the same files	Designed primarily to isolate agent tool execution
Sharing	Hosted reader/editor access and durable sync are planned	Portable SQLite database; optional Turso Cloud sync
Safe changes	Change Sets; added-file apply is broken in released 0.7.2 and fixed in a tested unreleased candidate	Copy-on-write isolation, audit, diff, and apply

ANALYSIS

Choose the data model and current capabilities

AgentFS offers isolation, recorded file operations and portable state. Folderbase starts with native files that an existing app or editor can use directly. Both need to be evaluated against the actual workflow; persistent storage alone is not a unique Folderbase capability.

A remote agent could eventually use an AgentFS-style sandbox while working on a version-pinned Folderbase checkout. The sandbox would protect execution; Folderbase would remain the authoritative database and publication boundary.

Choose based on the layer you are building

Evaluate AgentFS for an isolated agent filesystem and its documented sync option. Evaluate Folderbase’s local foundation when native file access matters. If you need a deployed record database or shared synchronization today, Folderbase’s planned services do not yet fulfill that requirement.

SOURCES

Primary references.

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.

AgentFS official product overview ↗Folderbase open-source Core ↗

The database is the folder.

Inspect the open Core and decide whether a Folderbase belongs in your agent architecture.

Explore open-source Core Discuss the Cloud pilot