The suite

Everything a small organisation needs, on its own machine.

Ordner is a self-hosted replacement for the mail, calendar, contacts and file storage that households, clubs, associations and small businesses rent from large platforms. The convenience is the same; the difference is who holds the data.

JMAPIMAP · SMTPCalDAVCardDAVWebDAVPasskeys28 languagesWCAG 2.2 AA

Four services, one install

One codebase, run as a single organisation's own install on its own machine — or as one hosted install serving many independent organisations, each with its own domains and its own keys.

Mail

JMAP, IMAP and SMTP submission — any client you already use. Inbound mail is authenticated, scanned and scored before it is filed; outbound is signed and delivered with modern standards honoured.

How mail works →

Calendar

CalDAV and JMAP, with scheduling, free-busy, reminders and booking. External calendars and public links included; a calendar shared by handle appears in the other person's own clients.

Contacts

CardDAV and JMAP, with vCard conversion, photos, import, export and duplicate handling. Groups and a shared group directory; sharing and delegation by handle.

Files

WebDAV and JMAP, with sharing, versions and a trash. External links through a share gate, short links for anything you hand out, and mail attachments as a read-only folder.

Beyond the big four

The same install also carries the applications a household, club or small business actually lives in — all speaking the same surfaces, all under your domain.

Photos

Your Pictures folder as one library, sorted by the day taken, with albums, editing (crop, straighten, rotate) and album export. Camera uploads are filed for you; every picture stays an ordinary file any WebDAV app sees.

Meet

Video meetings with a lobby and invited-only entry, reachable from Calendar and a room's own page. The media server runs beside the install; the records and tokens stay on your node.

Notes

Notes kept the way Apple Notes keeps them — as messages in your Notes mailbox — so iPhone, iPad and Mac Notes show the same notes, and edits sync both ways. Checklists, images, files and Markdown editing included.

Tasks

Tasks over JMAP for Tasks, with lists, due dates and reminders — and a task made straight from a mail message, linked back to it.

Forms

Forms and their responses on your own domain: a respondent API, exports and the owner's notices — sign-ups and surveys without a third party in the middle.

Booking

A public booking page on your domain: free-busy from your calendars, invited meetings and the video room already attached.

Migration, wider

The import reads your old provider over IMAP, POP3, CalDAV, CardDAV and WebDAV — and now Google Drive too, files exported to Office formats, streamed and resumable, with the OAuth client set once by the administrator.

Documents

Files open in the browser through ONLYOFFICE: read-only preview for everything the browser can draw, and word processing, spreadsheets and presentations edited together, with several people in one document at a time.

How it is different

Not a features race — the design states what it does and does not do, each with a reason. Here is what that means in practice.

Any client you already use

Every surface speaks the standard protocol, so native clients work without plugins. The web applications are just another client — they use the same public surfaces as Thunderbird or your phone.

  • JMAP (RFC 8620/8621) for mail, calendars and contacts
  • IMAP and SMTP submission through the gateway, with autodiscovery
  • CalDAV, CardDAV and WebDAV for everything else

Identity without passwords

Passkeys are the only primary credential — no password hashes to breach, no password policy, no breach list. Protocol clients get named, scoped, individually revocable app passwords. Applications connect over OpenID Connect.

  • Step-up with a fresh passkey assertion for every sensitive action
  • Delegation and groups for people; guests identified by an external ATProto handle get strictly limited rights

Sharing by handle, across installs

Grant access to anyone with a handle — like emma.ordner.fyi. A shared calendar or address book from another organisation appears inside your own account, in your own clients, next to your own data. No second account, no per-install app passwords, nothing copied to a central party.

  • Your identity isn't an account on somebody's server — it's yours, and it travels with you
  • Local or remote stops being a special case and becomes a lookup

Migration that respects the source

Move in from an existing provider over IMAP, POP3, CalDAV, CardDAV and WebDAV. The import reads your old provider without writing to it, resumes if interrupted, and is driven by a wizard.

  • Read-only on the source, idempotent, resumable
  • Erasure handled the way erasure should be

Operations a small team can run

An administration console for identity, domains, DNS and mail operations. A health check — a "doctor" — for every service. S3-compatible object storage as the only durable store, encrypted at rest.

  • Settings that apply without restarts where they can
  • Status and observability on the install's own private network

Built for everyone in the organisation

Every user-facing surface ships in 28 European languages and meets WCAG 2.2 AA as a build gate — not an aspiration, a gate: a page that does not meet it does not build.

Encrypted at rest, by construction. Every durable object — contents and names — is encrypted on the node before it reaches the object store. The provider sees ciphertext and opaque names, and is designed as if it were the adversary. The full security posture →
Status, stated plainly: Ordner is under active development and not yet released. It runs on a test installation today; interfaces and deployment steps still change. Where something is decided but not yet built, this site says so in the same breath — see Security.

The basics, in order.

Read the posture, or go straight to how the suite works.