[blagie]

My advice would be to have two versions:

- Paid, which supports private designs.

- Free, where every design is open-licensed and discoverable.

There are approximately zero companies which will want their IP open. On the other hand, this makes this available to approximately 100% of the university and hobbyist market.

Don't cripple the free version in any way beyond that.

The one lesson I learned watching CAD and other professional markets for decades: You want your tool used in university classes. Heck, if there weren't conflicts-of-interest, it'd be worth paying universities to adopt your tool.

Hobbyists are less important (although there have been many examples of hobbyist projects turning into major companies).

[javajosh]

That's a fantastic suggestion, blagie! I really like how requiring open licenses increases the marketing reach of the tool.

[DHaldane]

This is the classic SaaS CAD tool approach. But JITX runs locally - all design data stays local and we're not holding it hostage in our cloud.

Definitely agree with a free version though - we want to help those just starting out as well! But they needed the support from the router we just shipped so earlier offerings would have fallen a bit flat. In the cards now though...

[blagie]

shurg Make a free version which keeps all data locally AND uploads a copy to your cloud (at least for internet-connected machines). Upsides:

- Marketing / visibility: You're a repository of free designs

- Network effects: If people want to reuse designs, they will standardize on your tool

- Training data. Want to know a pin on a given chip is SCK or 3.3V? Or which pins, by default, to connect between a USB chip to program a microcontroller? That's in your library.

- Component library. If I make a footprint, Spice model, and 3d model for some part, you can get it for free for use by paying customers.

- ...

Yes, it can be circumvented. But the truth is 75% of businesses won't break your license anyway. Some will (and there's an obsession with dongles and what not), but those are mostly tiny fly-by-night operations which aren't likely to buy a $12k license anyway.

It is a lot of work, and I'm not advocating for where this should fit on your priority list, or how much is needed in an MVP. Just that you should consider this as perhaps the right long-term model.

[nyanpasu64]

Does this create a problem if schools prevent students from posting their projects publicly (because it would allow other students to "cheat" and look at previous students' solutions), and such projects are no longer considered open-licensed here?

[themoonisachees]

I'm pretty sure the product is already "paid" if you have a .edu email.