DiscoDrive for companies

Your team’s files, calendars and contacts on your own servers. You can run DiscoDrive in-house or hand it to us.

Discuss your projectWays to work with us

Email info@discodrive.app with a few words about your team and what you need.

Licence

DiscoDrive is distributed under PolyForm Noncommercial 1.0.0 (source-available).

Non-commercial use is free. Companies sign a separate agreement with us, whether for internal use or as part of their own product.

Your engineers can read the code before you decide anything, and ask us about deployment, security and support.

Source code and the licence text on GitHub

Ways to work with us

Anything from a licence alone to a server we run entirely. Scope and terms are agreed case by case.

A licence for your own servers

You install and run DiscoDrive yourselves; we grant the right to use it commercially. Data and administration stay with you.

Your own brand

DiscoDrive as part of your product or service, under your name and design. The amount of customisation is up for discussion.

A server we maintain

We install DiscoDrive and keep running it. Where the server sits is decided together.

Deployment and support

We help launch the system, move data and connect employees. Support terms and SLA are fixed in the contract up front.

For corporate customers

On top of everything described on this site, corporate customers also get:

  • Single sign-on through Keycloak: staff sign in to DiscoDrive with their company account.
  • S3-compatible object storage as the primary file storage.
  • Integration with the systems and infrastructure you already run.

Which of these you need is agreed during deployment.

Where the data lives

By default, on your disks, in ordinary folders. Stop the service and the files stay put, readable as usual. Corporate deployments can keep files in your own S3-compatible storage instead.

Confidential documents go in an encrypted vault. The server cannot read its contents or file names — even when we are the ones running the server.

Accounts, quotas and settings live in the admin panel. Sign-ins and other important events go to the security log.

Everything runs inside your infrastructure.
Questions before deployment
QuestionAnswer
Where are files stored?In ordinary folders on your server, or in your S3-compatible storage.
Are DiscoDrive apps required?No. Third-party apps connect over WebDAV, CalDAV, CardDAV and other open protocols.
Who can read a vault?Only whoever holds the key. On the server the vault is stored encrypted.
How do employees share files?With links that support passwords, expiry dates and read-only access.
How is access managed?Accounts and quotas are set up in the admin panel. Third-party apps get their own application passwords.
Can we move our data?Yes. Ordinary files are simply copied, no export needed. Vaults open in Cryptomator apps.

Migration

Moving from Nextcloud or Google Workspace is easier in stages: a small group first, then everyone else.

  1. Install the server, create accounts and set quotas.
  2. Export files from the old system and copy them over WebDAV or straight into the server folders.
  3. Move a few calendars and address books as a trial and connect them over CalDAV and CardDAV.
  4. Connect work computers and phones, and check sync and file links.
  5. Once everything works, move everyone else.

You can do this in-house or have us do it as part of deployment.

The short version

Each point can be checked independently.

  • When stored on disk, files sit in ordinary folders and can be read without DiscoDrive. Corporate deployments can keep files in S3 instead.
  • WebDAV, CalDAV and CardDAV: employees keep their own apps for files, calendars and contacts.
  • Encrypted vaults in the Cryptomator format.
  • Account protection includes argon2id, TOTP, WebAuthn, application passwords and a security log.
  • Per-employee quotas: once exceeded, writes stop.
  • Files, calendars, contacts and libraries are one system, not five.

Get in touch

The address is info@discodrive.app. So that we can suggest the right option straight away, tell us:

  • How many people, and what the cloud is for.
  • Where the server should be.
  • What you are moving from, if you are moving.
  • Data storage requirements and the support you need.
  • Which systems DiscoDrive needs to work with: Keycloak, S3 or others.

Discuss your project