this has been addressed by the TM team before – it's apparently "not a priority" and community workarounds exist. i hope they change their mind so I can recommend TM to my friends and family.

why would I spend $10usd per month on 1gb of cloud storage when I could get other solutions like t3.chat for $8 a month, with LLM API fees included? it doesn't really make sense to me.

The 10MB storage limit, even for self-hosted instances, presents a significant hurdle to usability. It effectively eliminates the benefits of self-hosting, making it seem counterintuitive to use our own resources when we could be leveraging yours for the website itself.

While I deeply appreciate the work you've put into this and am now a lifetime subscriber, I still believe the storage limitation is a critical area for improvement. The current limit is proving to be insufficient very quickly – I'm already at 10% capacity after just a short time.

To address this, I'd be very receptive to options like:

Paid storage upgrades: A one-time fee for increased lifetime storage would be a welcome solution.

Integration with external storage services: Offering support for services like S3, NextCloud, Seafile, or even local storage would provide users with far greater flexibility and control over their data.

This limitation seems to conflict with your stated commitment to user data ownership and control, which I strongly support. Providing more robust storage options would not only enhance the user experience but also strengthen the alignment with your core values. I'm excited to see how this evolves. Thanks again for your work!

Here is a version in clear, “plain” language that you can easily place under the feature request:

I totally agree — let's choose our own storage!

Why this is important

• Price — You now charge $10 per GB per month; with the major cloud providers, you only pay a few cents. That difference is huge.

• Fits the current model — We can already set our own OpenAI key. Then it is logical that we also decide where our files are.

• Privacy & rules — Many (European) organizations need to store data in their own cloud or on their own servers. Without this option, they will not be able to use TypingMind.

• Fewer costs & work for TypingMind - If we pay for storage ourselves, your server costs and support requests will decrease. You can then focus on new features.

• Space for larger files — Think of knowledge bases with PDFs, images, audio. With our own bucket, the 10 MB limit is no longer a problem.

• Technically simple — With one standard S3 connection, it works immediately for AWS, Backblaze, Wasabi, Cloudflare R2, MiniO, and so on.

• Stay competitive — Tools like Obsidian, Logseq, and Tana already offer this. With BYO‑Storage, TypingMind remains attractive to power users and teams.

Simple proposal

• In the settings, add a “Custom S3 Storage” section (Endpoint URL, access key, secret, bucket, region).

• If you don't change anything, simply use the current TypingMind storage.

• Maintain client-side encryption so data stays safe everywhere.

I'd love to test in a beta. With my own (cheap) R2 bucket, I can immediately use TypingMind more widely. Let's make this a reality!

yes please!! even if it could be connected to S3 or anything related having my own choice for cloud sync would be great

100 pct agree, self hosted should be an option

The 10MB is really not usable for a supposedly professional application. I already have three different cloud services and I'm not gonna pay now for another one with 10 US$ a month which is nearly 20$AUD. There really needs to be another solution. This is limiting the usability of the software hugely. let me store my files in iCloud, Google Drive, Microsoft Cloud or DropBox

True story !

I changed my mind (unfortunately) and now have a 1 GB subscription for $10 a month. And I'm using... 28 MB :(

I agree with this - the current option is simply too expensive. There must be an alternative solution, such as allowing users to connect their own cloud storage. Even if the upload limit were increased to 100MB, I would at least avoid receiving warnings whenever I upload photos.

Indeed, the default 10 MB should be increased. It doesn't take much to pass that. In this day and age, that's smaller than many website page loads, and as code and documents are loaded it becomes a nagging problem. Now with Knowledge Base, this is a few documents.

$10 per year for 1 GB would be ok. But $10/month exceeds the cost of TypingMind itself in less than a year, for something that is so cheap as to be nearly free in storage and bandwidth these days.

Offering built-in connectivity to a few major storage backends would be good to enable unlimited storage, to not rely on extensions to do it (though there is at least one extremely complete one).

My request is to: