[_frkl]

I would not write my own license. I'd really recommend you get a lawyer look over the text you have (that shouldn't be too expensive, it's a one time cost), or look at existing ones that are actually written by lawyers. For a public license (to restrict commercial use), I'd recommend both LicenseZero Prosperity ( https://prosperitylicense.com/versions/3.0.0 ) and the Polyform licenses ( https://polyformproject.org/ ).

For the private license, you could use/adapt the LicenseZero Private license ( https://licensezero.com/licenses/private ).

Those are more geared towards developer tools, so I'm not sure whether they'd be a good fit for your product. But all of them are written in simple to understand language so you should be able to figure that out by youself, and at the very least get a few pointers. If not, that is considered a bug with the license, and both projects are very open to feedback.

[cxr]

Obsidian folks: please don't use any of the aforementioned licenses. The reality is that they're _not_ a good fit (although the author would probably love to get you as a client to handle your EULA and convince you to use one of the others for your eventually-open-source plans, and that would be an even worse idea).

[_frkl]

Why are they not a good fit? From a shallow reading, I thought Prosperity and the Polyform licenses would be fairly similar in intent to the licenses they have on their page. I can't imagine the authors (not author) of Polyform/Prosperity would care either way, and since nobody ever claimed those are open source licenses I don't understand your other ill-made point either. Maybe you refer to the Parity license? That one would make no sense in this context at all, and I doubt anybody would suggest it here.

Also, since your post is fairly negative and unsubstantiated overall, would you care to suggest an alternative?

[Aeolun]

Give them an alternative?