TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Show HN: Axilla – Open-source TypeScript framework for LLM apps

161 pointsby nichocharalmost 2 years ago
Hi HN, we are Nick and Ben, creators of Axilla - an open source TypeScript framework to develop LLM applications. It’s in the early stages but you can use it today: we’ve already published 2 modules and have more coming soon.<p>Ben and I met while working at Cruise on the ML platform for self-driving cars. We spent many years there and learned the hard way that shipping AI is not quite the same as shipping regular code. There are many parts of the ML lifecycle, e.g., mining, processing, and labeling data and training, evaluating, and deploying models. Although none of them are rocket science, most of the inefficiencies tend to come from integrating them together. At Cruise, we built an integrated framework that accelerated the speed of shipping models to the car by 80%.<p>With the explosion of generative AI, we are seeing software teams building applications and features with the same inefficiencies we experienced at Cruise.<p>This got us excited about building an opinionated, end-to-end platform. We started building in Python but quickly noticed that most of the teams we talked to weren’t using Python, but instead building in TypeScript. This is because most teams are not training their own models, but rather using foundational ones served by third parties over HTTP, like openAI, anthropic or even OSS ones from hugging face.<p>Because of this, we’ve decided to build Axilla as a TypeScript first library.<p>Our goal is to build a modular framework that can be adopted incrementally yet benefits from full integration. For example, the production responses coming from the LLM should be able to be sent — with all necessary metadata — to the eval module or the labeling tooling.<p>So far, we’ve shipped 2 modules, that are available to use today on npm:<p>* *axgen*: focused on RAG type workflows. Useful if you want to ingest data, get the embeddings, store it in a vector store and then do similarity search retrieval. It’s how you give LLMs memory or more context about private data sources.<p>* *axeval*: a lightweight evaluation library, that feels like jest (so, like unit tests). In our experience, evaluation should be really easy to setup, to encourage continuous quality monitoring, and slowly build ground truth datasets of edge cases that can be used for regression testing, and fine-tuning.<p>We are working on a serving module and a data processing one next and would love to hear what functionality you need us to prioritize!<p>We built an open-source demo UI for you to discover the framework more: <a href="https:&#x2F;&#x2F;github.com&#x2F;axilla-io&#x2F;demo-ui">https:&#x2F;&#x2F;github.com&#x2F;axilla-io&#x2F;demo-ui</a><p>And here&#x27;s a video of Nicholas walking through the UI that gives an idea of what axgen can do: <a href="https:&#x2F;&#x2F;www.loom.com&#x2F;share&#x2F;458f9b6679b740f0a5c78a33fffee3dc" rel="nofollow noreferrer">https:&#x2F;&#x2F;www.loom.com&#x2F;share&#x2F;458f9b6679b740f0a5c78a33fffee3dc</a><p>We’d love to hear your feedback on the framework, you can let us know here, create an issue on the GitHub repo or send me an email at nicholas@axilla.io<p>And of course, contributions welcome!

12 comments

mlejvaalmost 2 years ago
Hey Nick and Ben, congrats to launch! I really like that you&#x27;re going in the TS way by default. I personally think there will me more AI Engineers (devs building LLM apps&#x2F;agents) working in TS than in Python.<p>I wanted to ask if you accept PRs for integrations?<p>I&#x27;m a co-founder of E2B [0]. We give private sandboxed cloud envs to any agent. We&#x27;re building two things:<p>- [1] Agent Protocol - it&#x27;s an open protocol that defines how to communicate with an agent. The current goal is to make benchmarking agents simple (it&#x27;s used for example by folks at AutoGPT and other popular agents)<p>- [2] SDK that gives your agent a cloud environment (currently in early access)<p>Would love to figure out how to integrate these to into Axilla if it makes sense to you. What would be the best way to connect?<p>[0] <a href="https:&#x2F;&#x2F;e2b.dev&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;e2b.dev&#x2F;</a><p>[1] <a href="https:&#x2F;&#x2F;github.com&#x2F;e2b-dev&#x2F;agent-protocol">https:&#x2F;&#x2F;github.com&#x2F;e2b-dev&#x2F;agent-protocol</a><p>[2] <a href="https:&#x2F;&#x2F;github.com&#x2F;e2b-dev&#x2F;rest-api">https:&#x2F;&#x2F;github.com&#x2F;e2b-dev&#x2F;rest-api</a> We built for example our ChatGPT plugin with it <a href="https:&#x2F;&#x2F;github.com&#x2F;e2b-dev&#x2F;chatgpt-plugin">https:&#x2F;&#x2F;github.com&#x2F;e2b-dev&#x2F;chatgpt-plugin</a>
评论 #37037970 未加载
评论 #37035833 未加载
评论 #37040627 未加载
jumploopsalmost 2 years ago
We use GPT-4 pretty heavily in a Typescript project, but have noticed lag from the TS versions of popular libraries (OpenAI’s npm lib, Langchain TS, etc.).<p>This framework is exciting to see. Even though Python is the “language of AI” most foundational models just sit behind an HTTP endpoint, making the web (and thus JS&#x2F;TS) a perfect fit, as you’ve called out.<p>It’d be neat to see a caching layer (maybe similar API to evals?) that can be a drop-in for production workflows where the responses are somewhat deterministic.
评论 #37038618 未加载
savy91almost 2 years ago
Amazing! I am working on projexts where we use LLMs and Typescript and and besides langchain-js which can be only described as bloatware, I can never find anything and find myself reinvent the wheel most of the time.
评论 #37036392 未加载
fswdalmost 2 years ago
I&#x27;ve come to the conclusion that anything that &quot;abstracts&quot; the openai complete&#x2F;chat complete API call is just bad practice and to stay away from the entire framework, with the exception of microsoft guidance. Just because you can, doesn&#x27;t mean you should. And if you do abstract the completion API, then it must either reduce friction or increase capabilities over just calling openai with http fetch&#x2F;axios. Which microsoft guidance does this.
评论 #37038485 未加载
评论 #37038906 未加载
评论 #37043681 未加载
rzmmmalmost 2 years ago
Hi, I checked out the demo and it looks very promising. As someone who is not very familiar with AI development, I feel a bit puzzled looking at the code examples. If I use the lib and it sends textual prompts based on some templates, can I be certain that the AI outputs will be well structured and contain the right information? Would it be possible to build an AI model with a lower level, programmable interface...?
BoorishBearsalmost 2 years ago
My two cents which you are free to ignore (and I almost implore you to ignore): I&#x27;m sure this is useful but as someone who works at an AV company and is building with these new generative AI tools... your psuedo-YC story intro kind of puts me off even wanting to look at the library, because it sets you up as grifters.<p>The <i>only</i> overlap with what you were doing at Cruise and the problems people building off a REST API wrapper for an LLM are running into are things that all software being pushed into a production environment runs into. High level things like &quot;let&#x27;s not introduce a regression&quot;.<p>I think if you&#x27;re talking to investors who don&#x27;t know better go for it. But if you&#x27;re posting for technical folks, some of them will be completely put off the moment you try to imply working in MLOps at an AV company makes you any more suited to implement RAG than any suitably experienced engineer who&#x27;s messed around with embeddings for a month.
评论 #37043557 未加载
评论 #37043096 未加载
fullstackchrisalmost 2 years ago
I&#x27;m gonna be that guy who will probably show up sooner or later anyway, but... I can&#x27;t imagine performance can compete with other languages? What were your findings or experience with that?<p>Still, I&#x27;m a huge fan of TypeScript and will give it a try anyway :)
评论 #37039869 未加载
kwanbixalmost 2 years ago
What a horrible name. Why? Just why? You are putting so much love into something to give it a name that is so bad?
评论 #37044449 未加载
fosterfriendsalmost 2 years ago
Congrats on building the library! I’ve recently been playing around with the js implementation of langchain, and I’m excited for there to be more high quality typescript support here.
capitanazo77almost 2 years ago
Feedback: Axila in Spanish means armpit
astrodudealmost 2 years ago
Hi Nick and Ben, Looked at the demo. Great job! I&#x27;ll be trying it soon!
SwiftyBugalmost 2 years ago
&quot;Axilla&quot; in Portuguese means &quot;armpit&quot; (it&#x27;s spelt &quot;axila&quot;). I like the name more because of this. Congrats on the launch! As a developer who&#x27;s been working a lot with TypeScript and LLMs, I&#x27;ll definitely take a look.
评论 #37035570 未加载
评论 #37035640 未加载
评论 #37034927 未加载
评论 #37037289 未加载