FOUNDER'S NOTECode is only part of what ships.
The datasets, builds, binaries, model artifacts, media, and other files that applications depend on tend to live across object storage, cloud drives, local folders, and one-off scripts.
I kept running into that problem in my own projects. The files were there. The tooling around them wasn't.
So I started building Repozit: a developer-first platform for storing, organizing, and serving the assets your code depends on - through a dashboard, CLI, SDK, and API.
The idea is to give those assets a proper home in the development workflow.
We've also built formex, a product built on Repozit that turns forms into organized data and asset workflows. For example a recruitment form can collect applications, CVs and attachments and automatically organize each applicant into a dedicated Repozit folder. So Repozit becomes the storage and ownership layer behind workflows, while products like Formex demonstrate what can be built on top of it.
It's early, and that's intentional. I want Repozit shaped by developers who actually have this problem.
Use it on a real project. Then tell me what's missing.