uplint.
Start building
AB About Uplint

The file layer
that outlives the cloud.

Uplint is the control plane for files: one API that gives every file a stable identity, routes it to the storage your policy chooses, serves it anywhere, and moves it later without changing a link. Built by a small, bootstrapped, engineer-led team — because files outlive the infrastructure that stored them.

See the platform Join the team
Founded 2025 Bootstrapped Remote-first Uplint by Vyana
01 Why we exist

Storage should be
a setting, not a project.

Every product has files. Almost none has a plan for where those files live in five years. We started Uplint because we had run that migration project too many times ourselves.

THE PROBLEM

Files outlive everything

Frameworks get rewritten, vendors get replaced, regions get added, teams turn over. The files uploaded in year one are still being served in year seven — by whoever inherited the bucket.

THE COST

Migrations are where products stall

Every storage change becomes a project: re-plumb uploads, rewrite URLs, dual-write, backfill, hope. Most teams put it off until a residency requirement, a price hike or an outage forces it.

OUR BET

Build the layer that does not move

Give every file a stable identity and a policy that decides where it lives. Then storage becomes a setting you change, not a system you migrate. That is the whole company.

02 What we believe

Four principles,
held in public.

A principle is only worth something if you can check it. Each one ends with the pages that prove it.

  1. 01OPEN

    Open by design

    Show the work, don’t ask for trust.

    Public pricing, a public status page with incident history, open SDKs, legal documents you can read, and a security page that states the worst case plainly.

    Check itPricing Status Security Terms
  2. 02OWN

    You own the bytes

    We hold the record, never the files.

    Objects live in buckets you control under credentials you can revoke. Upload bodies stream through and are not retained; reads never pass through us. Leaving is a config change.

    Check itSecurity Privacy Platform
  3. 03LESS

    Do more with less

    Five endpoints, kept to five.

    One API instead of a storage project. One policy edit instead of a migration. Four clouds behind the same call, and residency as a routing rule on every plan.

    Check itPlatform Docs Regulated
  4. 04SHIP

    Ship, then listen

    Useful this month, written up honestly.

    Something useful this month beats something perfect next year. Every release is written up — sharp edges included — and support is answered by the engineers who built it.

    Check itDispatches Contact
03 How we operate

Uplint by Vyana.
Small on purpose.

The facts about the company, and what each one means when something goes wrong — which is when it matters.

WHAT THAT MEANS FOR YOU

Growth is paced by revenue, not by a raise.

No board deck to grow into. Prices stay honest because customers are the only people we have to keep.

The engineer who built it answers the ticket.

A dozen people means no tier one. The person who wrote the code hears what it did to your afternoon, and fixes it.

If we vanished tomorrow, your files would not notice.

They are in your buckets under your credentials. The record exports in open formats. The terms promise 90 days notice and refunds anyway.

04 The story so far

Built in public,
one dispatch at a time.

Every milestone links to the post we wrote when it shipped. Dates are the real ones.

Feb 2026

Uplint introduced

One API for files, with a rule from day one: the bytes land in a bucket you own.

Read the dispatch Apr 2026

The upload security guides

Long-form writing on upload pipelines, OWASP controls and the cost of doing nothing.

Read the dispatch Jul 2026

One API, many buckets

Route each storage target to its own bucket, region and credentials, with a default fallback.

Read the dispatch Aug 2026

Azure and Google Cloud

Bring your own bucket now covers S3, Azure Blob and GCS — and R2 through the S3 API.

Read the dispatch
Now

Build once. Store anywhere.

Identity, routing, delivery, movement and audit — one control plane for any object store.

See the platform
05 Commitments

What we will always do,
and never do.

Written here so you can hold us to it. Most of these are also in the terms, the privacy policy or the DPA.

Always

  • Publish prices, limits and reply targets before you talk to sales
  • Post every incident on the status page with a timeline
  • Keep file bytes in storage you own — never on Uplint
  • Tell you 30 days before a material change to terms, prices or sub-processors
  • Give 90 days notice and refunds if we ever discontinue the service

Never

  • Read, scan or train on the contents of your files
  • Sell or share your data with advertisers or brokers
  • Claim a certification we do not hold
  • Lock your files behind our API — the objects stay reachable in your bucket
  • Quietly change what a plan includes
SecurityHow we hold the record, not the filesTermsUptime, refunds, the discontinuation promisePrivacyWhat we collect, and what we never touchStatusLive, with incident history
06 In our own words

The latest
from Dispatches.

How we think about files, storage and the trade-offs in between — in long form, with our name on it.

1 Aug 2026Bring Your Own Bucket, Now on Azure Too1 Aug 2026Three Clouds, One API: Uplint Now Stores Files in Google Cloud13 Jul 2026One API, Many Buckets: Route Every File Context to Its Own S310 Apr 2026What Is a File Trust Layer? (And Why Your App Needs One)
All dispatches
07 Questions

The ones people ask before they trust us.

Uplint is built by Vyana Compute, a small engineer-led company founded in 2025. The same team designs, ships, supports and writes about the product, and every inbox on the contact page is read by one of us.

ONE API. ANY BUCKET.

Build once.
Store anywhere.

Start free, connect a bucket you already own, and never run a storage migration project again.

Start building free Talk to us