Ordinary files. Useful application data.
Your app’s data should be easy to use, safe to change, and yours to keep.
Start with JSON, Markdown and attachments in a local folder. We are building one data contract for your apps and agents—locally, deployed and shared.
Core 0.7.2 beta · No account needed · Cloud in development
Illustrative data layout. Local file Core is available; the shared application contract and Cloud are in development.
Three use cases
Local files are the starting point
Your app already keeps data in files. Every new project rebuilds parsing, validation, queries and safe updates.
For exampleA small app with JSON tasks, Markdown notes and original PDF attachments.
A shared record schema and field queries are the next step; they are not in the released Core yet.
A deployed app needs its data to survive restarts and stay consistent across application instances.
For exampleTwo app instances read and update the same customer brief after either instance restarts.
The goal is one shared data contract and a durable remote API. Hosted database access is not available yet.
A teammate, an agent and another device need the same work without silently replacing each other’s edits.
For exampleA teammate edits a note while an agent works offline, then both changes return for resolution.
Reader/editor access and explicit synchronization are planned. The local preview does not provide a shared sync service.
Released Core 0.7.2 provides the local file foundation. The tested local development candidate includes creation, guarded edits, history and export/restore; it is not a published release.
One useful loop
The standard we are building toward
A folder, a collection’s schema, a record and its revision. The local SDK path should need no desktop app or Cloud account.
The next application contract should replace repeated parsing, validation and query glue. Today, the reference app still owns that code.
The tested local app handles competing edits and recovery within its documented writer limits. Clear errors and retry steps matter as much as a successful save.
A first project should make the next one easier. We will measure independent integrations, useful work completed and repeat use.
Try the local format
Node.js 22.14+ · macOS or Linux
From a folder you want to try, inspect it and preview the additions. These two commands do not change the folder.
npx --yes @folderbase/cli@0.7.2 inspect . --json
npx --yes @folderbase/cli@0.7.2 init . --dry-run --jsonThe full quickstart explains how to apply the reviewed plan, validate the workspace, and list its files. Local initialization does not connect or upload to Cloud.
Core & Cloud
A useful local start. An optional managed service.
Free
Open-source CLI and workspace format. Inspect, initialize, validate, and explore the documented capabilities on your machine.
Let’s talk
For developers whose deployed apps need shared, durable data. We are validating the remote service, access controls and synchronization path.
Opens an email to the founder. No checkout or subscription yet. Pricing and limits will be stated before any paid offer.
Practical guides
Build the workflow with the right storage
A recurring report example, a continuity manifest, and a practical test for the next run.
Read guideCompare the base, proposed result, and current files. Catch stale work before accepting it.
Read guideA decision guide to folders, Git, persistent volumes, AgentFS, checkpoints, and memory.
Read guideDirect answers
Folderbase is an open workspace format and local database Core for an agent’s real files. It adds a .folderbase layer while keeping documents, PDFs, code, and other files at ordinary paths.
Yes. Local Core is free, open source under Apache-2.0, and works without a Folderbase account. The quickstart shows inspection, a preview of initialization, and validation.
Cloud is a pilot invitation. The intended service will provide durable data for deployed apps, followed by shared access and explicit sync. Public self-serve Cloud and a paid plan are not available yet.
Bring your existing agent and runtime. Folderbase focuses on the files and their lifecycle. Hosted agent compute is outside the current MVP.
Core 0.7.2 has a known issue applying Change Sets that add files. Start with the local initialization quickstart and check issue #78 before relying on a complete agent write-back workflow.
Local initialization leaves your existing files at ordinary paths, usable in their native tools. They do not depend on a Cloud subscription. A tested, unreleased candidate supports export and restore with retained file history. Check the exact capabilities and limits of your chosen release.
Storage for agents
Try the local file foundation. Tell us what your app needs from deployed data, sharing or sync.