Formulating it a bit provocative: In what way is it more than an expensive cookiecutter repository? (Especially with a one-time-use policy per subscription)
Me too — trying to figure that out!
> but that project needs to be basically non existent while also being somewhat serious
Super interesting point. I've helped integrate it into some existing projects and it is not fun.
> In what way is it more than an expensive cookiecutter repository?
I don't disagree with this. A couple differences in my mind are support (that you're paying for, and has an incentive to be as helpful as possible) and on-going updates (a cookiecutter won't help you integrate improvements over time, as far as I know).
Pricing is totally an experiment right now, and I shot high on purpose. Suggestions?
Absolutely true. I remember the amount of hate HN spewed at Docker for making their desktop app /paid/ for Corp users.
> support (that you're paying for, and has an incentive to be as helpful as possible) and on-going updates (a cookiecutter won't help you integrate improvements over time, as far as I know).
That's true, good point.
> Suggestions?
I think it highly depends on your target audience.
> Things like django-coookiecutter are great, but they only really cover the project structure.