Who this comparison is for
File-Vault highlights
- One workspace connection used by every app (unified picker/API)
- Expiring external links + one‑click revoke with full audit
- DLP & antivirus gates on upload with override/audit
Google Drive (Workspace) highlights
- Native collaboration, powerful search, and previews
- Shared Drives and labels for governance
Capability matrix
| Capability | File-Vault | Google Drive (Workspace) | Notes |
|---|---|---|---|
| Unified picker across all workspace apps | Native | None | Per‑app builds otherwise required |
| One connection reused by many apps | Native | None | Drive OAuth typically repeated per app |
| Expiring external link + revoke audit | Native | Partial | Drive supports links; cross‑app audit via File-Vault |
| DLP & antivirus on upload (block until cleared) | Native | Partial | Drive malware flags exist; DLP requires Enterprise/labeling |
| Retention/legal hold mapping from one UI | Native | Partial | Drive labels exist; File-Vault maps policies across apps |
| Delta sync + reconcile external moves/renames | Native | Partial | Changes API native; File-Vault reconciles attachments |
| Predictable per‑object foldering (tickets/deals) | Native | None | Convention enforced across apps |
| Cross‑provider routing (Drive + S3/R2 archive) | Native | None | Signed retrieval for archives |
| Cross‑app audit & CSV export | Native | None | Drive has activity; File-Vault centralizes per app/object |
- Matrix compares File-Vault’s cross‑app orchestration to using Google Drive directly per‑app.
- Tokens: full/partial/none/native/addon/config‑dependent.
Total cost of ownership
Using Drive directly in each app multiplies integrations and policy drift. File-Vault makes one Drive connection serve all apps with shared policies, reducing engineering and operations hours.
Assumptions
- 4–8 Velaxe apps needing Drive access
- Security requires expiring links + audit exports
Migration plan
From Google Drive (direct per‑app) · Connect once in File-Vault → swap pickers/API → backfill attachments
-
1
Connect Shared Drive or user mode; run health check
-
2
Replace per‑app pickers with File-Vault picker
-
3
Scan existing folders; attach live files to objects
-
4
Enable expiring links, DLP/AV, and retention mapping
Security
- Least‑privilege scopes; AES‑256 at rest, TLS 1.2+
- RBAC for share/revoke/manage; full audit trail
Evidence & sources
| Claim | Value | Source |
|---|---|---|
| Delta reconciliation | Keeps attachments intact after external moves/renames | product_docs |
| Expiring links | Create and revoke with audit | product_docs |
About File-Vault
File-Vault is the multi-provider storage hub for Velaxe. Connect Google Drive, OneDrive/SharePoint, Dropbox, Box and optional S3/R2 at the workspace level, then let every app upload, attach, preview and share through a unified picker and API.
Admins set link and retention policies, enable DLP and AV scanning, choose provider scopes, and review complete audit trails. Files stay in your selected drives using predictable folder structures while File-Vault keeps metadata, attachment links and permissions synchronized.
Built for reliability and compliance: chunked uploads, resumable sessions, expiring external links, delta sync, audit exports and Prometheus-friendly health metrics.