No raw storage path ever escapes.
First-party cloud storage
Files the platform actually owns.
Weke Drive is not a white-labelled third-party drive with a logo swapped in. It is Weke's own storage service: Weke ID proves who you are, Drive decides what you may touch, and the object store behind it is never something a browser or a share link can reach directly.
The storage frame
Bytes in the store, meaning in the database.
File contents live in object storage; names, folders, versions, permissions, and audit lines live in the database. Keeping them apart is what makes a version immutable, a rename cheap, and a download something Drive has to grant rather than something a URL leaks.
Coverage
Three jobs, one file tree.
Keep the bytes safely, hand them to the right people, and be able to prove who did what.
Drives & versions
A personal root and an organization root, resumable uploads, and version manifests that are immutable once a version completes.
Sharing & links
Share with a Weke user or a group, or mint an external link that resolves through Drive — expirable, disableable, and able to forbid downloads outright.
Quota & audit
Usage against quota for the organization, a switch to disable external sharing entirely, and an audit event behind every sensitive action.
How a file moves
Sign in, authorize, serve.
The same three gates stand behind every download, preview, and share — including the ones opened by someone who has never had a Weke account.
- 01 — Weke ID signs you in
- 02 — Drive authorizes the action
- 03 — Drive serves the bytes