Omnidrive lets you connect multiple Google Drive accounts and manage all your files from a single dashboard. It runs entirely on Cloudflare's edge network — Workers for the API, D1 for the database, and KV for session storage — so there's no traditional server to maintain.
Omnidrive lets you connect multiple Google Drive accounts and manage all your files from a single dashboard. It runs entirely on Cloudflare's edge network — Workers for the API, D1 for the database, and KV for session storage — so there's no traditional server to maintain.
Unified multi-Google Drive storage gateway built on Cloudflare Workers.
🌐 Baca dalam Bahasa Indonesia
Omnidrive lets you connect multiple Google Drive accounts and manage all your files from a single dashboard. It runs entirely on Cloudflare's edge network — Workers for the API, D1 for the database, and KV for session storage — so there's no traditional server to maintain.
next_page_token, atomic upserts for performance, and graceful shutdown (SIGTERM) to prevent concurrent syncs.Omnidrive implements a robust security model to protect your files and data:
Omnidrive exposes an S3-compatible Object Storage API. Any S3 client (rclone, aws-cli, boto3, AWS SDK) can connect to it using path-style access.
How it works:
Endpoint: https://<your-worker-url>/s3
rclone configuration example:
[omnidrive]
type = s3
provider = Other
access_key_id = OMNI...
secret_access_key = ...
endpoint = https://<your-worker-url>/s3
force_path_style = true
Supported operations: ListBuckets, ListObjectsV2, GetObject, PutObject (single-part), HeadObject, DeleteObject, and full Multipart Upload (Initiate, UploadPart, CompleteMultipartUpload, AbortMultipartUpload).
| Layer | Technology |
|---|---|
| Backend | Hono on Cloudflare Workers |
| Database | Cloudflare D1 (SQLite) |
| Session Store | Cloudflare KV |
| Frontend | React 19 + Vite |
| State Management | Zustand |
| Language | TypeScript |
| Auth | Google OAuth 2.0 |
omnidrive/
├── packages/
│ ├── worker/ # Cloudflare Worker (API backend)
│ │ ├── src/
│ │ │ ├── routes/ # API route handlers
│ │ │ ├── services/ # Business logic (Google Drive, sync, auth)
│ │ │ ├── middleware/ # Auth guard, CORS, error handling
│ │ │ ├── db/ # D1 schema
│ │ │ └── types/ # TypeScript types
│ │ └── tests/ # Vitest unit tests
│ └── web/ # React SPA (frontend)
│ └── src/
│ ├── components/ # UI components
│ ├── pages/ # Route pages
│ ├── stores/ # Zustand state stores
│ ├── hooks/ # Custom React hooks
│ ├── lib/ # API client, utilities
│ └── types/ # TypeScript types
├── docs/ # Design specs and implementation plans
├── Makefile # Deployment automation
└── package.json # Monorepo root (npm workspaces)
The backend and frontend communicate via REST API. In development, Vite's dev server proxies /api/* requests to the local Worker on port 8787.
Before running the deployment wizard, ensure you have a Google OAuth App configured:
http://localhost:8787/api/auth/google/callback as an authorized redirect URI (if running locally) or your production domain callback.Omnidrive includes a fully automated deployment wizard that configures your environment, sets up databases, and starts the application for you. You can run it directly via remote script:
curl -fsSL https://raw.githubusercontent.com/abilfida/omnidrive/main/deploy.sh | bash
(This script will automatically clone the repository if it's not present in the current directory).
Follow the prompts to select your deployment target:
npm run dev..env, exposes your selected port, and runs docker compose up -d.Or use the Cloudflare Pages dashboard for automatic deployments from your Git repo if you prefer CI/CD.
If you prefer not to use the deploy.sh script, you can deploy manually:
npx wrangler login
npx wrangler d1 create omnidrive
packages/worker/wrangler.toml with the generated database_id.npx wrangler kv:namespace create OMNIDRIVE_SESSIONS
packages/worker/wrangler.toml with the generated KV id.npm run db:migrate:remote -w packages/worker
npx wrangler secret put GOOGLE_CLIENT_ID -c packages/worker/wrangler.toml
npx wrangler secret put GOOGLE_CLIENT_SECRET -c packages/worker/wrangler.toml
npx wrangler secret put JWT_SECRET -c packages/worker/wrangler.toml
npx wrangler secret put TOKEN_ENCRYPTION_KEY -c packages/worker/wrangler.toml
npm run deploy -w packages/worker
packages/web/.env.production with your newly deployed Worker domain.npm run build -w packages/web
npx wrangler pages deploy packages/web/dist --project-name=omnidrive-web
Omnidrive uses a single centralized .env file at the root of the project to manage both Web and Worker configurations.
/.env)Copy /.env.example to /.env and fill in your values. This file is automatically read by both Vite and Wrangler during local development.
| Variable | Description | Default |
|---|---|---|
WEB_PORT |
Port for the React frontend | 8999 |
WORKER_PORT |
Port for the Cloudflare Worker API | 8888 |
FRONTEND_URL |
Frontend origin for CORS and redirects | http://localhost:8999 |
WORKER_URL |
Worker URL for OAuth callback | http://localhost:8888 |
VITE_API_URL |
Worker API base URL for the frontend | http://localhost:8888 |
GOOGLE_CLIENT_ID |
Google OAuth 2.0 Client ID | |
GOOGLE_CLIENT_SECRET |
Google OAuth 2.0 Client Secret | |
JWT_SECRET |
JWT signing key for shared links (min 32 chars) | |
TOKEN_ENCRYPTION_KEY |
AES-256-GCM key for encrypting OAuth tokens (32 chars) |
Note: For production on Cloudflare, backend secrets should be set via wrangler secret put, and non-secrets in wrangler.toml under [vars]. The frontend uses packages/web/.env.production.
MIT © 2026 abilfida