Cloud Drive

Internal file operations with cleaner control.

A refined Next.js 16 foundation for secure uploads, predictable sharing, recovery workflows, and audit-ready admin surfaces.

Open workspace Review readiness endpoint

Server-rendered routes with static metadata, sitemap, robots, manifest, and a health endpoint.
Strict TypeScript, typed routes, hardened response headers, and env scaffolding aligned to the spec.
A light-first product shell built for dashboard, files, deleted items, shared links, and admin workflows.
No unnecessary infrastructure additions: no Redis, no Docker boilerplate, no ornamental dependency sprawl.

Workspace control plane

Uploads, visibility, audit, and recovery

Ready for auth + storage wiring

Current folders

Finance / Q2 planning

Workspace visibility with audit trail

Synced

Contracts / Vendor renewals

Workspace visibility with audit trail

Synced

Operations / Regional playbooks

Workspace visibility with audit trail

Synced

Signed upload URL issued for pricing-model-v7.xlsx

Public view link revoked by admin policy

Deleted folder restored inside retention window

Product shape

The UI starts from the operating model, not a template.

Each surface maps to a real requirement from the spec: uploads, visibility, recovery, and admin oversight.

Direct uploads, controlled access

Large files move straight to storage through signed upload flows while permission checks stay in the app layer where they belong.

Folders that stay understandable

Nested hierarchy, breadcrumbs, deleted-item recovery, and visibility states are designed into the workspace from the first pass.

Sharing with limits

Workspace access, public view links, download controls, expiry windows, and revoke paths are represented in the product surface up front.

Critical path

The upload lifecycle is already modeled around safe defaults.

The product shell and supporting utilities are prepared for the signed URL flow described in the spec.

Request signed upload session

Metadata is registered before bytes move so the system can track status, size limits, and owner context from the start.

Stream file directly to storage

The browser talks to the object store through short-lived credentials instead of routing large payloads through the app server.

Verify, activate, and audit

Completion updates state, makes the record visible, and creates an auditable event trail for recovery and review.

Production baseline

The starter is ready for real integrations, not a rewrite.

Next steps can layer Better Auth, Neon, Drizzle, Backblaze B2, Resend, and Sentry into the structure already in place.

View file index Inspect admin surface

Loading workspace

Cloud DriveInternal file ops

Cloud Drive

Internal file operations with cleaner control.

A refined Next.js 16 foundation for secure uploads, predictable sharing, recovery workflows, and audit-ready admin surfaces.

Open workspace Review readiness endpoint

Server-rendered routes with static metadata, sitemap, robots, manifest, and a health endpoint.
Strict TypeScript, typed routes, hardened response headers, and env scaffolding aligned to the spec.
A light-first product shell built for dashboard, files, deleted items, shared links, and admin workflows.
No unnecessary infrastructure additions: no Redis, no Docker boilerplate, no ornamental dependency sprawl.

Workspace control plane

Uploads, visibility, audit, and recovery

Ready for auth + storage wiring

Current folders

Finance / Q2 planning

Workspace visibility with audit trail

Synced

Contracts / Vendor renewals

Workspace visibility with audit trail

Synced

Operations / Regional playbooks

Workspace visibility with audit trail

Synced

Signed upload URL issued for pricing-model-v7.xlsx

Public view link revoked by admin policy

Deleted folder restored inside retention window

Product shape

The UI starts from the operating model, not a template.

Each surface maps to a real requirement from the spec: uploads, visibility, recovery, and admin oversight.

Direct uploads, controlled access

Large files move straight to storage through signed upload flows while permission checks stay in the app layer where they belong.

Folders that stay understandable

Nested hierarchy, breadcrumbs, deleted-item recovery, and visibility states are designed into the workspace from the first pass.

Sharing with limits

Workspace access, public view links, download controls, expiry windows, and revoke paths are represented in the product surface up front.

Critical path

The upload lifecycle is already modeled around safe defaults.

The product shell and supporting utilities are prepared for the signed URL flow described in the spec.

Request signed upload session

Metadata is registered before bytes move so the system can track status, size limits, and owner context from the start.

Stream file directly to storage

The browser talks to the object store through short-lived credentials instead of routing large payloads through the app server.

Verify, activate, and audit

Completion updates state, makes the record visible, and creates an auditable event trail for recovery and review.

Production baseline

The starter is ready for real integrations, not a rewrite.

Next steps can layer Better Auth, Neon, Drizzle, Backblaze B2, Resend, and Sentry into the structure already in place.

View file index Inspect admin surface