Vikunja as a business

[kolaente]

Thanks again for the comments!

@Wasabi

From a non-profit perspective, we’re more often than not faced with the situation that we actually need “Enterprise” features.

As someone being active in a non-profit organization as well, I know the problem all too well. I think you can answer the question “what exactly is a non-profit” by saying “all accredited entities like e.V. or equivalent”. That should cover the majority of cases. To cover the Fraunhofer case, you could also add a clause about having employees, etc. I wonder how Atlassian and others are handling this?

@Wasabi

This is my last point - I’m not entirely sure how many contributors you have, that either contribute code or help in the forums - how would that continue that journey? Ideally I’d hope there are no changes, just curious what’s your thoughts on that.

Yes, that would not change at all. The new paid-for features would be source-available, but under a different licence than the rest. I won’t do a relicensing of existing code. It would even be possible for people to contribute to the enterprise stuff, but would require a CLA.

@PatrikStenmark

I’ve been thinking about starting a non-profit organization for helping other non-profit organizations with their IT systems, and was considering using Vikunja as a first PoC. Reading this post got me thinking.

There are ones doing this, like Local-IT - they all need to find ways to make money, as hosting costs money and there’s no way around that. Then the other thing is you can get Google Workspace or Office 365 for free if you’re a non-profit org…

@PatrikStenmark

I’m thinking that an enterprise/company organization with 90 users would be pretty active during work hours, but a non-profit account with 90 users would have way less activity, and spread out over the day.

Good point! There won’t be any restrictions on that regarding the licence, only the hosting requirements for the org would change.

@PatrikStenmark

This would make it possible for you to handle paying clients and make money of the companies that are for-profit. You would help non-profit organizations. But you wouldn’t have to care about the actual running of the Vikunjas that they use, that would be handled by volonteers on a non-profit base itself. I would think that this wouldn’t result in any huge monetary loss, since most non-profits can’t pay that much anyway…

I’m not sure if I / the Vikunja project could participate in such an org, but I would help if I can!

@mynameisnothing

I plan to use Vikunja for personal tasks and my family. It would be great if you could provide the full functionality for small teams (e.g., 5-10 members). This would allow organizations to test the complete feature set before committing to a paid subscription.

I’m honestly wondering what use-case do you have in that case for the enterprise-only features? What could you do with it that you can’t already do with the OSS-Version? How important would you rate those things?

In any case, there will be a trial period to test the features before committing to a payment.

@mynameisnothing

Additionally, you could offer integrations with services like Slack, MS Teams, and Figma as premium features

Do you have anything in mind specifically?