Question 1

What does multi-tenant mean in FyreStorage?

Accepted Answer

A single deployment serves every customer. Branding, feature switches and theme are declarative configuration per tenant, so adding a customer never means forking the codebase.

Question 2

Where is the data stored?

Accepted Answer

Objects live in Amazon S3 and metadata is indexed alongside them, both inside your own cloud account. Licensing covers the host shell, the plugin engine and the theming system, not the infrastructure.

Question 3

How are features added without redeploying the whole app?

Accepted Answer

Every feature beyond core browsing is an independently built and deployed micro-frontend. The host loads it at runtime from a signed registry and hands it a capability-scoped SDK, so a plugin only reaches what it declared.

Question 4

Is file access private between users?

Accepted Answer

User separation in the current release is enforced by the application layer and the sharing gatekeeper, not by per-user storage credentials. FyreStorage is not marketed as zero-knowledge storage. The architecture is laid out so tightening to credential-enforced prefixes needs no application rewrite.

Question 5

Can a shared link be revoked after it is sent?

Accepted Answer

Yes. Shares carry policy: hashed tokens, optional passwords, expiry dates, download caps and instant revocation, with an access log recording who opened what.

Create your account