I was wondering how easy and reliable it is to work with NextCloud in any professional setting. Does it put too much maintenance work on DevOps to a level that makes just using things like dropbox the standard way? I read that German government uses nextcloud because it offers better control over data. Do the companies care about this matter too? or should I just learn big cloud alternatives?
Old school dinosaur that still advocates for private cloud solutions, here.
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.
True, but now you've got to take the time to manage a non-standard groupware and collaboration suite from the perspective of an administrator, as well as onboarding your staff to something they're unlikely to be familiar with. All of this costs time, which startups don't necessarily have or is better spent trying to grow the business or solving harder/more pressing problems.
Look, my job would be a lot more lucrative if I could convince the C-Suite to self-host everything on-prem again. The reality is that startups need to run lean and mean until they've got reliable revenue coming in, and this is where "off-the-shelf" solutions are going to win out over bespoke offerings.
Is it doable? Sure. Is it affordable? You betcha. Is it sensible for a startup? I'd probably say no.
I'm not sure what you mean by "nonstandard". Next loud implements standards like webdav, carddav, caldav, email (smtp, etc) and others.
Your staff may be familiar with Office365, Google Workspaces, Nextcloud, or any number of solutions, or none at all. So you will still have to leovide some level of training and support.
Not being locked in provides startups with ghe flexability they need, and the standards Nextcloud implements makes it even more flexible.
You're right, and I should clarify: non-standard from the perspective of an AMER Enterprise IT Engineer, and specifically from a talent acquisition perspective. I don't doubt you could train staff in NextCloud's offerings, but again, the point I was making is that it's probably not the best solution for a startup if you want to make sure time is spent solving the challenges of your product, rather than the challenges of the underlying corporate kit you've chosen to adopt.
As for locked-in..._eh_, that's both fair (Google and Microsoft both have abysmal data exfil capabilities) but not as valid as it used to be (there are gobs of startups whose entire schtick is automating your exit strategy from a "locked-in" vendor). By the time vendor lock-in for your corporate IT is a concern, you've likely got the capital to splash on an actual, dedicated Enterprise IT team.
Preaching to the choir! I love the convenience of public cloud offerings, but unless you're billing a customer for your consumption + margin or hosting something itsy-bitsy that can fit into burstable or low-resource instances, it's undoubtedly going to be cheaper on-prem or self-hosted in the long (3+ years) term.
At our startup, we rely on nextcloud (self hosted on a root server from a German hosting provider) + libre office for all of the more „mundane“ parts of our business. To be fair though, we’re in a very niche market (offshore wind) running at a very different speed compared to your regular startup. It’s been a conscious choice to run everything on foss and self host as much as we can. Big plus for nextcloud: the sync client works reliably even on intermittent and extremely slow connections (offshore). The overhead of maintaining nextcloud ourselves is manageable (yet another docker container) and it’s been astonishingly reliable ever since we got started. For us, maintaining control over data is paramount, so it matters greatly to us. If one day the overhead should become too much, I’d probably move our nextcloud over to a nextcloud provider.
> I’d probably move our nextcloud over to a nextcloud provider.
I recently moved (from Contabo to Hetzner), and I struggled to migrate NextCloud. I ended up creating a new Nextcloud container and re-uploading the files. I did have some more unique setup (trying to move from Caprover to Coolify, and the Coolify NextCloud image was using sqlite instead of MySQL for the NC database). If you migrate, just make sure to back-up the files locally first in a different folder, because the server is authoritative, so if on the new server the files are missing, they will also be deleted locally.
It's nice to hear you are dedicated to self-hosting. If you ever need a self-hosted Hotjar alternative, check out my UXWizz platform :)
When I worked at a smallish company, we were upgrading our email calendaring system from a homegrown thing to some better.
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.
I love many things about the hacker ethos, but after being in tech for several years, I’ve learned the following painful lesson:
Do not self host. The only thing you should ever self host is software your company wrote; unless you have a dedicated team for that specific piece of software alone.
You will never meet the uptime of Google Workspace. Your tools will never have less bugs. You will never meet the security certifications. Your real-time document editing, which may you think doesn’t matter, will never meet your employee’s expectations. You will never have as good tools for automated legal compliance. And if it goes down, which it will, even a day of downtime is more expensive than years of Google Workspace in all but the smallest of businesses. Additionally, every time something doesn’t work (or, heaven forbid, you’ve been hacked), your company’s employees and lawyers can and will blame you instead of an unmovable entity.
> Additionally, every time something doesn’t work (or, heaven forbid, you’ve been hacked), your company’s employees and lawyers can and will blame you instead of an unmovable entity.
That's what it's really about. Modern day "nobody ever got fired for buying IBM". It's not about the better solution, it's about blaming someone else if things go wrong.
Azure has been completely hacked twice now, yet people still move their shit over to Microsoft's cloud offerings. I don't understand how fucked in the brain you have to be to consider this a good idea, except for being able to shift blame.
It doesn’t matter if it’s fair, it’s just reality.
If you self-host for a business, and your self-hosted instance is hacked when other self-hosted instances of the same software weren’t, you are at risk for legal action and a possible criminal investigation. Was it really the software that was hacked, or were you negligent? Was it truly an accident, or did you have malicious intent? Plus, define negligent - does not having a service like CrowdStrike installed count? (You might say, “obviously not,” but if it takes $50K to convince the court on that point, shallow victory there.)
If you have a family, even if this is only a 10% chance of happening, you would have to be, in your own words, “fucked in the brain” to put your livelihood and career on the line to save a few bucks.
In my ideal world, beer would rain from sky and nobody would ever get drunk. We’re not in an ideal world, and “CYA” is a valid reason until you have a proper, large, dedicated IT team.
We completely agree here. I just don't think that's how it's supposed to be. How could Microsoft get away with this? They should pay billions in damages or penalties. And specifically, anyone who decided to move anything to the Microsoft cloud after the two hacking incidents should be treated just like someone who ran a nextcloud instance and got hacked, should Microsoft be hit a third time.
I can understand the attitude, but personally I don't second it.
I think the better question is: Do you care enough to divert some time away from building your product?
Some folks might be really motivated by not going with Google Workspace. Others don't care at all. There can be great motivational effects in doing what you think is right, I wouldn't discount it as a purely economical decision. Sure, tools need to be efficient, but we also need to enjoy them.
There’s also the leadership capital lens - you will 100% annoy a significant percentage of the org implementing a non standard data solution. That will come back to bite you down the line. Choose your battles.
Depends on your workers and also the kind of company you are. If you're building a privacy-conscious product and you've recruited people that share the same values, they'd applaud you not going for a cloud solution. I certainly would.
I think this viewpoint would be more common here in Europe.
And our conpany's O365 also has significant downtime. We've had several major incidents in the last months alone (one of which was the crowdstrike related one, which we don't use but apparently Microsoft do)
If you care less about spending any amount of time on your product than whatever it is you emotionally get out of hosting Nextcloud instead of using Google Workspace, beware.
This is not about Nextcloud vs GW. The spooky bit is that you consider taking on additional burden with something that will not improve your product in any way, when your product is the only reason why your startup maybe exists in the future.
That's a particularly dangerous habit to pick up, because you will have 1000 chances to make meaningless decisions and distract yourself every day.
Unless you have an extremely convincing reason to do something — and if you are wondering, you don't — don't.
Also, while this decision is easy, other choices are nuanced. Kubernetes or EC2 or managed containers or Firebase? I say there is no clear winner for all use cases. But if you are spending innovation tokens (or fractions of) all the time these choices get even more muddy.
First to market/move fast mentality will never consider it. And it’s usually over something that doesn’t really matter like this. Let people have their nextcloud!
EU is worried about the European data stored in US (for good reasons). They don’t want their digital assets leave the region, even if the American services are good.
The price is also not $10 per month. You have to increasingly upgrade for features that Nextcloud offers for free, particularly if they are used by enterprise (like multi user accounts).
All you have to do is read the commentary here to know this probably isn’t a good idea in a large work setting unless you have dedicated IT staff to support it.
Yes but, in a business environment, you need to have dedicated IT support for anything you're self-hosting. Things can go wrong even with the most stable piece of software, and you need to be ready for that. SAAS' main selling point is that they take away the maintenance burden from you, while the advantage of self-hosting is that you're the one in control, at the expense of having to maintain the thing yourself. Then some softwares can require more maintenance than others, but needing IT staff if you're self-hosting isn't specific to Nextcloud.
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.
Driven by my ideals and my previous horrendous experience dealing with Microsoft and Google support, I've been a strong advocate for self-hosting in my organization. I do not think companies should put something as valuable as their collaboration and communication in the hands of a company as inconsistent as Google or Microsoft.
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.
Well... An IT startup should have no need of NexCloud/O365/Google suite and so on, simply because techies know how to share files and produce documents in way much better ways.
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.
Hardly any "devops" work needed to keep it chugging along. My installation is ~10yo and don't remember a failed update or serious mishaps, then again it's just the family using it, so very standard usage.
It really depends. At my first job it was used with some success, but we were a PaaS, with few employees and a hard limit on costs (at least the two first years, then we were profitable enough to probably upgrade but it was integrated enough). It was just after they forked themselves too, so it wasn't as feature-complete as now.
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.
I have used both Own- and NextCloud in professional environments and it works fine. I had less issues getting it to work than a Domain-attached SMB storage. It's really important to know what you expect from it, but for a cloud storage & sharing solution it doesn't really have any drawbacks. As with most self-hosted software, you need someone to keep an eye on it and back it up from time to time. If that justifies paying Google to do it for you, that's also a reasonable proposition.
In my opinion it’s not a good alternative if you or your team members expect exactly the same quality of service. When you switch to Nextcloud you’ll have to expect more bugs, less reliability, less performance and obviously more maintenance (since it's typically self-hosted) compared to Google Drive, Dropbox or One Drive. So you'll have to go into this with a different kind of mindset. What you gain is independence, privacy and extendability due to a rather big platform ecosystem.
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
- 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.
> - 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
What about onlyoffice ?
Can you confirm your experience comes from a nextcloud instance and a collabora instance on two different servers ? What was the bottleneck ? Network traffic ?
It's been a while since I used OnlyOffice, can't really speak to its performance.
I think mostly the sluggishness comes from some input delay in the browser. When you open a Collabora Calc document and select any random cell, it just takes a couple of hundred miliseconds till the cell is actually selected. I can reproduce this with brand new instances, no matter how beefy the server is.
I find it’s when you build customizations that break in a version change where this will shoot you in the foot. Make sure it’s well supported for whatever plugins/customizations you need and out of the way and everyone will love whatever self hosted solution you introduce. Don’t go plugin crazy you’ll trap yourself when you need cross functionality of some sort.
There are companies that will host and support Nextcloud for you, so it does not necessarily mean any additional burden on Dev-ops than any proprietary Sass solution. And if your provider doesn't meet expectations (or stops meeting them) you can migrate to a new one with less difficulty than changing software completely, as you would with proprietary Sass.
I think this is the best of both worlds. You can be as hands off as you want today, yet still have all the same ultimate control benefits as self hosting.
Give that 5th or 6th 9 it's proper due (almost none almost always) and life gets quite simple and manageable and efficient and your tools provide value instead of extracting it.
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).
it works quite good. Used it in my previous gig. All documentstion and design libraries of the company (of 100+ people) were in Perforce. Everything was on AWS.
It's a joy to browse the design library and do code reviews with Swarm as a plus.
I think so but there are generally two competing philosophies. One is that startups should leverage cloud services as much as possible because of their relatively low resources required to get off the ground.
I think selfhosting open-source services is more useful for niche SMB's that specifically require on-prem data.
I see a lot of comments shying away from self hosting, to keep focused on your own product, or wanting the ability to shift blame onto the big providers when things go sideways. There are hosted Next Cloud options, has anyone had experience with these good or bad?
My main desire in trying NextCloud was syncing files with a handful of people, as a free software replacement for Dropbox. All of the other features were nice to haves.
I've tried several of the "budget" NextCloud hosts. I'm not going to name names, but all of them were very disappointing. File syncing frequently broke in hard to diagnose ways. And from a perspective of overall service, I would get 502s, 503s, or 504s far more often that I should have. This was with multiple budget providers. I didn't try any of the more expensive providers, because I couldn't afford it, so maybe this is a "get what you pay for" situation... But in theory, the size servers I was paying for should have been able to handle our traffic volume.
Anyway, after a couple of years of trying to make hosted NextCloud work for us, I gave up and bought Dropbox's paid service and haven't had any issues with it.
We use Cryptomator on top of Dropbox to ensure data privacy, by the way. Back when we were using NextCloud, we had been using their end to end encryption plugin until we discovered a silent failure mode in which it was uploading documents in plaintext to the "encrypted" folder. I believe nowadays the recommendation even for NextCloud is to use Cryptomator on top, rather than their built-in encryption.
It is great to have a Drive-like user-friendly UI to your shares (web, mobile apps). But don't do the syncing with it, there are more mature/robust solutions like SyncThing or rsync.
Self-hosting is no big deal but NextCloud -- from what I've seen -- is not very good. Used by the German government is not the recommendation you might think it is.
I was reading about this. It depends on a lot of things, however if you want end to end encryption, only cryptpad and seafile seem to have this capability.
Running a service is one thing. Keeping it reliable and secure is another. Especially if you are a start-up. You have limited capital and even more limited developer time. Don't waste either on building your own infrastructure.
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.
This advice is repeated constantly, and it’s taken as gospel.
If you / your team know what you’re doing, you can absolutely run your own stuff without it being a nightmare. I’ve worked at a 9-digit-ARR SaaS where we ran our own servers (as in, we owned physical servers, not a VPS), ran our own networks, etc. Everything was in IaC. There were shockingly few incidents compared to literally every other SaaS I’ve worked at since.
We didn’t self-host email / file sharing, to be clear – that’s a fool’s errand due to IP reliability rules. Google Workspace is great.
I’m not trying to specifically call you out here, I’m just trying to counter the general argument that it’s impossible to do what the big providers do while still having a reliable service.
I don't disagree - there are people who are capable and willing to put in the effort. But I don't think that's most people - especially people asking how to do it. There's a lot to know about how to do things properly, so if you don't have at least one person who has been there and done that, I think it's not worth the effort.
I've worked at multiple small companies now where all our document storage and organization needs were met exclusively by GDrive.
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".
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.