On-Premises Personal Agents
Run your own personal-agent platform on your own servers, giving each employee or customer a personalized agent that remembers them and acts for them within the permissions you set.
Solutions
AI workstation for financial professionals
Give your professionals one desktop under your institution's identity, rather than a collection of unrelated chat windows. FinDesk brings agent assistance, documents and business tools into a configurable workstation. Our Forward Deployed Engineers (FDEs) assemble and deploy the branded distribution with your team, around the work people actually need to do.
- Your brand, distribution assets and private extensions.
- Business tools as plugins within a shared desktop frame.
- Local and hosted agents, with explicit tool access.
Ways to start
Explore the SDK
your technical team can use the distribution template and packaging SDK to understand the host, shell and plugin contracts. This download is a developer SDK, not an end-user app installer.
Bring one workflow
choose a professional role, your brand and an existing business service. FDEs build the first workstation with your team, including a scoped adapter and clear operating responsibilities.
Solutions
Moments that matter
Start the day with work items and institution-selected tools in one frame. Move from an application into agent assistance with deliberately selected context. Prepare a document, inspect the result and return to the business workflow without treating every application as another chat session.
The aim is continuity of work, not unrestricted agent access. A tool visible to a person can remain unavailable to the assistant; a connected service can expose only the operations the institution chooses.
Solutions
Two views of the same workstation
Professional workspace
Work queue · Documents · Business applications · Agent assistant. A professional opens a document and asks for help with selected context, then reviews the result before using it.
Institution configuration
Enabled plugins · Explicit tool attachments · Brand · Organisation endpoints. The institution selects the tools people see and separately decides which registered tools an agent session may use. Showing an application does not grant the agent its authority.
Architecture
Plugin architecture
These are architecture layers, not security grades:
L1 Host:
the stable platform contract, registries and mediated host services.
L2 Shell:
the desktop frame—sidebar, top bar, layout and routing mounts—which places registered plugin contributions.
L3 Plugin:
a bounded business surface with navigation and a view, plus an optional backend-for-frontend (BFF), binary sidecar or Model Context Protocol (MCP) tools.
A distribution selects the shell, enabled plugins, brand and policy. The shell does not select the plugin set by itself. Existing services connect through purpose-built plugin UI and explicit adapters, with an optional BFF or host-supervised sidecar. This is not a promise that every website embeds unchanged.
Control boundary
plugins use scoped host APIs, and privileged operations are checked in the main process. Declaring an agent tool is separate from attaching it to a session: attachment is opt-in and off by default. Execution isolation for local agents comes from FinShield and FinSafe.
Distribution
Your distribution, not a fork of the core
Set the product name, application identity, logos, theme, locale and enabled optional plugins. Add institution-private workflows, configure endpoints and policy, and package platform-specific installers for macOS, Windows and Linux according to the chosen SDK and architecture.
Your institution owns its distribution repository, assets, private plugin source and release identity; the proprietary platform core remains separately supplied. Pin the SDK and sidecar versions to manage upgrades. Local-only configuration and hosted services are explicit choices, not a blanket promise that every connected workflow runs offline.
Products
Supervision and composable product roles
Professionals review outputs; the institution reviews plugins, context sharing, tool attachments and configured endpoints. Treat agent access and human application access as separate decisions. FinDesk stands alone; other products are optional.
- FinDeskthe workstation experience, host, shell and plugins.
- FinHuboptional managed models, hosted agents, skills and platform connectivity.
- FinShieldlocal-machine protection, execution isolation and runtime tracing, separate from renderer-plugin controls (FinShield and FinSafe).
- FinGuardan optional stateful, rule-based action gateway for scoped routes into enterprise systems.
- FinClawone available runtime integration, not a required engine.
Runtime and business-tool choices are separate from the desktop brand. Scope compatible connections rather than assume every runtime or action is automatically covered.
FDE
FDE delivery
- Agree: users, workflow, identity and deployment boundary.
- Assemble: pin the SDK, select the shell and plugins, and configure the branded distribution.
- Adapt: build the first private integration and explicitly attach approved agent tools.
- Check and hand over: validate the selected platform installers, endpoints and local-agent controls; hand over the distribution repository, private plugin source and update process.
FAQ
Common questions
Is this another chat app?
No. FinDesk combines a desktop frame, business plugins and agent assistance under your institution's brand.
Can we keep existing applications?
Yes. Scope UI and optional BFF/sidecar adapters around existing services; integration is not universal drop-in embedding.
What do we own?
Your distribution identity, assets, configuration and private plugin source—not proprietary platform-core source.
Does installing a plugin give agents access?
No. Tool registration and session attachment are separate. Host checks and local-agent isolation also have different roles.
How do we deploy and update?
Use a pinned SDK and your distribution configuration to build platform-specific installers. FDEs deliver the setup and update process; the public SDK is not an app installer.
Solutions
Extend your workstation for investment research and analysis
Bring your research workflows, data sources and professional tools; shape the next layer with our FDEs.
Next step
Put your institution's AI workstation in your professionals' hands.
Talk to an FDE about your brand, workflows and first private integration.