Is this open source? Is it local browser API calls, or routing through your server?
replies(1):
Prompt testing should be simple and straightforward. All I wanted was a simple way to test prompts with variables and jinja2 templates across different models, ideally somthing I could open during a call, run few tests, and share results with my team. But every tool I tried hit me with a clunky UI, required login and API keys, or forced a lengthy setup process.
And that's not all.
Then came the pricing. The last quote I got for one of the tools on the market was $6,000/year for a team of 16 people in a use-it-or-loose-it way. For a tool we use maybe 2–3 times per sprint. That’s just ridiculous!
IMO, it should be something more like JSFiddle. A simple prompt playground that does not require you to signup, does not require API keys, and let's experiment instantly, i.e. you just enter a browser URL and start working. Like JSFiddle has. And mainly, something that costs me nothing if I'm or my team is not using it.
Eventually I gave up looking for solution and decided to build it by myself.
Here it is: https://langfa.st
Help me find what's wrong or missing or does not work from you perspctive.
P.S. I did not put any limits or restrictions yet, so test it wisely. Don't make me broke, please.
API calls are routed through a thin proxy on my side, this is how you get access to all the models with my API keys. I definitely would not want to store those keys in code of the JS bundle in the browser (:
Only if you want to spend more time managing an open source project than building a real world project. It is not easy and it can be a big distraction.