DEV Community

Iconical
Iconical

Posted on

I Built My Own Self-Hosted File Sharing Server Instead of Alts; Here’s Why

The Breaking Point

At some point, I realized I was overcomplicating something simple.

I just wanted to:

  • Upload a file
  • Share a link
  • Preview media
  • Move on

Instead, I kept juggling heavy cloud platforms, storage limits, privacy tradeoffs, and unnecessary friction.

So I asked myself:

Why not just make what I want and host it myself?

That’s how Swush started.


The Problem With “Simple” File Sharing

Modern cloud storage tools are powerful but often overkill.

Common issues I ran into:

  • File size limits
  • Account requirements
  • Privacy concerns
  • Slow sharing workflows
  • Feature bloat for basic needs
  • Multiple tools for different similar features

Sometimes you don’t need a full ecosystem.

You just need fast, clean file sharing that you control.


What Is Swush?

Swush is a self-hosted file sharing and media server built to be:

  • ⚡ Fast
  • 🧩 Minimal
  • 🔐 Privacy-friendly
  • 🐳 Docker-ready
  • 💻 Everyone-focused

It allows you to:

  • Upload files instantly
  • Generate shareable links
  • Serve media
  • Run entirely on your own infrastructure
  • Add your watchlist
  • Including many upcoming features

No SaaS lock-in. No forced accounts. No external cloud storage providers.


Why Self-Hosted?

Self-hosting gives you:

  • Full data ownership
  • Custom domain support
  • Deployment flexibility
  • Integration freedom
  • Zero third-party tracking

For developers especially, it removes friction.

You control the stack, the deployment, the storage, and the roadmap.


Tech & Architecture Decisions

When building Swush, I focused on:

  • Keeping deployment simple
  • Avoiding bloated dependencies
  • Making Docker the primary install method
  • Designing for clarity over complexity

One of the biggest lessons:

Deployment friction kills adoption.

If something takes 20 steps to run, most people won’t try it.

Simplicity became the core philosophy.


Lessons Learned Building It

  1. Simple tools are powerful
  2. Self-hosting communities value transparency
  3. Developer UX matters more than fancy marketing
  4. Documentation is as important as code
  5. Fast setup increases feedback

The goal wasn’t to build “another cloud.”

It was to build something clean, practical, and easy to run.


Who Is It For?

  • Everyone
  • Privacy-focused users
  • Homelab enthusiasts
  • Small teams who want lightweight internal sharing
  • Anyone tired of unnecessary SaaS complexity

What’s Next?

Swush is evolving, and feedback is incredibly valuable.

If you're into self-hosting or open-source tools, I’d love to hear your thoughts.

Links:

👉 Source Code: https://github.com/imthatdev/swush
👉 Roadmap: https://iconical.dev/roadmap/swush
👉 Feedback: https://iconical.dev/feedback/swush
👉 Changelog: https://iconical.dev/changelog/swush


Final Thought

Sometimes the best solution isn’t a bigger tool.

It’s a simpler one you fully control.

Top comments (0)