Sparks Cloud calendar
AvailableNative EU calendar in Postgres – recurring events, attendees, public web RSVP for guests, ICS export, and migration wizard. Optional instead of or alongside Exchange/Nextcloud.
Sparks provides all backend components – or you connect what you already run: from full sovereignty and your Matrix backend to hybrid with Microsoft 365 or your own Exchange and SharePoint. Word, Excel and Outlook can stay on the desktop – Sparks brings chat, video, calendar and AI together in one interface, usually without migrating data.
Sparks Cloud calendar
AvailableNative EU calendar in Postgres – recurring events, attendees, public web RSVP for guests, ICS export, and migration wizard. Optional instead of or alongside Exchange/Nextcloud.
Exchange SE & SharePoint Server
AvailableExchange Server/SE via EWS and SharePoint Server on-prem – calendar, files, identity (Entra ID, AD FS). Parallel with M365 supported.
Microsoft 365
AvailableCalendar from Exchange, tasks from Planner, files from SharePoint & OneDrive, MS Teams chat connection.
Google Workspace
AvailableGoogle Calendar, Google Drive files and Google Contacts – connected via OAuth, no data migration.
Nextcloud / openDesk
AvailableNextcloud calendar (CalDAV), files (WebDAV), Nextcloud Talk bridge. Full openDesk compatibility.
Open-Xchange
AvailableOX App Suite calendar (CalDAV) and contacts (CardDAV) – ideal for hosted Exchange alternatives.
Matrix server
AvailableAn existing Matrix server can be reused. Any compatible Matrix server works – e.g. Synapse, Tuwunel, Dendrite, Conduit. Optional: connect your own LiveKit for video.
Cisco Jabber
EnterpriseClick-to-IM and click-to-call into the installed Jabber client – org-controlled deep links, no chat bridge.
If Outlook remains your mail and calendar client, you can schedule Sparks online meetings without switching apps: the Sparks Outlook add-in (Office.js) extends Outlook desktop, Outlook on the web, and New Outlook for Windows – similar to the “Teams meeting” button.
Available as an Office add-in (React + Office.js). The meeting button and calendar task pane are implemented; create appointment from email, dual-write to the Sparks Cloud calendar, and RSVP sync are in progress.
Sparks meeting in appointments
When composing an Outlook appointment, the “Sparks meeting” button inserts a join link, meeting ID, and invitation block – including meeting options (lobby, E2EE, etc., depending on plan).
Sparks calendar task pane
The ribbon opens a compact Sparks calendar panel: view events and manage Sparks appointments without leaving Outlook.
Connected to Sparks backends
Authentication via Entra SSO or Keycloak; appointments and online meetings use the Sparks account API and appointment manager – compatible with Exchange/M365 hybrid setups.
Central rollout
Deploy as an integrated app in the Microsoft 365 admin center or sideload for pilots. Production hosting: outlook-addin.sparks.team.
In development
Organisations running Cisco Jabber (CUCM + IM and Presence) can start chat or a call in the installed Jabber client from Sparks – without embedding Jabber chat in the app and without an XMPP bridge.
Enabled per organisation. From the contact card, people page and avatar menu, Sparks opens the Jabber protocol handler (IM or call). History and media stay in Jabber.
Click-to-IM
Opens the Jabber chat window for the contact’s JID or user ID via deep link (e.g. im: / xmpp:).
Click-to-Call
Starts an audio or video call via Jabber protocol handlers (ciscotel: / tel: / sip:) using the contact’s number or SIP URI.
Org control
Admins enable the feature per organisation and configure preferred schemes and an optional default IM domain.
Desktop and web
Tauri desktop and the browser open the OS protocol handler. Requires Jabber installed and registered.
Intentionally not included
Sparks is not a new silo. It connects to your existing backends and leaves your data where it is – or you use the native Sparks Cloud calendar (EU Postgres) without an external calendar source. Exchange data stays in Exchange. Google data stays in Google. Nextcloud data stays in Nextcloud. Sparks is the frontend that brings everything together.
Data stays in your backends – Sparks is the frontend.
The Sparks assistant accesses calendars, chats, tasks and files from all connected backends – simultaneously. Questions like "What are my tasks for today?" or "Summarise the Nextcloud document we discussed in the last meeting" are answered with real context – not hallucinations.
Discover the AI assistant