Show HN: Base – API for authentication, email sending, images and more(base-api.io)

140 pointsby gdotdesign7 tahun yang lalu53 comments

Show HN: Base – API for authentication, email sending, images and more

https://www.base-api.io

55 comments

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.

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.

gdotdesign7 tahun yang lalu

Thank you for your insight!

I'm still figuring out the pricing so I'll keep this in mind!

ttul7 tahun yang lalu

The even greater problem with sending email is that your platform will immediately and comprehensively be abused by spammers.

To make your email woes go away, I would recommend using MailChannels [1] rather than SES or SendGrid because MailChannels has a built-in anti-abuse layer that will send you a webhook whenever a bad user is detected. SES will just terminate your account, which probably isn't what you want. Also, at high volume, MailChannels costs less.

[1] Disclosure: MailChannels is my company.

novaleaf7 tahun yang lalu

not just emailing. any service that could theoretically be utilized by spammers/scammers will be. (Source: my own SaaS)

jkaufmann_7 tahun yang lalu

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!

rtcoms7 tahun yang lalu

Interesting that you've made it using

https://crystal-lang.org/ https://www.mint-lang.com/

How did you decide to use these framework and how was your experience ?

gdotdesign7 tahun yang lalu

I'm the author of Mint, so it was the obvious choice :)

I choose Crystal because I had experience using Ruby and I absolutely loved the syntax, also Mint is built with Crystal. I really like it because it easy to read (even with type annotations) and compiles to a fast binary.

Edit: If you have specific questions let me have it :D

mintplant7 tahun yang lalu

From Mint's docs [0]:

> Record definitions are globally unique, so defining a record with the same structure but a different name will raise an error.

So I can't have both

    record User {
      email : String,
      name : String,
      id : Number
    }

and

    record Task {
      name : String,
      description : String,
      id : Number
    }

in the same project?

[0] https://guide.mint-lang.com/reference/records

gdotdesign7 tahun yang lalu

You can! One has email field the other has. description field.

Existenceblinks7 tahun yang lalu

One interesting aspect is that it takes a lot of energy building the whole compile-to-js frontend framework, yet you are also building your own service. Kudos!

I'm using Elixir and Elm, and understand why Mint happens. I'm keeping eyes on Mint, would love see a build-with-Mint page. This app is the first one!

Scarbutt7 tahun yang lalu

Not Crystal related but from where do you get the art? ;)

algodaily7 tahun yang lalu

Not OP but google around for vector-style images. There was even a Show HN project that generated them, I'll look around

swyx7 tahun yang lalu

i'd appreciate a link, i did a basic search on those keywords but didnt find anything matching.

matdehaast7 tahun yang lalu

https://undraw.co/ https://www.humaaans.com/

gdotdesign7 tahun yang lalu

I released Base about a month ago and created a blog post with some details https://dev.to/gdotdesign/base-api-for-authentication-email-...

Let me know what you think! :)

andwaal7 tahun yang lalu

Hi, could you explain this section from your TOS?

"You will provide us the right to reproduce, modify or create derivative works from your Content. Obviously we won’t be modifying your Content, we need these rights for example to be able to share your designs with other users. You will also provide us a right to publicly perform or display your Content to allow us to display the material on other users’ monitors.

Base does not claim any ownership on your Content. You hereby grant Base a worldwide, non-exclusive, revocable, royalty-free, fully paid, sublicensable and transferable license to use, host, store, reproduce, modify, create derivative works, publicly perform, display, distribute and transmit your Content."

I am not sure I read it right, but does it say that you are allowed to share my content with whomever you like? And also create new versions of my work?

growt7 tahun yang lalu

That's almost a standard disclaimer by now. If this API let's you upload an image and by request (of yourself or a user) it returns a resized version of that image, that might already be a derivative work and distribution of that content.

gdotdesign7 tahun yang lalu

Thank you for the comment. It's not my intention to claim any ownership of content, I'll review the text and modify it accordingly.

_underfl0w_7 tahun yang lalu

It says that in the quoted text. You still didn't answer the question though.

FrancoisBosun7 tahun yang lalu

Looks nice. I’m uncomfortable pushing the password in plaintext to an unknown entity. I can always bcrypt the password locally before sending it through the API, but it would be great to see examples of this, to prevent deva from pushing secrets outside their zone of control.

Otherwise, I can see myself using this in some side-projects. Good work!

Blackstone47 tahun yang lalu

When I login/signup to a website, I'm always sending my password in plaintext to the server (obv. encrypted via TLS). What's the difference?

FrancoisBosun7 tahun yang lalu

The difference is my customer's don't have a first-party relationship with the data store that holds their password.

    browser -> www.example.com

    browser -> www.example.com -> Base

That's the biggest problem I see with this approach. The password will be seen by two parties instead of just one.

prabhaav7 tahun yang lalu

Very cool gdotdesign! We're working on something similar in the decentralized auth space.

Just curious, how/why did you pick email sending as a service add on?

gdotdesign7 tahun yang lalu

It was easier then implementing it by hand, making sure that they are delivered to the inbox, etc.

lifty7 tahun yang lalu

who did the design for the website?

gdotdesign7 tahun yang lalu

It's me, still a one man show :)

AngeloAnolin7 tahun yang lalu

Maybe you would need help later. At some point. I can help.

nodesocket7 tahun yang lalu

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?

jacobobryant7 tahun yang lalu

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.

gdotdesign7 tahun yang lalu

Mailing list support is definitely on the backlog!

dawidw7 tahun yang lalu

I have question regarding example of "Retrieving details of a file"

https://www.base-api.io/reference/files

The curl request uses [1] id and in response we get [2] id. Why is that?

[1] 6536fb5e-01b1-4a0c-b05b-33bac00c65ac

[2] ed7066dc-614c-48f3-8456-926598e88473

gdotdesign7 tahun yang lalu

Thank you for spotting it! It's just inconsistency, I'll update the examples.

dawidw7 tahun yang lalu

Thank you, I thought that I was missing something. BTW - I've found your page very useful - thank you for that!

gitgud7 tahun yang lalu

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 one-stop-shop. it also seems much more approachable than Firebase which is nice.

reeeeee7 tahun yang lalu

I completely agree on this being a lot more approachable than Firebase. The premise of Firebase is so nice, but the amount of information when starting to look into it are overwhelming.

napolux7 tahun yang lalu

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..."

gdotdesign7 tahun yang lalu

By "if..." I assume you mean by going out of business? In that case the service would be released as open source and you would continue as normal.

What I would like feedback on is how people would like to use a service like this? Self hosted with a license? SaaS? some other way I'm not thinking of?

jacobobryant7 tahun yang lalu

For me, as an early stage startup founder, I'd prefer SaaS. At this stage I don't want to have to think about anything that could've been handled for me. At a later stage I might prefer self-hosted, but not sure.

sambf7 tahun yang lalu

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.

gdotdesign7 tahun yang lalu

Thanks for the bug report! It should be fixed now.

> It'd be neat to be able to host it ourselves, if you ever plan to release it as OSS.

The pricing is just a placeholder at this point, it is possible that there will be a self hosted plan, since it can be easily compiled to a single binary.

paulcsmith7 tahun yang lalu

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

greatjack6137 tahun yang lalu

Incredible work, would love to start using something like this.

I personally need a self hosted plan with enterprise support.

But your pricing plans look great for the hobbyist and small shop.

garysahota937 tahun yang lalu

Are there any alternatives to Base as well? What are some main points for using this over them?

jaequery7 tahun yang lalu

It’s the beginning of an Api-as-a service trend.

Nullabillity7 tahun yang lalu

Well, Parse did it a couple of years ago. And showed why it's a horrible idea to rely on a service like this.

gitgud7 tahun yang lalu

Is there an article you could link? Sounds interesting

statictype7 tahun yang lalu

Isn’t that what AWS started more than 10 years ago?

jaequery7 tahun yang lalu

I was thinking more in terms of a full-fledged API SaaS platform that have business logic and data-schemas/storage.

It comes w/ an admin and you just pick and choose what you need, for example:

/users /posts /products /orders /login /emails etc ...

It'd be neat to see a community-driven marketplace to boot, for all types of solutions.

Perfect for SPAs and JAMstacks.

[deleted]7 tahun yang lalu

prabhaav7 tahun yang lalu

I think maybe Heroku is a better analogy in this scenario?

mintplant7 tahun yang lalu

More like Parse (since bought out by Facebook).

alephnan7 tahun yang lalu

Google App Engine

[deleted]7 tahun yang lalu

sparkling7 tahun yang lalu

What about delay between my backend to your API?

LordHeini7 tahun yang lalu

A point of note.

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.