you can give kbin.run a try if you'd like. i've been actively keeping it up-to-date with the latest commits to the kbin develop branch, even had my own admin feature pull request accepted (yay!).
kbin.social's federation was disabled early on and a lot of users ended up sticking with the mothership, but kbin.run has been online since "the exodus" 3 months ago. honestly it's been more for me to use as a gateway to the threadiverse/fediverse, but i've kept registrations open while actively purging the occasional spam accounts that make their way through. i sysadmin as a hobby (i like giving myself extra work) and i will scale up the instance if it becomes necessary, but the current bare metal virtualization environment has no problem keeping up with the way it is. i also try to be as transparent as possible with the faq/privacy policy/terms of service pages and posts in the local meta and announcement magazines, but realize it's a US based instance so the laws of the land apply in full force, of course.