Questions about the gate

Why doesn't Filarr serve the API itself?

Because it cannot read your databases: they are encrypted end to end, and only your devices hold the key. Serving an API means decrypting. The gate does it on your side, with a key you give it for the chosen databases only: Filarr keeps seeing encrypted blocks only.

Does the gate see my whole account?

No. The token opens only the access's databases. It gives neither your notes, nor your files, nor your vaults, nor your other databases, nor your account's keys. A database linked to a closed one only gives raw ids.

What about my views? If I open a view "Active customers", does the gate only see those customers?

No: the gate reads the whole database, all its rows and all its columns. Views are a convenience (ready-made addresses), not a boundary. To share less, open a database that holds less. On the software side, an app key can be limited to one view.

What does Filarr see of my API?

The access, the token's fingerprint, keys and views sealed so that it cannot open them, counters (sync requests, downloaded volume, accepted commits), the gate's IP address and version. Never the token, a database key or a row. The reads the gate serves to your software do not go through Filarr.

A token leaked: what is at risk?

Whoever holds it reads the access's databases until you revoke it. Revoke the access in Settings → API access: the token is refused at once, and the databases' keys change, so that the old token cannot read anything written afterwards, even if encrypted blocks leaked. Replacing the token is enough when you want to keep the access and nothing leaked; it does not change the keys.

After a revocation, does the gate's copy disappear?

A gate that is online erases its copy and its keys within a second. An offline gate learns it at its next connection; until then, it keeps what it already copied. If the machine is no longer trusted, erase the copy there (in its management UI: Settings → Forget this machine).

Does it count against my plan?

Only what goes through Filarr is counted: the gate's sync requests, the volume it downloads, its accepted commits. The reads it serves to your software, never. The figures of each plan are on the pricing page and in Settings → API access (plans).

Can I open a database of a shared vault?

Yes, if you are the vault's owner or an admin. The gate then reads that database like any other; the vault's members keep working in it as usual.

Can I create an access from my phone?

No: creating one is done from the desktop app or the web, where the mobile app sends you.

Where is the technical documentation?

In the gate's public repository, with step-by-step tutorials and complete examples: github.com/filarr-work/filarr-gate.