To my knowledge you can't run your own self-contained Bluesky server/network that doesn't go through (or at least partially rely on) services owned/operated by the Bluesky corporation.

> A world of full self-hosting is not possible with Bluesky. In fact, it is worse than the storage requirements, because the message delivery requirements become quadratic at the scale of full decentralization: to send a message to one user is to send a message to all. Rather than writing one letter, a copy of that letter must be made and delivered to every person on earth.

https://dustycloud.org/blog/how-decentralized-is-bluesky/

> The cost of running a full-network, fully archiving relay has increased over time. After recent growth, our out-of-box relay implementation (bigsky) requires on the order of 16 TBytes of fast NVMe disk, and that will grow proportional to content in the network.

https://whtwnd.com/bnewbold.net/3lbvbtqrg5t2t

> The fediverse currently hosts around 27,000 servers (many more users, but let's focus on servers). Adding just 5 more servers would be a blip in terms of the affect on the network. Adding 5 more servers to an ATProto ecosystem with that many fully participating nodes would be an exhausting number of additional messages sent on the network. ATProto does not scale wide: it's a liability to add more fully participating nodes onto the network. Meaningfully self-hosting ATProto is a risk to the ATProto network, there is active reason to disincentivize it for those already participating.

https://dustycloud.org/blog/re-re-bluesky-decentralization/

[plus more]

https://mathewingram.com/work/2024/11/28/is-bluesky-really-d...

https://en.futuroprossimo.it/2024/11/anatomia-di-bluesky-e-d...