First, congrats! Launching anything is hard, let alone after two pivots. I had a couple of questions and comments:
* Are you looking to explicitly support other auth providers (I for one would love to have you support https://fusionauth.io/ -- full disclosure I work for them)? Or is the best path forward there to just use the Custom Token Issuer instructions?
* There's a typo here where it looks like the markdown hasn't been correctly processed: https://docs.xkit.co/docs/custom-catalog:
> If you want full control over how users interact with the Integration Catalog beyond what's available in [Self-hosting(doc:self-hosted-catalog), you can use our libraries or APIs to fully customize the experience.
* I'm trying to understand why someone would create their own catalog. Is that because they have their own suite of applications currently using OAuth for auth? So kind of a AWS Service Catalog play? Or is it more "I'll take care of adding this fiddly integration to XYZ service once so that all my developers can use this integration in the varied apps they are building"?
* What is the difference between using xkit and a tool like Zapier to handle SaaS integration? It looks like with xkit you have more control, including over the integration process. Why would I want to use something lower level like xkit?
Again, congrats on the launch!
* Are you looking to explicitly support other auth providers (I for one would love to have you support https://fusionauth.io/ -- full disclosure I work for them)? Or is the best path forward there to just use the Custom Token Issuer instructions?
* There's a typo here where it looks like the markdown hasn't been correctly processed: https://docs.xkit.co/docs/custom-catalog:
> If you want full control over how users interact with the Integration Catalog beyond what's available in [Self-hosting(doc:self-hosted-catalog), you can use our libraries or APIs to fully customize the experience.
* I'm trying to understand why someone would create their own catalog. Is that because they have their own suite of applications currently using OAuth for auth? So kind of a AWS Service Catalog play? Or is it more "I'll take care of adding this fiddly integration to XYZ service once so that all my developers can use this integration in the varied apps they are building"?
* What is the difference between using xkit and a tool like Zapier to handle SaaS integration? It looks like with xkit you have more control, including over the integration process. Why would I want to use something lower level like xkit?
Again, congrats on the launch!