Built for the text you return to.

Most cloud storage is designed to keep everything. Kilobytes of notes sit next to gigabytes of video, pushed through the same pipe, priced by the same meter. Somewhere in that pile, your plain-text files — the ones you actually open every day — get exactly the same treatment as everything else.

fpod was built on a different bet: that notes, configs, and snippets deserve infrastructure designed for them alone. Not a smaller cloud drive. A sync pipeline with one job — moving your text between your devices, quietly, reliably, and encrypted by default.

A deliberate boundary

The fpod text vault is fixed at 32 MB. It isn't a starter tier, and it never grows. It's a boundary — calibrated for what you return to, not for hoarding everything.

In plain-text terms, 32 MB is a large space: years of markdown notes, dotfiles, lexicons, and journal entries / cheat sheets, all with room to spare. If your vault ever pushes against the edge, the boundary is doing its job — keeping this place focused on the text that earns it.

Images live in a separate companion space, so photos never crowd out your words.

A pipeline, not a platform

fpod doesn't try to be your editor. It doesn't organize or present your notes. It doesn't try to become your second brain, and it doesn't want more of your attention. It stays in the background — standard protocols (WebDAV, SFTP, S3), encryption at rest by default, client-side encrypted files in /fvault, and a one-click export that hands you everything as plain files.

Your sync layer should be boring. That's the point.

What fpod will never do

No ads, no content analytics. Your notes are a sync payload, not a data source.

No feature tiers. One plan. Everything included, for everyone.

No proprietary formats. Your files remain standard text, on our servers and in your exports.

No holding your data. If your subscription ends, your vault becomes read-only — never deleted, always exportable.