As I understand it, to support things like timed bans your only options are undocumented APIs which can change at any point in time. So while some things are documented and possible, not everything is and that's not the level of support we need.

Right, most of the APIs used are documented, but https://slack.com/api/users.admin.setInactive is not. There are some unofficial docs: https://github.com/ErikKalkoken/slackApiDoc/blob/master/user...

Otherwise APIs used are documented: https://api.slack.com/methods/files.delete https://api.slack.com/methods/chat.delete https://api.slack.com/methods/search.files https://api.slack.com/methods/search.messages

To be clear: NOT recommending Slack. Just mentioning that we also have issues and some tooling has helped, the tools could use more docs but they're pretty simple and open source FWIW.

Still, installing those open source tools in the Go Slack and collaborating with Kubernetes over them seems better that just live with whatever Slack offers today.

Downside is that it's additional infrastructure that someone now needs to be on-call to support and pay for.

This is the main reason we aren't considering leaving Slack.