Ogygia Mail Vault
SELF-HOSTED MAIL VAULTALPHA 3

Your mail.
Your own place.

One encrypted file for your email.
You decide where it lives and who has access.

Ogygia brings mail from your existing accounts into a password-protected .cbox vault. Use it locally on Windows, or on your own server through a browser and remote clients.

Download Windows portable See how it works

0.2.0-alpha.3·Early test release

One portable vaultMultiple accountsSelf-hostedOffline reading with a local vault

YOUR STORAGE, YOUR CHOICE

One vault. More ways in.

The .cbox file stores your mail and account settings in encrypted form. Choose the access method that fits your own setup.

01 / ON YOUR COMPUTER

Windows, on your own PC

Extract the package, launch the app and open a local vault. Read and search downloaded messages without an internet connection.

Portable folder · local .cbox
02 / ON YOUR SERVER

Docker and a browser

Run the server on your own infrastructure. The web interface gives you access to the vault stored on that server.

Your own storage · HTTPS for remote access
03 / THROUGH A REMOTE CLIENT

Local interface, remote API

The Windows client uses its own interface; your Ogygia server API handles mail operations. Sign in with the owner password or a permission-scoped API key.

The vault stays on your own server

A home for test email, too

Optional authenticated SMTP test accounts for projects and environments, with encrypted storage. Relay is off by default; an explicitly enabled automatic policy applies only to future events.

SMTP TEST

Ogygia is not a cloud inbox service. It connects to your existing IMAP accounts and can receive SMTP test mail when you configure it.

RELEASE FILES

Try it in your own setup.

Version: 0.2.0-alpha.3
Download a package, then check its filename and full SHA-256 value.

Available

Windows portable

A native window, a local vault or a connection to your own Ogygia server. Extract the folder and run it, with no installer.

Windows x640.2.0-alpha.3
Ogygia-0.2.0-alpha.3-windows-x64.zip24.46 MiB · 25,652,931 bytes
Download
Available

Deployment package

For your own server: Docker deployment and browser access. You manage persistent vault storage and backups.

Docker / browser0.2.0-alpha.3
Ogygia-0.2.0-alpha.3-deployment.zip11.33 KiB · 11,602 bytes
Download
Available

App notices

Bundled application notices, copyright statements and third-party acknowledgements.

Release files0.2.0-alpha.3
Ogygia-0.2.0-alpha.3-notices.zip318.32 KiB · 325,955 bytes
Download
Available

Checksums

SHA-256 checksums for the three ZIP packages. Compare the value of your downloaded file with the listed value.

Release files0.2.0-alpha.3
SHA256SUMS304 B · 304 bytes
Download
LATER

Linux and Android

Downloadable Linux desktop and Android remote-client packages are deferred. Neither is available for this release here yet.

Build commit49fff72fd45db63c8e8f8f76c9b88c980e966533Machine-readable release data

BEFORE THE FIRST LAUNCH

A few minutes to get ready.

The portable package includes its application environment. You remain responsible for vault backups and keeping the server process running.

  1. 1

    Download and verify

    The Windows package needs 64-bit Windows, Microsoft Edge WebView2 Runtime and .NET Framework 4.8. After downloading, calculate its checksum:

    Get-FileHash .\Ogygia-0.2.0-alpha.3-windows-x64.zip -Algorithm SHA256

    The full value must match the file card and the entry in SHA256SUMS.

  2. 2

    Back up, then extract

    Use Archive & Recovery to create an encrypted whole-vault backup. If the old build has no backup screen, stop it and copy its entire encrypted data directory with sidecars. Keep the pre-migration backup, password and old app. Extract the entire ZIP; do not run the app from inside the archive.

  3. 3

    Choose where the vault lives

    Launch Ogygia.exe. In local mode, your vault can live in the portable folder’s data/ directory. In remote mode, enter your own Ogygia server address and sign-in details. For a server, follow the deployment package guide, with a persistent data directory and HTTPS for external access.

  4. 4

    Set up continuous operation

    Background sync and jobs require the hosting process to keep running. Desktop background running and persistent access are separate options, both off by default; closing the window alone does not provide continuous server operation.

RELEASE STATUS, IN PLAIN SIGHT

An early release, with clear limits.

This page describes the release files and how to use them. A version and checksum identify a package; they do not establish full device acceptance.