No Database, No Drama: Why RedSky Is Built Client-Side

When we tell people RedSky is "client-side" and "hosts no content," the reaction splits two ways. Technical folks nod. Everyone else hears a phrase that sounds like fine print and moves on. That's a shame, because it's one of the most important things about how RedSky is built — and for adult creators specifically, it's a feature with real consequences. Let me explain it in plain language and tell you why it matters for you.

What "client-side" actually means

Most apps you use work like this: you log in, and your data lives on the company's servers. Your posts, your messages, your activity — copied into their database, sitting on their infrastructure, under their control. The app is a window, but the company is also a warehouse, holding a copy of your stuff.

RedSky doesn't work that way. RedSky is a client — a window onto the Bluesky network, which runs on the open AT Protocol. When you use RedSky, it talks directly to that network from your browser. It shows you your feed, lets you post, lets you message — but it doesn't keep its own warehouse of your content. We host no content and maintain no database of your posts. Your posts live on the open network, where they already lived; RedSky is just a better pane of glass to see them through.

Think of it as the difference between a librarian who photocopies every book you read and keeps the copies, versus one who simply hands you the book from the shelf. RedSky hands you the book.

Why this matters for adult creators specifically

This isn't just an architectural preference. For people who make adult content, it has direct, practical upsides.

There's less to leak. The hard truth of security is that data which doesn't exist can't be stolen. Every service that stores a copy of your content and activity is another warehouse that could be breached, subpoenaed, sold in an acquisition, or quietly mined. A client that keeps no database of your posts simply has far less to lose on your behalf. When a creator asks "what happens to my data if RedSky gets breached or sold?" the honest answer is: there's no central trove of your posts here to take.

You're not trapped in a new silo. A lot of "creator-friendly" platforms are really just another walled garden trying to own your audience. RedSky is the opposite. Because it's a client on an open protocol, your identity, your follows, and your social graph live on the network — not locked inside RedSky. If you ever stopped using RedSky tomorrow, your account and audience are untouched, because they were never ours to hold. That's account portability, and it's the whole point of building on AT Protocol.

Your login stays in your control. You log into RedSky with a Bluesky app password — generated under Settings → App Passwords on Bluesky, never your main password. It's scoped and disposable: you can revoke it anytime without touching your real credentials. So even your access to RedSky is something you hold the keys to, not something we hold over you.

What it means in everyday use

In practice, the client-side design just shows up as the experience being clean and honest:

• You log in with your real Bluesky account. Same handle, same follows, same posts — RedSky isn't a separate account or a copy. It's your existing presence, finally shown the way it should be: adult content visible by default, no blur, no toggles, adults-only feeds.
• The full toolkit, none of the warehousing. Native video, an image lightbox built for browsing, custom feeds, lists, DMs, profile editing, light and dark mode, feed and notification filters, hide a user, report a post — all the tools, working against the live network.
• A few things are intentionally local. Your saved/bookmarked posts, for instance, are kept on your device rather than synced to some central account store. That's the tradeoff of not running a warehouse — and we'd rather be honest about it than quietly hold your data to make a feature smoother. Build your saved collection on the device you actually use, and you're set.

The honest limits

I'm not going to oversell this. Client-side architecture isn't a magic shield, and I won't pretend it is. RedSky can't protect you from mistakes the network can't — mislabeled posts, weak passwords, oversharing in DMs. And we're candid about what's still ahead: server-side session hardening is on our roadmap, not something we've finished. Today, your session lives in your browser, which is exactly why app passwords — scoped and revocable — matter so much in the meantime.

We're also a third-party client and not affiliated with Bluesky PBC. We're an independent team building a better adults-only window onto an open network we don't own and don't want to own. That independence is part of the pitch: your audience isn't ours to monetize, lock in, or lose.

Why we built it this way on purpose

We could have built RedSky as another silo — copy everything onto our servers, own your data, call it "your account." That's the standard playbook, and it's the playbook that's failed adult creators over and over. You build on rented land, the landlord changes the terms, and your audience and your content are suddenly hostage to someone else's business decision.

We didn't want to be one more landlord. So we built a client, not a warehouse. RedSky's job is to show your world the way it's meant to be seen and then get out of the way — not to accumulate a database about you that becomes a liability the moment anything goes wrong.

No database. No silo. No drama. Just a better window onto the network you already own. Bring your Bluesky account, log in with an app password, and see your feed unfiltered.

— Craig, RedSky Team