Love the idea. I love there are people working on this kind of tool.
My biggest question is where the data is stored. I think the storage model for the comments should be mentioned in the FAQ. If it is on your server only then I don't think I'd use it.
I would ideally like the comments to be stored as metadata files committed to the repo or inline with the code. I'd probably therefore prefer a tool-user-based pricing model. And I think $100/y would be a fair price per user.
I don't get the repo based pricing. I could have a repo with a single docker file in, or a repo with a million lines of C++. Having a lot of repos forces me onto the expensive per-user licensing. It would be ok at $100-$200 /y but $69/m === $828/y seems too much. That's 1%+ of a senior dev's salary in most part of the world, for one tool.
Thanks for your feedback! This is the reason why we posted our work on HN. I really appreciate it!
You won't believe, storing Nots data as a separate git repo or as a metadata was our initial thought when we were starting the project. But it quickly became clear that it's too complicated, pollutes the repo, hard to query. Lots of downsides.
But we know that everything you entered is your data, and we cannot lock you on the service. We're thinking of one-click export of your current docs snapshot as a nicely formatted HTMLs. Maybe even make a recurring task of sending such snapshots by email once in a while. Will figure it out. Stay tuned.
As of prices, it's a fair point. Now it's clear that we have to review per-user prices. And you're right, something around $100/y is fine. Thanks for your suggestions!
Looks like you have run up against a shortcoming of git itself. I accept that you may need to store the data on your end for those reasons. If this is the case it might be worth having that in the FAQ too, and convince me that you ensure a decent uptime and that you can export the data nicely if you want to move on later.
Love the idea. I love there are people working on this kind of tool.
My biggest question is where the data is stored. I think the storage model for the comments should be mentioned in the FAQ. If it is on your server only then I don't think I'd use it.
I would ideally like the comments to be stored as metadata files committed to the repo or inline with the code. I'd probably therefore prefer a tool-user-based pricing model. And I think $100/y would be a fair price per user.
I don't get the repo based pricing. I could have a repo with a single docker file in, or a repo with a million lines of C++. Having a lot of repos forces me onto the expensive per-user licensing. It would be ok at $100-$200 /y but $69/m === $828/y seems too much. That's 1%+ of a senior dev's salary in most part of the world, for one tool.