[sf-wy]

Great idea! I like the ergonomics of this for the developer-side, it's easy to add and puts the onus on the developer to have a robust auth system that avoids users creating 1000s of accounts so they can get unlimited LLM access.

One challenge on frontend-only apps is if the prompt is proprietary then this will be exposed unless you will then offer prompt templating or prompt mapping on your side i.e. the frontend says prompt: Template_123 and then this maps to the actual prompt somehow. Prompting is important still and maybe for a while so having the internals externally available could be sensitive.

[ProofHouse]

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

[HeavenFox]

Thanks for the feedback! Pricing is something we are iterating on. Our intention is that we only make money if our customers make money - which is why only authenticated users count towards the limit.

If pricing is preventing anyone from using our product, please shoot me an email (in my HN profile) and we'd love to hear about your use case!

Good call on the marketing copy! We will do some revisions!

[HeavenFox]

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!