Without Uplint4 integrations
File infrastructure for developers Generally available
Build once.
Store anywhere.
One API to upload, manage, serve, and move files across any object store. Keep your application portable—and your data in infrastructure you own.
Bring your own storage One stable file identity No credit card
Stable file identity Storage routing
01 Application request
upload.tsTypeScript
const file = await uplint.files.upload({file,storage: "production",metadata: {customer: "cus_72m"}});02 Uplint control plane
uUplintfile_8Kx92m
authorize route metadata File identity created37 ms
03 Storage destination
S3AWS S3company-files / productionRouting
AZAzure BlobReady to connect＋
GCGoogle CloudReady to connect＋
R2Cloudflare R2Ready to connect＋
Native connections to the clouds you already use
- S3AWS S3
- AZAzure Blob
- GCGoogle Cloud
- R2Cloudflare R2
- ＋S3-compatible
Infrastructure, simplified
Put a clean file interface between product code and an increasingly complicated storage world.
Unified surfaceOne API.
Every upload, retrieval, delivery, move, and deletion.
Portable by designAny cloud.
Route files by provider, tenant, region, or policy.
Ownership intactYour storage.
Your buckets, security boundaries, and infrastructure.
01 The missing infrastructure layer
Your storage can change.
Your product doesn't.
File uploads are easy until your product needs another cloud, another region, or a customer-owned bucket. Uplint gives every object store one interface.
With Uplint1 integration
Change the configuration. Keep the code.
02 Platform primitives
The control plane
for every file.
Your application knows the file. Uplint handles the provider, region, credentials, routing, and movement underneath.
- 01STABLE IDENTITY
Reference the file.
Not the bucket.A durable file ID keeps application references stable—even when the object moves between providers.
- 02BRING YOUR OWN STORAGE
Your storage.
Your data.Keep files inside infrastructure and security boundaries you already control.
- 03POLICY ROUTING
Different customers.
Different clouds.Route each tenant to the provider, bucket, and region their requirements demand.
- 04ONE FILE API
Five primitives.
No vendor surface area.A small, predictable API for the operations your product actually needs.
03 Portability by default
Switch providers.
Don't touch your code.
Select a destination below. The infrastructure configuration changes instantly; the application call stays exactly the same.
const file = await uplint.files.upload({file,storage: "production"});// This code never changes. No application changes
S3
AWS S3Connected · Healthy
Live{"provider": "s3","bucket": "company-files","region": "ap-south-1"}Configuration updatedjust now
04 Built for real architectures
One file layer.
Many requirements.
Start simple, then add regions, providers, and customer-owned storage without rebuilding your product.
SAAS01
Product teams
Ship a complete file layer without turning every cloud decision into product code.
Explore use caseB2B02
Multi-tenant platforms
Give each customer the bucket, provider, or region their policy requires.
Explore use caseAI03
AI applications
Handle documents, datasets, images, audio, and generated artifacts consistently.
Explore use caseENT04
Regulated software
Keep data in approved regions or customer-owned storage with one interface.
Explore use case05 Ship your first file
From zero to uploaded
in one request.
Connect a bucket, create an API key, and keep every future storage decision out of your application code.
Read the five-minute quickstart$ npm install @uplint/node✓ added @uplint/node$ uplint storage connect production✓ AWS S3 connected bucket: company-files region: ap-south-1▋YOUR FILE LAYER, DECOUPLEDOne API for your files.
One API for your files.
Any storage underneath.
Make your application portable before the next storage decision makes it permanent.