I would reconsider the "Unlimited Emails" offering for the "Ultimate" $100/mo plan. Assuming you're using SES, a customer sending 1,065,000 emails would cost ~$100. All it takes is one person to abuse it before it's costing you big money.<p>On the surface, "Unlimited" sounds great, but your target market is developers that know the cost of sending emails. This may result in the opposite effect as it signals your model may not be scalable if there's not enough low usage accounts to subsidize the additional costs of sending emails.
Seems like policies around data and privacy would be paramount here. As someone who has developed a couple backends I always struggle to see the value add of a system like this. For me, it always seems like this is something I'll have to do later and back tracking would be more work. Very clean site though, the mint technology piece was pretty interesting as well. Good synergy to market both at once!
Interesting that you've made it using<p><a href="https://crystal-lang.org/" rel="nofollow">https://crystal-lang.org/</a>
<a href="https://www.mint-lang.com/" rel="nofollow">https://www.mint-lang.com/</a><p>How did you decide to use these framework and how was your experience ?
I released Base about a month ago and created a blog post with some details <a href="https://dev.to/gdotdesign/base-api-for-authentication-email-sending-image-upload-and-more-4f1" rel="nofollow">https://dev.to/gdotdesign/base-api-for-authentication-email-...</a><p>Let me know what you think! :)
Looks great, but I have been bitten badly before by vendor lock-in using a SaaS and they either go out of business or jack up their prices exponentially. The only mitigation I know of is to make Base open source, so if needed users can host their own instance. What are your thoughts on this?
I use firebase for authentication and have been quite happy with it, but if this provides better integration with mailing lists out of the box, that would be compelling to me. Although I use firebase for authenticated users, I also have a mailing list sign up form with just an email field. I ended up creating my own confirmation email flow because I needed it to work for both people who created an account and people who just used the email form. It would've been nice not to have to do that.
I have question regarding example of "Retrieving details of a file"<p><a href="https://www.base-api.io/reference/files" rel="nofollow">https://www.base-api.io/reference/files</a><p>The curl request uses [1] id and in response we get [2] id. Why is that?<p>[1] 6536fb5e-01b1-4a0c-b05b-33bac00c65ac<p>[2] ed7066dc-614c-48f3-8456-926598e88473
This is pretty interesting and useful. This would be immensely useful for prototypes and a great entry point for developers. Kind of reminds me of Firebase how it tries to be a <i>one-stop-shop</i>. it also seems much more approachable than Firebase which is nice.
Why should I link myself so heavily to a provider like you? Not wanting to troll, as a dev, I know that the problems you try to solve are common, but still wondering what happens "if..."
The sign-up button for the developer plan doesn't work (Firefox 68.0.1). Nice idea though. It'd be neat to be able to host it ourselves, if you ever plan to release it as OSS.
This looks awesome! What backend framework are you using? I'm the author Lucky and was wondering if you happened to use it on the backend since you are using Crystal
Incredible work, would love to start using something like this.<p>I personally need a self hosted plan with enterprise support.<p>But your pricing plans look great for the hobbyist and small shop.
A point of note.<p>Like usual with Ruby/Crystal apps the api uses snake case for its keys.
The js default is usually camel case.
It can be rather ugly to have it mixed if one uses this in a js/node app.