Use the storage you choose
Keep files locally or place them in configured cloud storage without changing the record model.
Files and assets
Make files part of the record.
Model images, documents, audio, video, and other uploads alongside the data they belong to—without building a disconnected upload service.
- Asset fields
- Access checks
- Streaming
Data and bytes together
Upload, relate, and deliver.
Daptin asset columns connect file metadata and storage to application records. The same product model can govern the file, its owner, and the API that returns it.
Stream and cache downloads
ETags, conditional responses, bounded reads, and streaming support real file-serving workloads.
Keep uploads within the application
File operations pass through Daptin’s record and access paths instead of a parallel anonymous bucket API.
Build media-rich products
Use assets for profiles, catalogues, documents, attachments, learning material, or managed downloads.
Product uses
Keep the file attached to the thing it describes.
Profiles and catalogues
Attach avatars, product photographs, downloadable specifications, and galleries to the records already governing them.
Documents and learning
Store reports, source material, submissions, course assets, and media alongside ownership and application metadata.
Audio and video
Serve media with byte-range support so compatible players can seek without downloading the entire object first.
Large uploads
Use streaming paths and S3 multipart handling instead of requiring the application server to buffer every upload in memory.
Delivery engineering
Authorization happens before cached bytes leave the server.
The asset route resolves the owning record and checks table visibility plus row read permission. ETags and conditional responses reduce repeat transfer; bounded caching keeps large files out of an unbounded memory read; compressible responses negotiate gzip without breaking range requests.
Storage durability, retention, malware scanning, and moderation remain deployment choices. Test sensitive assets through allowed, denied, cached, and uncached paths using the exact schema.
See the asset verification checklist →