Learn how ownCloud and Twake Drive differ in their key features, development activity, technology stack and community adoption, so you can decide which of these cloud file sync & share tools is best for you.
Last 30 days
Last commit
5 hours agoRepository age
7 yearsVersion
v8.2.2License
Apache-2.0Self-hosted
YesRepository
owncloud/ocis
Last 30 days
Last commit
4 hours agoRepository age
10 yearsVersion
1.108.0License
AGPL-3.0Repository
linagora/twake-drive
ownCloud appears to have several advantages over Twake Drive, particularly in popularity, growth and features. Consider your specific needs regarding popularity, growth, activity, technology, maturity, licensing and features when making your decision.
ownCloud leads in popularity with 2,167 stars vs 990 stars for Twake Drive. The 119% higher star count indicates stronger community adoption. In terms of developer contributions, ownCloud has 283 forks, indicating moderate developer engagement.
ownCloud is growing faster, adding 37 stars in the last 30 days (+1.7%) against adding 3 stars for Twake Drive (+0.3%). ownCloud is both larger and pulling further ahead.
Both projects show recent activity, with ownCloud last updated 5 hours ago and Twake Drive 4 hours ago.
Both tools share common technology foundations, being built with JavaScript, Typescript. However, they differ in their additional technology choices: ownCloud uses CSS, Bash, Python, Golang, SCSS, PHP, Vue while Twake Drive leverages JSX.
Twake Drive has been in development longer, starting 10 years ago, compared to ownCloud which began 7 years ago. This 2.7-year head start suggests Twake Drive may have more mature features and established processes.
The projects use different licenses: ownCloud is licensed under Apache-2.0 while Twake Drive uses AGPL-3.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Cloud File Sync & Share.
ownCloud provides self-hosting options for complete data control and customization, while Twake Drive may be primarily cloud-based or require different deployment approaches.
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs
vs