Frequently asked questions

Fiducia AI is not a SaaS platform. We deploy the agents directly into your existing infrastructure rather than operating as a shared service that all clients use. For most multifamily offices and EAMs, that means inside your dedicated Microsoft Azure tenant or AWS account, with secure connections to your on-premise systems where needed.

This architectural choice changes how several of the standard SaaS vendor risks apply to your operation, and it is what makes the answers to confidentiality, data, privilege, and continuity work the way they do. Your data and your workflows never leave your environment.

Yes. For senior single-family offices, foundations, and holdings that run their own infrastructure and refuse anything cloud, we offer a sovereign deployment pattern: an open-source AI model running on your own hardware inside your walls. Nothing leaves your perimeter, and no US-incorporated provider is in the chain.

We are direct about the trade-offs (longer setup, additional configuration work, hardware investment on your side) before you commit. This pattern is scoped and priced separately from a standard engagement.

No. The architecture is model-agnostic by design. You can move between Claude, GPT, Qwen3, Apertus, or any future frontier or open-source model with a configuration change rather than a rebuild. The same applies across Microsoft Azure, AWS, and your own hardware. Lock-in is a vendor problem, not a Fiducia AI design choice.

Confidentiality is governed by your existing access controls and tenant boundaries, not by ours. The agents run inside your dedicated Azure tenant or AWS account, with secure connections to on-premise systems where needed. No data leaves your tenant. No information is shared between clients. Each engagement is fully separated.

No. The enterprise AI services we use inside your tenant, such as Azure Foundry or Amazon Bedrock, are governed by contractual no-training and data-handling commitments from your cloud provider. Your data is not used to train third-party models, and is not visible to other clients or to Fiducia AI.

A direct answer, since most providers do not give one. The Azure Switzerland and AWS Zurich regions are physically Swiss. Their corporate parents, Microsoft and Amazon, are US-incorporated and remain within reach of the US CLOUD Act. No private contract overrides US extraterritorial law.

For most external asset managers and multifamily offices the practical risk is low: clients are not US persons, the data has no US nexus, and with customer-managed encryption keys the cloud provider holds only ciphertext it cannot read without your cooperation.

For senior single-family offices, foundations, and holdings whose threat model includes adversarial legal process, governmental compulsion, or geopolitical risk, we deploy the sovereign on-premise pattern instead.

No. An AI agent inside your own environment functions like any other authorized internal tool, comparable to secure email between you and your client. It receives content, applies its rules, and returns the output to the same authorized user. Nothing leaves your confidentiality perimeter. Privilege concerns generally arise when privileged material is shared with external consumer AI services, which is the opposite of how Fiducia AI is deployed.

No. The agents are designed and configured by Fiducia AI to fit your existing workflows. Your team interacts with them in natural language, the same way they would brief a human assistant. Your relationship managers, analysts, and trustees stay in their craft. The conceptual layer of the work, what to ask, what matters, who the client is, remains entirely yours.

Mistakes are treated as input, not incidents. Most fall into two categories, and both are fixable: if the agent misunderstood an instruction, we refine the prompt or rule; if the agent lacked context, we add it to its knowledge base. A structured feedback loop captures these corrections so the agent gains experience over time rather than repeating the same mistakes. Critical decisions stay with humans in the loop, and every action is logged. Agents are tools, not unsupervised autonomous workers.

Yes. We will not deploy any model below a defined size and capability floor for compliance or due-diligence work. Below that threshold, models hallucinate and miss subtle clauses at rates that are not acceptable for regulated use.

This is a technical floor. Commercial considerations do not lower it. It rules out the cheap consumer-grade models some vendors quietly use behind the scenes.

Operational continuity is built into the architecture. Because agents run inside your own environment, they are governed by your existing business continuity plan and your cloud provider's SLAs, the same framework that protects the rest of your IT operations. There is no separate Fiducia AI platform that needs to stay online for your team to keep working. On our side, we maintain incident response procedures and can quickly restore agent configurations; on your side, your existing BCP already covers the infrastructure agents run on.

No. The goal is to invert the 80/20: today most relationship managers and analysts spend 80% of their time on admin and 20% on the relationship. Agents take the admin layer so your team can spend their time on what AI cannot do, which is the trusted human relationship at the core of this business.

Swiss multifamily offices, external asset managers (EAMs), single family offices with operational complexity, and small holdings managing multiple entities. The common pattern is small expert teams under regulatory and cost pressure, still running on Excel sheets, manual reporting, and fragmented systems.

Four core pillars, plus custom workflows: due diligence on direct investments and portfolio companies; compliance and KYC; market intelligence; prospecting and client acquisition. If your team can describe how they do something, we can build an agent that does it alongside them.

Different category. Microsoft Copilot is a productivity assistant embedded in Word, Outlook, and Teams. It uses a small fraction of what the underlying models can do.

We build on Azure Foundry, which gives direct access to the frontier models (Claude, GPT, and others) with the configuration controls required for compliance, due-diligence, document analysis, and agentic workflows. Most family offices running Copilot today are using a small slice of what is available, often without realizing it. Foundry is where the real capability sits, and building on it at scale is exactly what Tomasz did at Microsoft for 17 years before co-founding Fiducia AI.

Yes. For clients with strong sovereignty requirements, we deploy Apertus, the Swiss national large language model built by EPFL and ETH Zurich, with native Swiss German support. This is the strongest sovereignty option for senior single-family offices and foundations, and it pairs naturally with our sovereign on-premise deployment pattern.

Concrete examples from current engagements: a single family office in Zurich reduced quarterly due diligence from 120 hours per analyst to 12, in one week. The agent also surfaced five forecasting errors that had gone undetected across multiple analysts and years.

A multifamily office in Basel reduced monthly client reporting from one full day to two to three minutes per client, with personalization per family.

We start with a focused pilot on one workflow, typically delivered in weeks. From there we expand based on what we learn together. You see ROI inside the pilot.