Swallow your pride or curiosity on rolling your own kit and accept the reality that OneDrive/Google Drive/Dropbox/Box.com/et al are going to be better for your needs. The single biggest benefit of SaaS products are their flexibility to provide service when you can't or don't want to support the deployments yourselves, which is basically startup mode.
Once you're off your feet and have an honest-to-god Enterprise IT team with a budget, let us deal with it. They'll likely keep end-user storage in a Collab Suite (M365, GWorkspace) unless there's a specific advantage or requirement for your business needs in running it on-prem.
Everything is a tool, and the use-case of these tools is in freeing you to solve the really hard problems of startups, i.e. survival, success, and sale/solvency.
In my young year I was pushing for something like this, an off the shelf self hosted system. I was worried that slinging it out to a thirdparty would be both expensive and bad for my career.
However I was wrong. Much as it was a dick to set up, migrating to Google (workspace? fuck knows what it was called) was totally worth the money.
At newer companies I've look at self hosting, but I just don't want to be on the hook for securing the stuff, or dealing with the email deliverability when some marketing prick does something stupid.
OwnCloud and such wouldn't be considered a mainstream resume skill, and comes with its own upkeep and maintenance, along with ownership of the entire backup/restoration process.
However, ideals aside. In many large companies, using Microsoft or Google products can also be a compliance headache (that is, if you're outside the US). A larger corp is more likely to be hit with such issues than a small startup.
Also, self hosting of course requires resources. I'm not talking about compute, in my experience that is very negligible. It of course requires people to keep stuff up to date and learn how to use it to its fullest extent. A larger enterprise can more easily afford this effort than a small startup. Even considering my idealistic stance, it is hard to ignore the low cost of entry as well as the ease of getting started with the big cloud offers.
that doesn’t only apply to google workspace, it also applies to things like payment processing, auth, etc.
Staten that, as a POOR solution to collaborative works on documents NexCloud/O365/Google suite might be "good enough" for some, NextCloud is not on par, but near, the burden for IT is simply the fact these products are monsters alone, essentially impossible to really knows entirely in codebase terms, complex to heal when trouble happen etc.
So yes NextCloud could be used in professional settings, and owning their own infra is better than living on someone else computer, but the real point is if your employees really need such tools/paradigm or not. Someone in IT could collaborate with a shared repo, notes, makes slides in org-mode and so on. Someone much less skilled could still use BookStack and alike. Only end-users already trained on office-like stuff could like these monsters.
Now, I would not use it unless you have to follow ISO norms/get governmental agreements for any company with enough money. If you're a three-person startup with one client barely paying two salaries, trying to find a bigger market though, go for it.
E.g. here are some specific things and examples of things you'll have to deal with, in no specific order. These are just some things I've had to deal with recently.
- You'll have to educate people in your group that there are at least 3 different ways to share files among each other and that they can all coexist in parallel (Individual Shares vs. Group Shares vs. Group folders vs. Circles/Teams) (I did a german blog post on this: https://bitbetter.de/blog/nextcloud-freigabe-chaos/)
- Handling of file/folder names with special characters is a mess e.g. if you have Windows and Linux clients there will most certainly be conflicts. (Luckily this has been fixed recently by the `forbidden_filename_characters` config option – which is not enforced yet via the Web UI) see https://github.com/nextcloud/ios/issues/2802
- Creating Nextcloud users with spaces in their names, will break CalDAV on iOS Devices (https://github.com/nextcloud/server/issues/15641)
- Nextcloud (aka Collabora) Office is very slow if you want to actually work collaboratively with it (no matter the power of your Collabora server) – unfortunately it's no match for Google Docs or Office 365
Don't get me wrong: It's still a fantastic Open Source project with tons of talented people and it's a beacon of hope in the GAFA world. Everyone should try it out (and help it evolve) so it can be better than the commercial alternatives. But going into this and expecting to get the same kind of product quality like Google Drive/One Drive/Dropbox will lead to disappointment.
If you're already using it for large file version control for, e.g., gamedev, and don't mind the cost, how well does it work to store all other company documents? I'd assume it has better scalability and permissions management than Nextcloud (not to mention the version control on par with git).
IMHO, having the diversity in storage and computing would help the current tech world a lot.
I think selfhosting open-source services is more useful for niche SMB's that specifically require on-prem data.
If you are worried about someone stealing your ideas, don't be. First, nobody cares about what you have until you make it big, which is going to happen a long time from now if ever. Second, the major services all provide enterprise deals that ensure privacy, enough that the largest companies in the world and many governments rely on them. You are far more likely to be hacked if you try to roll your own than if you use a popular service - especially if you aren't an experienced IT admin.
If you are in a start-up you want to put your full focus on your product - don't waste time on infrastructure. Use popular online services, use popular brands for hardware, use popular languages and popular libraries. Use anything you can to get you going as quickly and as painlessly as possible so you can focus on building your product and your business. That's going to be hard enough.
I say this as someone who worked with a start-up from inception to being acquired 10 years later. I was the guy building the networks and the servers and the desktops. We cobbled together our own systems from white box parts and using free software that required lots of setup and maintenance. I spent a lot of my time maintaining that stuff instead of working on our products. When we got acquired, the first thing they did was throw all that stuff out and switch to their existing systems that were all the well regarded name brands that you know. Since then, everything just works.
I won't say it's a good solution for everyone. If you have strict documentation needs for industry reasons, it's going to be hell for your workers. Good luck finding anything you need. Good luck getting people to follow a consistent format, or hell, even a compliant format.
... DevOps shouldn't be deploying, administering and maintaining something like NextCloud.
And honestly without any additional input this question sounds like "I worry what I would be in a position when NextCloud wouldn't be able to support the needs of 10000s users. BTW currently it's me myself and my dog in this startup".