Skip to main content

The Drumee Stack

Drumee brings the layers a team normally assembles from separate products — storage, permissions, chat, tasks, meetings — into one platform with one data model and one permission system.

This page describes what the platform is made of.

The Three-Layer Product Architecture​

Drumee's product is structured in three distinct layers, each serving a different role:

LayerRoleWhat It Includes
File System CoreFoundation — this is what we sellStructured storage in workspaces, with versions, trash, quota and fine-grained role-based permissions
Collaboration LayerAdoption driver — this is why teams adoptFile sharing, folder-native chat, tasks and calendar, meetings, Office documents edited together in the browser
System LayerDifferentiator — this is the long-term moatAn app marketplace on the hosted service today; a public API reference and an SDK coming soon

Key insight: Layer 1 IS the product. Layer 2 makes it adoptable. Layer 3 makes it extensible.

What Is in a Workspace​

CapabilityIn short
FilesFolders and files, direct-to-storage uploads with resume, previews, video streaming, versions, 30-day trash
Office documentsWord, Excel and PowerPoint files open and are co-edited in the browser, with history
ChatA conversation per workspace, topics, threads on a file, direct messages, mentions
TasksBoards with columns, sprints, labels, comments and history; a calendar
MeetingsAudio and video rooms, 1:1 calls, screen sharing, guest links with a lobby
SharingInvitations with a role; links with expiry, password and email restrictions
OrganizationMembers, teams, policies, an audit log, plans and billing

The Four Technical Pillars​

1. Identity & Access Control​

A role-based model decided entirely on the server.

  • One role per person per workspace: Viewer, Chatter, Editor, Admin, Owner
  • A separate ladder for administering an organization
  • Share links for people outside, with their own permissions and protections
  • Server-side sessions that can be revoked instantly; two-factor authentication
    → RBAC System

2. File Storage​

Metadata in a database, content in object storage.

  • Every folder and file is a node in a workspace tree

  • Content is stored in S3-compatible object storage under a random identifier — never under the file's name or path

  • Browsers upload directly to storage; the server authorizes, verifies and records

  • Soft delete with a 30-day trash; versions on every change of content

  • → File Storage

3. Realtime Collaboration​

Every change is an event.

  • Changes are published to the people in the same workspace over WebSocket

  • A short replay window makes reconnection seamless

  • Subscriptions are checked with the same permission rules as the API

  • → Request Pipeline

4. Tenancy & Data Protection​

Every organization's data is separated by construction.

  • Each document carries the ID of the tenant that owns it, and every query filters by it

  • Passwords, sessions and codes are stored only as hashes; stored secrets are encrypted

  • End-to-end encryption is in development

  • → Data Storage & Encryption

Runtime Architecture​

Drumee runs as one application binary in two roles, next to three stores:

ComponentResponsibility
ServerThe REST API, the realtime hub, and the web application
WorkerPreviews and video renditions, imports, notifications, scheduled clean-up
Document databaseThe source of truth for everything except file content
Object storageFile content and everything derived from it
Cache and queuesShort-lived state, the event bus, job queues

Servers and workers keep no state of their own, so any number of them can run side by side.

→ Technology Overview

Deployment​

EditionStatus
SaaSLive at app.drumee.com
Self-hostedComing soon

The same platform serves both: the self-hosted edition is the hosted one packaged for your own infrastructure, without plan limits.