[eirikbakke]

Thank you for your thoughtful comment!

I always thought of relational databases as a tool for businesses; normally we don't need them as individuals--except perhaps when planning a wedding! Thus the pricing is targeted for businesses and people who get reimbursed by their employers. A second group might be contractors who purchase their own tools.

There might be ways to make a separate tier for private or occasional use, though. And recurring vs. perpetual might be a separate question from the actual total expected cost.

[AlotOfReading]

It's a very different conversation when an engineer goes to their manager and says "I think this tool I tried out at home could improve our work" versus "we should buy everyone licenses for this tool that I've never used".

[edlinfan]

Should you be interested in doing so, my suggestion would be to offer an "offline" version. It could be feature-limited as follows:

1. Do not include the planned online collaboration features.

2. Support only Excel, Access, CSV/TSV, and Sqlite data sources.

Charge a fair one-time license fee for this, and you would create an attractive tier for individual power-users, without cannibalizing subscription sales of the "online version" for businesses and contractors who care about collaboration and interacting with large production databases.

Just my $0.02.