There’s a ton of clients actually, and you can run almost all of the infrastructure yourself as it’s open source. They’ve committed to opening up the entire protocol, but at the moment some of the connections between the main bluesky network and third party self hosted services are permissioned. I even talked through with them how you’d implement Zaps on bluesky and it’s pretty straightforward. The only tricky part is users won’t know they’re there because the clients don’t display or send the event kinds for zaps. Profiles can be extended easily to add lightning wallet addresses. It’s not codeless because atproto has schema validation, so you’d need to create a schema definition and json validator code for zaps and adding wallet addresses to profiles, but once you did that, the PDS and other parts of bluesky would work with them.