Support intro
Sorry to hear you’re facing problems. 
The community help forum (help.nextcloud.com) is for home and non-enterprise users. Support is provided by other community members on a best effort / “as available” basis. All of those responding are volunteering their time to help you.
If you’re using Nextcloud in a business/critical setting, paid and SLA-based support services can be accessed via portal.nextcloud.com where Nextcloud engineers can help ensure your business keeps running smoothly.
Getting help
In order to help you as efficiently (and quickly!) as possible, please fill in as much of the below requested information as you can.
Before clicking submit: Please check if your query is already addressed via the following resources:
- Official documentation (searchable and regularly updated)
- How to topics and FAQs
- Forum search
(Utilizing these existing resources is typically faster. It also helps reduce the load on our generous volunteers while elevating the signal to noise ratio of the forums otherwise arising from the same queries being posted repeatedly).
Hi everyone,
We are currently evaluating the integration of Nextcloud with Google Cloud Storage (GCS), making use of the Autoclass feature to optimize storage costs.
The setup we are considering looks like this:
-
Nextcloud as the main collaboration platform.
-
Google Cloud Storage as the object storage backend, configured via S3 compatibility.
-
Buckets with Autoclass enabled, so that objects are automatically transitioned between Standard / Nearline / Coldline / Archive depending on access patterns.
We’d like to hear about real-world experiences on the following:
-
Practical compatibility
-
Has anyone successfully implemented Nextcloud with GCS in S3 compatibility mode while using Autoclass?
-
Did you run into upload, read, or sync issues (e.g., with apps like Memories, Preview Generator, etc.)?
-
-
Latency & performance
-
Have you noticed delays when accessing files that Autoclass moved to colder storage classes?
-
Does user experience in Nextcloud suffer when files are pulled back to Standard?
-
-
Costs & operations
-
Did the automatic class transitions in Autoclass generate unexpected operation or retrieval costs?
-
Any best practices on which buckets should use Autoclass vs. those that should remain Standard only?
-
-
General recommendations
-
Is Autoclass worth it for mixed-use scenarios (active + archival files)?
-
Or would you recommend manually managing object lifecycle policies instead?
-
I’ve read some reports that Nextcloud may not play nicely with GCS in S3 mode, so I’d love to hear if anyone has this running stably in production.
Thanks in advance for sharing your insights!