MoroJS

Your problem isn’t tools, time, or knowledge. It’s that you quit every project at 70%.

So I bought some cloud compute last night with the goal of providing my companion agent framework as a service for users who don't want to run it locally or deal with API keys. The project is first and foremost DIY and open-source. From what research I did on the SL Marketplace, I'm in no way trying to compete with Lifebots or Smartbots products or the host of greeter and special purpose bots. This project is more akin to having a companion ala Kindroid or Replika. The user can fully self-host this framework, even run an Ollama model locally, which makes it virtually free. Or, with my framework service, pay a small monthly subscription for hosted runtime, token accounting, SL & Discord relay, expanded memory, persona design & hosting, UI logs (see what the agents sees), uptime monitoring, and customer support. The user only has to provide an API key for Claude (more LLM options coming) and run their agent avatar locally.

In nestjs framework we can build libraries for a project, it lives in the libs folder. Core is the library name, and the src for that core library lives in src. The main src is the project source code, it's mainly for modules. So this way i can probably create one more storage library in the project and there will be one more source folder. I think this is good in terms of organising the code.

This is a backend built with: Node.js Express MongoDB And React for the Frontend. But the goal wasn’t just CRUD… It was to simulate how an actual banking system behaves

Hot take: The framework that gets the most GitHub stars is almost never the framework that survives its first 10,000 production requests. Stars measure excitement. Production survival measures error handling, state persistence, and what happens when a third-party API times out at 2 am. Pick your framework based on its worst day, not its best demo.