Core Concepts

This page explains the key ideas behind Hyperfile.

Accounts

An account is your identity on Hyperfile. Each account has an email address, profile, and a set of team members and roles.

Filesystems

A filesystem is a collection of files and folders. Each filesystem:

• Has its own root directory
• Lives in a specific region (US or EU)
• Has independent permissions and settings
• Tracks version history for all files

You can create as many filesystems as your plan allows.

Files and Folders

Files in Hyperfile are content-addressed — each file version is identified by its SHA-256 hash. This means:

• Duplicate files are stored only once
• Uploads are fast because unchanged files are skipped
• Version history is efficient

Folders are organizational containers. They can be nested to any depth.

Permissions

Hyperfile uses role-based access control:

• Owner — Full control, including billing and member management
• Admin — Manage filesystems and members, but not billing
• Member — Upload, download, and manage files

Sync

The CLI sync engine compares your local file tree with the remote and transfers only the differences. This makes syncing fast even for large directories.

API Keys

API keys provide programmatic access to Hyperfile. Each key inherits the permissions of the account that created it.