8 ms·
That's completely reasonable. I would, however, like to point you to the Terms of Service stormpath has: http://www.stormpath.com/terms_of_service http://www.s
by rdegges 13y ago
That's completely reasonable.
I would, however, like to point you to the Terms of Service stormpath has: http://www.stormpath.com/terms_of_service http://www.stormpath.com/terms_of_service
You own all your data, completely. Us (as employees) can't even access it! Furthermore, we use strong encryption and all security best practices to keep things locked away.
I'd argue that if you're safe enough with pushing your user data into an RDS instance, you're already giving out this part of your application.
- nathancahill 13y agoYou're comparing a tiny startup to AWS. For me, the bigger issue isn't security, it's not knowing if you guys will still be around in a couple months (no offense). Between the chances of getting acquired or running out of funding and shutting down, startups aren't the best place to put the most essential part of your application. Stormpath is gone = my app is gone.
- rdegges 13y agoThis is a great point I wasn't even considering. You're completely right -- there's definitely inherent risk in relying on a third party (particularly a new one). Just some background on Stormpath: we've been around since 2012, have funding, a big team, and are growing pretty fast. Also: we make it as painless as possible to migrate out of our platform (I can answer specific questions if anyone is interested).
- nathancahill 13y agoWhen I write an app, I never worry that one day I'll wake up to an email from my database saying "I'm done storing your data, you'll have to export it to another database. Look, I made it really easy to migrate." It's a nice product, but it would work better as an open source service I could host on my own servers and databases.