TigerFS is a new experimental filesystem that mounts a database as a directory and stores files directly in PostgreSQL. The open source project exposes database data through a standard filesystem interface, allowing developers and AI agents to interact with it using common Unix tools such as ls, cat, find, and grep, rather than via APIs or SDKs.
TigerFS aims to address the lack of shared, reliable state for agents by combining the simplicity of a filesystem with the transactional guarantees and structure of a database. Released under an MIT license, TigerFS supports two usage models: file-first and data-first.
In a file-first workflow, developers organise files such as Markdown documents in directories, with atomic writes and automatic versioning. This allows existing tools such as editors and command-line utilities to work with the files without modification, while also enabling concurrent access and simple coordination by moving files between directories to represent task states such as todo, doing, and done. Michael Freedman, TigerData co-founder and CTO and the creator of the project, explains the goal on LinkedIn:
Agents don’t need fancy APIs or SDKs, they love the file system. ls, cat, find, grep. Pipelined UNIX tools. So I made files transactional and concurrent by backing them with a real database.
In a data-first workflow, users mount an existing PostgreSQL database and explore its data using standard Unix tools. Filesystem paths can include filters and sorting that translate into database queries, allowing users to retrieve or export data without writing SQL. Freedman adds:
Every file is a real PostgreSQL row. Multiple agents and humans read and write concurrently with full ACID guarantees. The filesystem /is/ the API (…) I built this mostly for agent workflows, but curious what else people would use it for. It’s early but the core is solid.
Franck Pachot, developer advocate at MongoDB and AWS Data Hero, recalls the Oracle “Internet Filesystem Option” and comments:
I love this – mounting a database as a filesystem. It recalls the excitement of the early Y2K internet era. The idea was so disruptive that the dot in Oracle 8.1 jumped onto the “1” to become an “i”.
According to the documentation, TigerFS mounts via FUSE on Linux and via NFS on macOS, and can connect to an existing PostgreSQL instance or a managed service. Each file corresponds to a database row, providing transactional guarantees and concurrent access while allowing tools such as Claude Code and Cursor to interact with data through a traditional filesystem model. To achieve that, TigerFS adds special dot-prefixed directories, such as .build, .info, and .export, to each directory.
On Hacker News, most developers are curious about the limitations and the performance implications, with user iamcalledrob writing:
Super interesting. I love to see more stuff built on top of filesystem APIs. I wonder what the performance characteristics are? I’m assuming this is going to work well for small datasets that fit in memory, and probably less well beyond that. So good for config, context, etc.
User bjornroberg adds:
Really nice concept. I like the idea of using file system primitives to interact with structured data.
TigerFS works with any PostgreSQL database and mounts via FUSE on Linux and via NFS on macOS, without external dependencies.
