Dropbox agrees to pay about $350 million for Tigris Data to reach AI builders

Dropbox has agreed to pay about $350 million in cash for object-storage startup Tigris Data. What Tigris built, why Dropbox wants it and what its customers should check now.

FluxOrbit4 min read

Dropbox has agreed to buy Tigris Data, a startup that sells globally distributed object storage, for about $350 million in cash. The agreement was signed on 3 November and announced on 5 November, alongside a new Dropbox infrastructure product called DBX Agent Cloud.

The price is not a leak. It comes from Dropbox's own filing with the US Securities and Exchange Commission, which gives approximately $350 million before the usual price adjustments and expects closing in the fourth quarter of 2026. The announcement itself and Tigris's blog post mention no figure. StorageReview noted on 8 November that the deal had not closed. Until a closing is announced, this is an agreement, not a completed purchase.

Tigris's customers, and the customers of platforms built on it, now have a new owner to assess.

What Tigris built

Tigris sells object storage: buckets of files that applications read and write through the same API as Amazon S3. The company says it supports over 90% of that API, so tools and libraries written for S3 work against it. Four things define the product, all by the company's own account:

  • Placement. By default a bucket is of the Global type. Tigris decides where the data sits and shifts it towards wherever it is being read, behind one endpoint.
  • No egress fees. There is no charge for moving data out, whether to another region or to the internet.
  • Bucket forks. Instant clones of a bucket that copy no data, so each AI agent or experiment can have its own version.
  • Its own hardware. Tigris says it runs on its own infrastructure, not on a large cloud.

Its founders, the company says, previously built Uber's storage platform. It began with a database product and switched to object storage in 2024, according to its documentation. It raised a $25 million Series A led by Spark Capital in October 2025, and names AI companies such as fal and Krea as customers.

It also sits underneath other platforms. Railway's documentation names Tigris's servers as the hardware under its storage buckets. Fly.io's lists Tigris as the object storage built into its platform and bills for buckets created through a Fly account.

Why a file-sync company wants it

Dropbox published third-quarter results on the day of the announcement: revenue of $637.3 million, up 0.5% on the third quarter of 2025. In that release its co-chief executive presented selling storage infrastructure to companies building AI applications as a new source of growth, drawing on infrastructure the company has built over nearly two decades.

DBX Agent Cloud is the vehicle, aimed at companies and developers who build AI applications and agents. The first piece is S3-compatible object storage that can be bought on its own. Filesystem and content-processing features come next, with no dates given.

The pitch is the one Tigris made when it raised money: AI teams move between compute providers, and their data should follow without a toll.

Our reading is that Dropbox is buying time. It says it knows how to run storage at scale. Tigris adds a working developer product with customers already on it.

What has been promised, and what has not

Tigris's post tells customers that the product, the S3-compatible API, the price list with its free egress, the team and the support channels all stay as they are. Dropbox told TechCrunch it has no current plans to cut headcount as part of the deal.

The post sets no end date on those terms and does not say what happens after closing, only that customers will be kept informed. StorageReview's report says Dropbox has yet to say what DBX Agent Cloud's object storage will cost, whether egress will be charged or when it will be available.

Free egress is the promise we would watch, because it is what keeps leaving cheap.

What we would check

None of this is a reason to move. In our view a provider owned by Dropbox may be a safer home than a startup a year past its Series A. But a change of owner is the moment to check your exit while the old terms still apply. Our advice to a team with data at a provider in this position:

  • Find out whether you are a customer at all. If your buckets came from a hosting platform, ask what runs underneath.
  • Rehearse the exit while egress is free. Copy everything to a second S3-compatible store and run the application against it. Then list what you use beyond plain reads and writes, such as forks or global placement, and check for an equivalent.
  • Know where the data lives. Tigris's documentation says Global buckets are "not suitable for strict data residency requirements", while single-region buckets keep object data inside the region you pick. The same page adds that object keys and system metadata are copied to every region. If a contract or regulator cares, check every bucket and ask about metadata.
  • Read the contract. Look for assignment to a new owner, notice of price changes, and how long you can retrieve data after termination. Ask in writing whether any of it changes at closing.

After that we would watch two things: the closing, and the first DBX Agent Cloud price list. If egress is still free on it, the promise has held where it matters.

Building something that has to stay up and stay safe?

We design, build and look after software for teams that cannot afford surprises.

WhatsApp