Skip to content

SilentSuite Bridge

SilentSuite Bridge is a local daemon that translates between CalDAV/CardDAV and the Etebase protocol. It runs on your machine and makes SilentSuite compatible with any calendar, contacts, or tasks app that supports CalDAV/CardDAV -- including Thunderbird, macOS Calendar, GNOME Calendar, Windows Calendar, Outlook, and more.

How It Works

Your App (CalDAV/CardDAV)
        |
http://localhost:37358/
        |
SilentSuite Bridge (local)
        | (encrypted)
SilentSuite Server

Local-only bridge

Keep the bridge bound to your local machine unless you fully understand the risk: DAV clients can access decrypted local calendar, contact, and task data through the bridge.

The bridge handles encryption/decryption locally. Your data is still end-to-end encrypted -- the bridge just presents it as standard CalDAV/CardDAV to your apps.

Supported data types:

  • Calendars (CalDAV / VEVENT)
  • Tasks (CalDAV / VTODO)
  • Contacts (CardDAV / VCARD)

The bridge exposes every SilentSuite calendar, task list, and address book as its own DAV collection, so compatible clients can select the destination collection for new events, tasks, and contacts.

Install

Windows

Download the current Windows bridge binary directly:

Save the file in Downloads. You can either keep the release file name or rename it to silentsuite-bridge.exe, then run it from an already-open PowerShell or Windows Terminal window so any first-run errors stay visible:

powershell
cd $env:USERPROFILE\Downloads
.\silentsuite-bridge-windows-x86_64.exe --version
.\silentsuite-bridge-windows-x86_64.exe --login

If you renamed the file, use ./silentsuite-bridge.exe instead.

If Windows SmartScreen appears, choose More info and only continue if the publisher/file name matches the SilentSuite release you downloaded.

Installer Status

Bridge installer scripts are being hardened. If you use a PowerShell installer command, run it from an already-open PowerShell or Windows Terminal window, not from the Run dialog or by double-clicking a .ps1 file.

WARNING

Do not run installer commands from the public dev branch. Those scripts may contain unreleased changes and are not part of the stable docs flow.

If a PowerShell window closes before you can read the error, reopen PowerShell and run the diagnostic form instead. It downloads the installer to a temporary file and runs it with -File, so failures stay visible and are also written to %LOCALAPPDATA%\SilentSuite\install.log.

powershell
irm https://raw.githubusercontent.com/silent-suite/silentsuite/main/bridge/install.ps1 -OutFile $env:TEMP\silentsuite-bridge-install.ps1
powershell -ExecutionPolicy Bypass -File $env:TEMP\silentsuite-bridge-install.ps1

All downloads are also available from the GitHub releases page.

First-Time Setup

1. Start The Bridge And Log In

After installation, run:

bash
silentsuite-bridge

This starts the local bridge and opens the dashboard at http://localhost:37358/. If your browser does not open automatically, open that URL yourself. Enter your account email and password in the dashboard setup form; the bridge authenticates with the server, stores your session locally, and starts syncing.

silentsuite-bridge --login is still available as a fallback or advanced path. Running it adds another account or re-authenticates the same account; it does not remove accounts that are already configured.

2. Note Your Connection URLs

After successful login, the dashboard shows your CalDAV/CardDAV URLs:

FieldValue
CalDAV URLhttp://localhost:37358/your@email.com/
CardDAV URLhttp://localhost:37358/your@email.com/
UsernameYour account email
PasswordYour account password

You can always find these URLs by:

  • Opening the dashboard at http://localhost:37358/
  • Using the system tray menu account entries (Copy CalDAV URL / Copy CardDAV URL)

Multi-Account Use

The bridge can keep multiple accounts active in one local bridge profile. Each account has its own credentials, local cache namespace, sync thread, and DAV path.

bash
silentsuite-bridge --login
silentsuite-bridge --login
silentsuite-bridge --list-accounts

Each account uses a URL containing the account email:

text
http://localhost:37358/work@example.com/
http://localhost:37358/personal@example.com/

Use the matching account email and password in your calendar/contact client. A client authenticated as one account cannot access another account's DAV path.

You can add or re-authenticate accounts from the dashboard with Add / Re-authenticate Account. It shows the dashboard sign-in form and starts syncing the account after login succeeds; you do not need to restart the bridge.

To remove only the local login/session for one account while keeping its local cache for future re-login:

bash
silentsuite-bridge --logout work@example.com

To fully remove one account's local bridge data, including its decrypted local cache:

bash
silentsuite-bridge --remove-account work@example.com

WARNING

The bridge local cache contains decrypted calendar, contact, and task data. Use --remove-account when retiring a shared or untrusted machine.

3. Keep The Bridge Running

Leave silentsuite-bridge running. The bridge will:

  • Start the CalDAV/CardDAV server on localhost:37358
  • Show a system tray icon (green = connected, yellow = warning, red = error)
  • Sync automatically in the background

Dashboard

The bridge serves a status dashboard at:

http://localhost:37358/

The dashboard shows:

  • Connection status
  • All configured accounts
  • Last sync time
  • Per-account CalDAV/CardDAV URLs with copy buttons
  • Add / Re-authenticate, Log out, and Remove account actions
  • Recent sync log

Use Log out to remove local bridge credentials while keeping that account's local cache for re-login. Use Remove account to delete local bridge credentials and that account's decrypted local bridge cache on this computer. Other configured accounts are not affected.

Auto-Start

Install Auto-Start

bash
silentsuite-bridge --install-autostart

This configures the bridge to start when you log in:

  • Linux: Creates a systemd user service
  • macOS: Creates a launchd agent
  • Windows: Adds a startup registry entry

Remove Auto-Start

bash
silentsuite-bridge --remove-autostart

Uninstall

Windows PowerShell Installer

If you installed the Bridge on Windows with the PowerShell installer, Docker is not involved. The installer downloads silentsuite-bridge.exe into your Windows user profile, adds that folder to your user PATH, and creates a per-user startup entry so the Bridge can run after you sign in.

To remove the local Bridge app from Windows 11, open PowerShell as your normal Windows user and run:

powershell
# Stop the Bridge if it is running
Get-Process silentsuite-bridge -ErrorAction SilentlyContinue | Stop-Process -Force

# Remove the startup entry
& "$env:LOCALAPPDATA\SilentSuite\silentsuite-bridge.exe" --remove-autostart 2>$null
Remove-ItemProperty -Path "HKCU:\Software\Microsoft\Windows\CurrentVersion\Run" -Name "SilentSuiteBridge" -ErrorAction SilentlyContinue

# Remove the installed Bridge executable and installer log
Remove-Item -Recurse -Force "$env:LOCALAPPDATA\SilentSuite" -ErrorAction SilentlyContinue

Optional: remove the Bridge install folder from your user PATH:

powershell
$userPath = [Environment]::GetEnvironmentVariable("PATH", "User")
$newPath = ($userPath -split ";" | Where-Object { $_ -and $_ -ne "$env:LOCALAPPDATA\SilentSuite" }) -join ";"
[Environment]::SetEnvironmentVariable("PATH", $newPath, "User")

Then sign out and back in, or restart Windows.

If you want to remove local Bridge account data before deleting the executable, list the configured accounts and remove each one first:

powershell
& "$env:LOCALAPPDATA\SilentSuite\silentsuite-bridge.exe" --list-accounts
& "$env:LOCALAPPDATA\SilentSuite\silentsuite-bridge.exe" --remove-account your@email.com

Uninstalling the local Bridge only removes the desktop sync helper from this computer. It does not cancel a hosted SilentSuite trial or subscription. Cancel the trial from your SilentSuite billing/account page if you do not want it to continue.

Environment Variables

VariableDefaultDescription
SILENTSUITE_SERVER_URLhttps://server.silentsuite.ioEtebase server URL
SILENTSUITE_LISTEN_ADDRESSlocalhostIP address to listen on
SILENTSUITE_LISTEN_PORT37358Port to listen on
SILENTSUITE_DATA_DIRPlatform-specificData storage location
SILENTSUITE_SYNC_INTERVAL900 (15 min)Sync interval in seconds
SILENTSUITE_LOG_LEVELINFOLog level (DEBUG, INFO, WARNING, ERROR)

For self-hosted servers:

bash
export SILENTSUITE_SERVER_URL=https://sync.your-domain.com
silentsuite-bridge

CLI Reference

bash
silentsuite-bridge                    # Start the bridge
silentsuite-bridge --version          # Show version
silentsuite-bridge --login            # Add or re-authenticate an account
silentsuite-bridge --list-accounts    # List configured accounts
silentsuite-bridge --logout EMAIL     # Remove local credentials; keep cache
silentsuite-bridge --remove-account EMAIL  # Remove credentials and local cache
silentsuite-bridge --manual-login     # CLI add/re-authenticate (headless/dev)
silentsuite-bridge --install-autostart  # Install auto-start
silentsuite-bridge --remove-autostart   # Remove auto-start
silentsuite-bridge --no-tray          # Start without system tray

Troubleshooting

Bridge won't start

On the default localhost bind, the bridge can start before an account is configured so you can log in through http://localhost:37358/. If you intentionally configured a remote/non-loopback bind, the dashboard is disabled for safety and you must add an account first with:

bash
silentsuite-bridge --login

Can't connect from your app

  1. Verify the bridge is running: open http://localhost:37358/ in your browser
  2. Check the tray icon color (green = OK, red = error)
  3. Check the dashboard sync log for errors

System tray not visible (GNOME)

GNOME removed native tray support. Install the AppIndicator extension to restore it. KDE, XFCE, and other desktop environments support the tray natively.

Firewall blocking

Ensure localhost:37358 is not blocked by your firewall. The bridge only listens on localhost -- it never accepts connections from other machines.

Next Steps

Once the bridge is running, set up your apps:

Released under the AGPL-3.0 License.