It's just more complex than that. There's no relay model for the events, because it does not prescribe atomic events, but rather leverages pkdns (a separate application) to assign keys in place of DNS. So like you can host your website at a long string that is published to DHT. That is the censorship-resistant aspect to the PK ecosystem. This part also requires a browser or OS allowance to resolve PKDNS websites.

Then, you're correct in that "the live version of Pubky" is invitation-only, but that extends to the application. So anyone running an instance of the Pubky app can provide invite codes to their own instance and users.

I haven't gotten my instance running yet but there is at least one other instance of the Pubky app running from someone who doesn't work for Synonym.

Part of the PK Stack includes a Nexus which handles routing and indexing if I'm not mistaken.

I would be interested to hear your real opinion on its architecture. At this point I want to shove a nostr relay inside of Pubky just to fuck with people. But priorities.