Show HN: ServerlessAI – Build, scale, and monetize AI apps without back end (opens in new tab)

Here's my hypothesis: since we are still in the gold rush phase of AI, going to market early and pivoting quickly is imperative. Therefore, it is worthwhile to focus on your differentiating factor and outsource everything else. Plus we use the OpenAI API format, so there isn't vendor lock-in - though we hope we provide enough value for you to stay!

And you are right on the money that OpenAI may not be the best backend forever. That's why we also support Anthropic, Groq, and Mistral.

Lots of company are doing this exact business, they all have insane churn rate.

Biggest use case seems to be for people who want to prototype something quickly, they don’t yet want to bother with managing the infra and don’t mind the extra cost since this will be running at small scale. But if the experiment is successful, then the customer churns as it (most of the time) makes little sense to scale ML on serverless. And if the experiment is not successful, they are obviously also going to churn.

A friend of mine works for a very large company and he was telling me about an AI startup they bought for (he thinks) in the ballpark of 8 digits. After they were on boarded he was able to dig into what it was. It's literally a GPT backend with system prompts and RAG. If you have a good sales team you can print money for doing almost nothing right now.

I've seen an AI yearbook photos styled app print money that was serverless.

There's lots of novelty apps atm that, as the other commented stated, just want to get to market as soon as possible to validate an idea

Doesn't everyone ask this question about Okta, like what am I doing farming out my user login?

Thanks! Despite my best Google-fu, I didn't find Puter in my market research :) It is a very interesting project for sure!

Looking at Puter's offering, at the end of the day, we serve the same goal of making developer's life easier. ServerlessAI is more narrowly focused on AI use cases, while Puter is providing a more generic app runtime. Both have their best use cases!

Founder of Puter here. Thank you very much for mentioning us!

Serverless in today's world means you don't have to manage the infrastructure and you pay nothing if it's idle. It doesn't mean "no servers" and really never did.

I disagree. These sorts of pricing structures rule out consumer usage quickly due to high numbers of users. Have flat usage fees and get rid of these per user limits. Both doesn’t make sense unless you want to turn away any app that has many users.

I’d also recommend they clean up the copy of what they offer (expand on the why).

Other than that looks cool

Thanks for the feedback! We are building prompt templates right now. Besides the security benefits you mentioned, this can also enable developers to tweak prompts without redeployment, run A/B tests, and evaluate different models. It's an incredibly powerful tool!

I’m binge watching House MD right now, and the number of distinct ways he shits on people for basically saying, “focus on what’s important” is impressive.

The latest one I recall was something like, “we’ll be sure to use the real medicine instead of the placebos.”

Perhaps:

> You can authenticate users through any identity provider, like Google or Apple, and set per-user request or spending quotas. You can also define an allowlist for endpoints and models. To monetize, you can apply different quotas for various user tiers.

Thank you! We do believe app developers will find this valuable, and we are also working on IAP integration. Sadly I am not an app developer, so if anyone have any suggestions on how I can serve this community better, I'm eager to hear from you! My email is in my HN profile.

Will look into Firebase Marketplace! That is a great suggestion!

IANAL, but since "Serverless, Inc." chose a generic term for their trademark, usually this means only very specific instances of that mark are enforceable, e.g. "Serverless Framework", "serverless.com" and "Serverless, Inc." But if a company were to say "We make it really easy to use serverless technologies in the cloud!" (note lower case s), that shouldn't be infringing because it's just using serverless as a generic, descriptive term.

"ServerlessAI" and "serverlessai.dev" shouldn't be infringing because they incorporate the generic term in their mark, not the Serverless Framework-specific term. Of course, this means that ServerlessAI would have the same issues you point out - a less-defensible mark and poor Google results.

Also, in the US pretty much anyone can sue for anything, so even if you're in the right it can be an expensive headache to have to defend yourself.