Ask HN: Industry standards for locking down a SAAS product to prevent abuse?

Re:Ask HN: Industry standards for locking down a SAAS produc... by kvnn on Tuesday May 28, 2013 @03:31PM (#5782166)

Congrats on finishing!

I'm building a SaaS product right now and finding that there aren't very many sources for finding industry standards. Non-enterprise SaaS is quite new.

That said, I think the best thing to do is wait until you spot abuse, and create measures to prevent it. Work on your analytics and reporting systems rather than trying to contrive possible service abuses.

[ Parent | on HN ]

Re:Ask HN: Industry standards for locking down a SAAS produc... by Terpaholic on Tuesday May 28, 2013 @04:42PM (#5782623)

Hey thanks! Especially for the MVP, I think you're absolutely right about the abuse part. As for the login/recovery, have you had any experience with signup rates using Facebook/Twitter authentication? Reinventing the login flow seems like a bad idea to me at this point. For billing, I'm examining Recurly and Paypal Subscriptions (although I'm wary of Paypal).

[ Parent | on HN ]

Re:Ask HN: Industry standards for locking down a SAAS produc... by kvnn on Tuesday May 28, 2013 @06:52PM (#5783385)

I don't have experience, but I've read this : http://blog.mailchimp.com/social-login-buttons-arent-worth-i... .

I'm rolling my own signup (which is easy enough in Django), but I'd consider doing a Google login. Facebook & Twitter I wouldn't care to implement: My target audience wouldn't want to be mixing their social logins with my service.

[ Parent | on HN ]