File storage and sharing for the whole company, on servers you control — a clean web file browser behind one company login, with workspaces that keep each company's files strictly separate, and the other Synergy apps filing documents into it for you automatically.
Open the app and you are in your files — folders, breadcrumbs, uploads, downloads — all behind the same company login as the rest of the suite, so there is no separate Drive password to manage.
List and navigate folders with breadcrumbs, create folders, rename, delete, and download — verified working in a real browser, light and dark.
Click-to-upload and drag-and-drop straight into the current folder. Upload-to-download round-trips are byte-verified — what you put in is exactly what comes back.
Files, folders, shared drives, and search all back the screen you see — with each file's details and version history tracked automatically behind the scenes.
SynergyDrive sits entirely behind SynergyAuth. There is no separate Drive account and no second password — the company login confirms who you are, and the system places you in your company's own workspace on every single request.
The login layer was attacked on purpose. An internal security review found a way one internal service could pretend to be another; the fix walled the services off from each other so identity can never be faked in transit — then the exact same attack was re-run and no longer works at all.
SynergyDrive is not just where people put files — it is where the platform puts them. A locked side door, open only to trusted Synergy services, lets the platform file documents into the right person's Drive.
SynergyMeet transcripts land in the meeting host's Drive automatically — proven end to end with a live meeting whose labeled transcript arrived without anyone uploading anything.
When an app files a document for you, it acts under the same workspace boundaries a signed-in person gets — so automatic filing can never cross company lines.
Two real bugs, found and fixed before launch: a hidden database fault meant file uploads had never once succeeded — and file sizes always showed as unknown. Both were traced to the root cause and fixed, then proven by uploading files and confirming the downloads came back identical. That is the standard: shipped means tested, not assumed.
FastAPIPostgreSQLMinIO object storageOne company loginnginx + TLSDocker Compose