Product
Features
Use cases
[resources]
Guides, changelog, security, integrations, and the older blog archive. No fabricated customer wall.
Web and desktop share the same relationship model when you are signed in. They are not the same computer.
A precise map of local vault, meeting audio, cloud ledger, model providers, and analytics.
How proposed Gmail, Slack, calendar, and HubSpot actions are held until a person approves them.
Supported operating systems, architectures, the download resolver, and the first-run choice between signing in and bringing your own keys.
Desktop releases from GitHub. No invented version numbers.
What stays on the machine, what syncs, what waits for approval.
Gmail, Calendar, Slack, HubSpot, MCP.
Editorial notes from the product. Categories: product, workflow, security, install.
A published-story index. Empty until a real write-up is approved.
CRM, inbox, meeting notes, and generic assistants — only the seams we can defend.
Definitions for leftover search URLs. Help-center queries stay answered.
Documentation for the API lives at docs.oppulence.io. We are not building a second docs tree here.