Explore the platform
Upload, download, encrypt and convert files across S3, Azure Blob, GCS, Google Drive and OneDrive through one configurable interface. AES-at-rest with per-project keys — and Excel and CSV decode to JSON on the way in.
Every cloud's storage SDK is just different enough to be annoying — different auth, different error semantics, different conventions. eru-files wraps S3, Azure Blob, GCS, Google Drive and OneDrive in one API: same upload, same download, same encryption story.
Pivot from AWS to Azure with a JSON config, not a sprint. AES-at-rest is transparent on both ends, MIME sniffing keeps uploads honest, and Excel, CSV and ZIP decode without a separate service.
AWS S3, Azure Blob, GCS, Google Drive and OneDrive — one API, one set of error semantics.
Per-project AES keys. Transparent on upload and download — never written into application code.
Upload a workbook, get back rows of JSON — with header-row detection and type inference.
Auto-detected headers, parsed types, ready for queries. No preprocessing service needed.
Upload an archive, fetch a single file or list its contents — without unpacking client-side.
Type detection prevents masquerading uploads. Per-MIME size limits enforce your policy.
Multi-file upload and download with folder-templated paths and configurable concurrency.
Collision-free naming with document ID tracking per project and storage backend.
AWS IAM roles, Azure managed identity, GCP service accounts — credentials managed for you.
One upload flows through the files API, gets AES-encrypted, hits a storage driver and lands in your cloud of choice — the same call whether it's S3 or OneDrive.
No SDK lock-in. Swap clouds, buckets, encryption or MIME policy by editing config.
// AWS S3 object storage — configured through eru-files { "storage_type": "AWS", "storage_name": "user-uploads", "encrypt_files": true, "region": "ap-south-1", "bucket_name": "eru-prod-user-uploads", "authentication": "iam-role" }
