This isn’t Mastodon so a “Bluesky server” isn’t a thing.
Mastodon is shaped like email so you have “servers” sending messages to each other.
Atproto is shaped more like RSS with aggregation. Everyone posts data to their hosting (which anyone could move at any time), and apps like Bluesky aggregate data from everyone’s hosting.
So a concept like “Bluesky server” is nonsensical. What you have is “atproto hosting” (which can be provided by Bluesky, by other communities, by other companies, or can be self-hosted — it’s all open source and you can even implement your own) and “Bluesky app” (of which there’s only one — but there are forks like Blacksky which fork the entire stack including the server). There also “other atproto apps” like https://leaflet.pub, https://tangled.org, etc, which have nothing to do with Bluesky.
Mastodon is shaped like email so you have “servers” sending messages to each other.
Atproto is shaped more like RSS with aggregation. Everyone posts data to their hosting (which anyone could move at any time), and apps like Bluesky aggregate data from everyone’s hosting.
So a concept like “Bluesky server” is nonsensical. What you have is “atproto hosting” (which can be provided by Bluesky, by other communities, by other companies, or can be self-hosted — it’s all open source and you can even implement your own) and “Bluesky app” (of which there’s only one — but there are forks like Blacksky which fork the entire stack including the server). There also “other atproto apps” like https://leaflet.pub, https://tangled.org, etc, which have nothing to do with Bluesky.