FinAIOSby FinoGeeks

Product · Experience layer

FinDesk

The white-label AI desktop

Most institutions end up with AI scattered across vendor chat windows, none of them in their own brand and none governed the same way. FinDesk gives you one desktop you own: your brand, your plugins, your rules, with FinSAFE sandboxing every agent that runs on it.

Talk to FDEDownload the FinDesk SDKSee in the stack
An advisor workspace built on findeskHarbour & Vale Private Bank is a sample brand · illustrative data
Harbour & Vale · Advisor workspacefindesk
Search clients, documents, plugins…⌘K
Client: Chen household
Household · sample client

Chen household

AgentOverviewDocumentsActivity
EL
Elena Lau · 13:12

Prepare me for my 2pm with the Chen household. Anything I should raise?

AI
Advisor Agent · plugin · 13:12

Here’s a one-page brief. Two items need your attention before the meeting.

Meeting brief · Chen householdSources: Client Book, Research, IPS
Read-only actions · loggedDraft, review before use
Ask the agent, or type / for plugin commands↵
Plugin sidebar Each tool is a plugin your institution enables per role.
Agent pane The agent works across plugins: client book, research, IPS. It cites its sources and stays within read-only scope.
Plugin panel Context-aware panels, here Compliance Inbox and Research, with declared scopes.

Where it sits

The experience layer of FinAI OS

FinDesk is where advisors, operations staff and clients actually meet the agents. It connects to FinHub's AG-UI gateway and uses the models the platform manages. Agents can also run locally on the computer, each inside FinSAFE by default, with their network connections logged in FinDesk's own Audit center.

Sold on its own, it connects to the agents and systems you already run. Inside FinAI OS, it connects to FinHub for models, platform agents and reviewed skills.

FinAI OSThe managed agent platform · on-prem or your private cloud
Layer 4
Experience
Where clients, advisors and staff meet the agents.
FinDeskPlugin-based white-label AI desktopFinClipMini-program runtime for your apps
FinDesk is here
Layer 3
Agent
Manage, run and contain agents per tenant.
FinHubManaged agent platformFinClawMulti-tenant agent runtime
Layer 2
Knowledge
What agents know, and how it is structured.
FinLoreKnowledge baseFintologyOntology + knowledge graph / distillery
Layer 1
Control
Every agent runs contained; FinGuard decides each write that goes through it.
FinGuardAction gatewayFinSAFESandbox
Your infrastructure  Models · data · identity · core systemsHighlighted: Experience layer

White-label, not white-wash

One desktop. Your brand, your plugins, your people.

The same findesk shell, themed and configured three ways. Brand, type, colour, plugin set and workspace change per institution. Policy, audit and the agent runtime underneath don’t change.

Illustrative · sample brands and data

Private bankAdvisor-led wealth · full plugin set
Retail bankBranch advisors · slimmer plugin set
Insurance wealthHybrid advice · compliance-heavy plugins

Plugin architecture

Anything can be a plugin. Nothing bypasses policy.

The host shell loads plugins that declare what they need in a manifest. Your institution reviews and enables those scopes.

How a plugin runs inside findeskIllustrative

Diagram: the findesk host shell loads plugins through a manifest and permissions layer. Plugins come from three sources: first-party FinAI OS, institution-built and partner.

plugin.manifest.jsonIllustrative · not a published schema
// Compliance Inbox: a first-party plugin
{
  "id": "compliance-inbox",
  "version": "1.4.0",
  "publisher": "finai-os",
  "surfaces": ["sidebar", "panel"],
  "workspaces": ["advisor", "compliance"],
  "scopes": [
    "cases:read",
    "kyc:request"
  ],
  "actions": {
    "kyc.refresh": {
      "approval": "compliance-officer"
    }
  },
  "theme": "inherit"
}
  • a.Declared, not discovered. A plugin can do only what its manifest declares and your administrators approve.
  • b.Theme inherits. Plugins pick up the institution’s brand tokens, so third-party tools look native.

Capabilities

What FinDesk does

Five things a platform team needs to put a branded, governed AI desktop in front of advisors, operations staff and clients.

  1. 1

    Branding & theming

    Wordmark, colour, typography, density and light or dark mode, all set as brand tokens. Change them once and the shell and every plugin follow.

    Brand tokensPer-entity themes
  2. 2

    Plugin SDK

    Build your own tools as plugins with a manifest, surfaces (sidebar, pane, panel, command) and declared scopes. Your teams own them; FinDesk hosts them. Your distribution repo holds your brand and plugins and pins the SDK version, so you take product updates without merging source.

    ManifestSurfacesScopes
  3. 3

    Role-based workspaces

    Separate workspaces for advisors, operations and clients, each with its own plugin set, layout and permissions, from one deployment.

    AdvisorOperationsClient
  4. 4

    Any agent, sandboxed by default

    Run local agents such as FinClaw, Hermes, Codex, dsh, pi-agent and others, or connect to agents hosted on FinHub, from one interface. Each local agent runs inside FinSAFE by default on macOS, Windows and Linux, and its network connections are logged in FinDesk's on-device Audit center.

    FinSAFELocal agentsAudit center
  5. 5

    On-premise desktop

    Deploy inside your own environment. One installer covers macOS, Windows and Linux, on both arm64 and x64, with the same brand, plugins and policy on every machine.

    On-premmacOSWindowsLinux

Standalone · better with

Useful alone. Stronger in the stack.

FinDesk can front the agents and systems you already run. Paired with other FinAI OS products, each step adds a capability you would otherwise build yourself.

FinDesk alone

A branded, plugin-based desktop

  • Your brand across shell and plugins
  • Role-based workspaces and plugin sets
  • Plugin SDK for institution-built tools
  • Local agents sandboxed in FinSAFE by default
  • Deployable inside your environment

Better with

+ FinHubManaged agent platform
Agents that live in the desktop

Connect to the platform's AG-UI gateway for its hosted agents and managed models, and pull reviewed skills from its catalog into FinDesk's Agent Store.

+ FinGuardAction gateway
One gateway for enterprise actions

FinDesk is designed so its local agents reach your enterprise systems through the same FinGuard gateway as server agents.

+ FinLoreKnowledge base
Answers with sources

House views, policies and product documents become citable knowledge that agents connect to over MCP.

Deploy with FDE

Your desktop, stood up inside your environment

Forward Deployed Engineers set up FinDesk alongside your brand, platform and compliance teams, and leave you able to build the next plugin yourselves.

Talk to FDE
A typical FinDesk engagementTypical sequence · scope varies
  1. Step 1

    Shell & brand

    Deploy the host shell; set brand tokens, identity and the first workspace.

  2. Step 2

    Plugins & wiring

    Enable first-party plugins, connect your systems and build the first institution plugin together.

  3. Step 3

    Roll out by role

    Launch one workspace, add roles, and hand the plugin SDK to your teams.

Next step

Give your institution an AI desktop with your name on it

Talk with a Forward Deployed Engineer about standing up FinDesk on its own or as part of FinAI OS.

Talk to FDEExplore FinAI OS