Your organisation's IT.Define it once and OrganicOS applies it everywhere.
Mail, files, chat, VPN, and a workspace for each person — on your server in the EU.
What is OrganicOS?
A declarative IT platform. You describe your organisation once: people, apps, and access. OrganicOS turns that into a running server and a workspace for each person.
Run the stack yourself, host on the OrganicOS.io EU cloud, or connect a server you already have. OrganicOS.io handles updates and day-to-day infrastructure operation.
One place instead of five admin panels
Most teams run mail, files, and VPN as separate services. Each has its own admin login. Over time, nobody has a full picture of who can access what.
OrganicOS gives you one view of people, apps, and access — instead of checking each service separately.
Apps from the marketplace
Start with mail, files, chat, git, passwords, and VPN. Add more from a curated catalog of open source apps, each pre-integrated with sign-in and the rest of your stack. Enable an app in the dashboard and it deploys to your server.
The catalog is still growing. If something you need is not there yet, let us know.
Best IT practices, built in
Signed history
Every change is a commit in your blueprint repository — reviewable and reversible.
Offboarding is immediate
Remove someone once; their access drops everywhere it applied.
Encryption by default
Transport, disks, and backups are encrypted in the default server setup.
Evidence, not checklists
Compliance reports compare what is configured with what is actually running.
Compliance and evidence
OrganicOS helps you meet GDPR and NIS2 technical requirements:
- Disk and backup encryptionRequiredActive
- Single sign-onRequiredActive
- Audit loggingRequiredActive
The dashboard checks what is configured against what is actually running — evidence from the live system, not a questionnaire.
How OrganicOS works
From first setup to day-to-day changes, the same workflow applies.
Set up
Pick the apps you need and invite your team. Access rules live in the dashboard, not in five separate admin panels.
Run
The server runs what you configured. Services stay in sync without manual reconciliation.
Workspace
Each person signs in once. Mail, files, chat, and VPN are already set up on their device or USB boot.
Update
A new hire or a departing colleague? One change propagates everywhere it matters.
Company data stays on your server, separate from personal files on the device.
Technical overview
For engineers and IT leads evaluating the platform.
Dashboard changes become signed commits in the blueprint repository. The on-server agent verifies each commit and rebuilds the host to match — or refuses if something does not check out.
Platform components
- Blueprint
- The organisation's configuration in Git: people, enabled apps, access rules. Your organisation holds the repository. Changes are signed commits.
- Dashboard
- The admin interface at organicos.io. People, apps, marketplace, and compliance reports — changes are written to the Blueprint as signed commits.
- Agent
- The on-server control plane. It owns the organisation's blueprint git repository, verifies signatures on incoming commits, and applies the configuration. The running system must match the Blueprint or the update fails.
- Server
- A Nix-based server running identity, mail, files, chat, VPN, git, backups, and the services the Blueprint enables.
- Workspace
- A personal environment on an organisation device or USB. Apps, VPN, and sign-in are already configured.
Nix-based server and workspace templates are open source (AGPL).
Common questions
Quick answers on data, workspaces, compliance, and licensing.
Where does our data live?
On infrastructure you control in the EU. OrganicOS.io cannot access your data. It is encrypted under your organisation's keys.
What is a workspace?
Each person's ready-to-use environment. Mail, files, chat, and VPN are already configured on an organisation device or a USB boot image.
Is compliance built in?
Security controls and audit evidence are part of the default setup. The dashboard compares what you configured with what is actually running, so you can show live proof instead of maintaining a separate checklist.
Is the software open source?
The Nix-based server and workspace templates are open source under AGPL. You can inspect the code, fork it, and run the stack without OrganicOS.io if you choose.
Get in touch
Want a walkthrough? Request a demo. Already using OrganicOS? Sign in to the dashboard.
Request a demo
We will walk you through OrganicOS for your organisation.