server

nextcloud/server

☁️ Nextcloud server, a safe home for all your data

Ship status

Still shipping

Pushed in the last 30 days.

Last push
Oct 3, 2026
today
Ship score
100/100
How it is calculated →
Stars, last 7 weeks
Stars, weekly: 36,468 → 36,949 (Aug 18 – Sep 29, 2026)
+299 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
37K
Forks
5.3K
Open issues
3.7K
Watchers
549
Primary language
PHP
Created
Jun 2, 2016
Owner
nextcloud · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 28 startups in the directory ship primarily in PHP.

Topics

#cloud#collaboration#decentralized#design#distributed#enterprise#federation#file-sharing#free-software#hacktoberfest#javascript#nextcloud#open-source#opensource#owncloud#php#self-hosting#sharing#usability#ux

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 99%, self-hostable 95%, hosted offering 92%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: shipping — last push 2026-10-03This is the badge for nextcloud/server, as served from the URL below.
[![OSSEAN: shipping](https://ossean.com/badge/nextcloud/server.svg)](https://ossean.com/nextcloud/server)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.