Skip to main content

Our Story

Drumee was created by Somanos Sar — driven by a belief that data ownership should belong to users, not platforms.

"The reason I created Drumee was that I was upset by the fact that users lost control of their data. And it still upsets me." — Somanos Sar, Founder

The Moment It Started​

The trigger was simple and universal: you store files on Apple Cloud, and they belong to Apple. Not to you. Apple's infrastructure. Apple's terms. Apple's access.

This is not a niche concern. It applies to every cloud tool teams depend on daily: Google Workspace, Dropbox, Notion, Slack. The convenience is real. The hidden dependency is also real.

Most users never think about it — until a breach, a shutdown, a price increase, or a compliance audit forces them to.

Somanos decided to build the alternative.

What Was Built​

Drumee started as a technical problem: how do you give someone full control over a web-based workspace without relying on any external infrastructure?

The answer required building from the ground up:

  • A file system for the web — workspaces, folders and files with their own metadata, versions and trash
  • An access control model enforced on the server for every request
  • Collaboration built into the data — chat, tasks and meetings attached to the workspace they belong to
  • A foundation that can be extended without rebuilding it

The result is not another SaaS tool. It is an OS-like infrastructure system for the web - designed to adapt to your workflows, your deployment model, and your control requirements.

The Platform Today​

Drumee runs as a single server binary, with object storage for files, a document database with strict tenant isolation, and a realtime layer designed to scale horizontally. → The Drumee Stack

The Principle That Drives Everything​

Drumee's Terms of Use contain no clause that gives Drumee ownership of user data. No lock-in. No harvesting. No processing of your files for advertising or AI training.

This is not a marketing claim. It is a structural commitment — enforced by architecture, not just policy.

On the self-hosted plan, Drumee (the company) cannot access your data. Technically impossible. That is the point.

Where We Are Today​

Drumee follows a dual-path strategy — starting with SaaS, ending in sovereignty.

  • SaaS — The onboarding layer. Live at app.drumee.com, it allows teams to get started instantly with file storage and collaboration.
    No setup, no friction — just a way to experience how Drumee works.
    It’s not the final destination, but the first step.
  • Self-Hosted — The core product.
    The self-hosted edition is coming soon.
    This is where Drumee delivers its full promise: total control, zero dependency, and true data ownership.

The roadmap is simple: start in the cloud → understand the value → move to full sovereignty.

Every improvement we make is focused on one goal: making the transition from convenience to control the most natural decision a team can take.

The Mission​

We are redefining digital ownership by transforming file systems into collaborative, extensible workspaces — where data is not just stored, but activated, shared, and evolved.

This is not a productivity tool company. This is an infrastructure company with a conviction:

Your data should belong to you. Not to the platform you pay to use it on.