Cloud vs Self-Hosted: Which Wardrowbe Is Right for You?

Wardrowbe comes in two flavors: a cloud subscription you sign up for in two minutes, and a free self-hosted version you run on your own hardware. Same app, different operational model. I get asked which one to pick fairly often, so here's an honest breakdown.

Spoiler: most people should use the cloud version. But the self-hosted path exists for real reasons, and if those reasons apply to you, it's a genuinely good option, not a "lite" alternative.

The Short Version

Both versions have the same features: AI tagging, outfit suggestions, weather integration, learning engine, family sharing, analytics, the whole thing. Self-hosted isn't a stripped-down version.

What's Actually Different

The difference isn't features. It's who operates the infrastructure.

With cloud, I run the servers. You sign up, the app works, I push updates automatically. If something breaks, it's my problem to fix. You pay $10/month (or $9/month on the yearly plan) and that's the end of your infrastructure involvement.

With self-hosted, you run your own server. Docker Compose brings up the entire stack in one command. But you're also the one doing the git pull when a new version ships, managing backups, keeping your server up. There's no monthly fee because there's no service being provided, just software.

The AI piece is worth calling out specifically. Cloud includes managed AI with high-accuracy models for tagging and outfit suggestions. Self-hosted means you bring your own LLM, usually via Ollama or any OpenAI-compatible API. Getting started with the self-hosted AI setup takes some configuration. The results can be just as good if you run a capable model, but it's more setup and the quality depends on what hardware you're running.

Virtual Try-On is similar. Cloud users get 3 credits per month included (see /#pricing for details). Self-hosted users need to set up thier own ComfyUI instance and point the app at it.

Who Should Choose Cloud

Honestly, most people. Here's the profile:

You want the app to just work. Sign up, download the mobile app, start digitizing your wardrobe. No Docker, no environment variables, no server. The whole setup takes a couple minutes.

You don't have a spare machine. Self-hosting requires hardware that's always on. If you don't already have a home server, NAS, or cheap VPS lying around, you'd be buying or renting infrastructure specifically for this — and at that point, $10/month for cloud is usually cheaper.

You want automatic updates. When I ship a new feature or fix a bug, it deploys automatically. Self-hosted users have to pull and restart their stack manually. It's not hard, but it's friction that cloud users never deal with.

You want reliable uptime. Your home server going offline means your wardrobe app is offline. Cloud has redundancy built in. Not a big deal for a wardrobe app specifically, but worth noting.

You want managed AI without configuration. The cloud version uses well-tuned models. You get accurate tagging and good outfit suggestions without touching a single config file. If you care about suggestion quality, the managed path is simpler to get right.

The free trial is 7 days. If you decide it's not for you, you haven't paid anything.

Who Should Choose Self-Hosted

The self-hosted version exists because I believe software like this should be ownable. Some people have real reasons to run it themselves.

You already run a home server or NAS. If Docker Compose on your machine is a normal Tuesday for you, adding Wardrowbe is trivial. You're not adding infrastructure overhead, just another service.

Privacy is a genuine priority. Cloud means your clothing photos and outfit history live on my servers. I don't track you or sell your data, but that's my word. Self-hosted means none of that data leaves your network. For people who take wardrobe data privacy seriously, that's a meaningful difference, not a hypothetical one.

You want to use your own LLM. Maybe you're already running Ollama for other projects. Maybe you have a GPU at home. Maybe you just don't want any AI company seeing your clothing photos. The self-hosted version connects to any OpenAI-compatible API, so you have full control over the AI pipeline.

You enjoy tinkering. Some people genuinely like having the source code, understanding how it works, and customizing things. The GitHub repo is open source, and that's the whole point. Contributions are welcome.

You want zero ongoing cost. The self-hosted version is free. If you already have hardware or can use Oracle's free tier VPS, the only cost is your time.

The Setup Experience, Honestly

Cloud setup: go to app.wardrowbe.com, create an account, download the mobile app. Done.

Self-hosted setup:

git clone https://github.com/Anyesh/wardrowbe.git
cd wardrowbe
cp .env.example .env
# Edit .env with your domain, LLM endpoint, etc.
docker compose up -d
docker compose exec backend alembic upgrade head

That's genuinely it for the app itself. The 15-30 minutes in the comparison table is mostly configuring your .env, setting up a reverse proxy if you want HTTPS, and getting an LLM running if you don't have one. If you've done this kind of thing before, it's fast. If it's your first time, budget closer to an hour and occassion some patience for DNS propagation.

Ongoing maintenance is low. Pull updates when you want new features, keep your server running, do your own backups. Nothing surprising there.

One Thing Worth Knowing

The cloud revenue funds the open source development. When you subscribe, you're paying for your subscription and also indirectly making the self-hosted version better. I work on one codebase for both, and the features ship to both at the same time. It's not a separate project that gets attention when I have spare time.

So if you self-host and like the app, telling people about it matters. The sustainable model only works if some people pay for the cloud version.

A Quick Word on Privacy

Since privacy comes up a lot in these comparisons: cloud Wardrowbe doesn't track you, doesn't sell your data, doesn't share it with third parties. No ad networks, no analytics resellers, no fashion brand partnerships. Your wardrobe data is used to run your wardrobe app and nothing else.

If you still want more control than that, self-hosting is the right answer. There's a whole breakdown of what wardrobe apps know about you and why it matters if you want to think through it more carefully.

Which One Should You Pick

If you're not sure, start with cloud. The free trial costs you nothing, setup takes minutes, and you can evaluate the app without any infrastructure commitment. If you later decide you want to self-host, your data is exportable and the migration is straightforward.

If you already run a home server, care deeply about data ownership, or want to tinker with a local LLM setup, start with self-hosted. It's not harder than most self-hosted apps, and the documentation covers the setup in detail.

Either way, you're getting the same wardrobe app. The choice is really about who handles the server.

Start with cloud: 7-day free trial at app.wardrowbe.com. No credit card required until the trial ends. See pricing for plan details.

Start with self-hosted: GitHub repo. Docker Compose, free forever.