It s been a week since we launched Ovren - and I just want to say a genuine thank you.
We built Ovren because every team has backlog work that never makes it into a sprint. Not more ideas. Not more AI suggestions. Real engineering work that needs to get shipped.
So we launched Ovren as an AI engineering execution product for real backlog tasks: AI frontend and backend engineers that work inside your real codebase, execute scoped work, and return reviewable code updates.
There's something counterintuitive about building an AI product in the mental health and self-awareness space: if you're doing it right, your users should eventually need you less.
Most product teams optimize for stickiness. More sessions, more time in app, more daily returns. But at Murror, we've been wrestling with a different question what if the goal of our product is to help someone build enough self-understanding that they don't need to open the app as often?
I've been building my app for 8 months now, and i ended up having 5 repositories
nextjs app
databases
customer facing API
node-sdk that wraps the api
react-sdk, for both reusing shared component and customer facing components
So i thought, it's gonna be great if i create a mono repo with submodules. But it was terrible. I realized that turborepo does not like external packages, and as i tried to reuse my own customer facing libs, the DX became terrible. It was very time consuming to ship a feature. Even when i wanted to use Codex or Cursor 3, it was not able to show git diff properly, also i was not able to use Cursor's cloud agents properly to ship complex features.
