Trust and deployment
A credible finance answer needs more than fluent language. It needs an approved definition, an authorised route to the data, a deterministic calculation and enough source context for finance to challenge the result. Précis is designed around that chain.
| Period | Scenario | Account | Cost centre | Amount |
|---|---|---|---|---|
| 2026-Q1 | Actuals | 4000 Revenue | CC-100 | 1,816,420 EUR |
Customer environment
Précis is designed as a single-tenant deployment in the customer's AWS, Azure or GCP environment, in a region the customer selects. The application and data services sit behind customer-approved ingress; databases and internal services do not need public endpoints.
Source systems remain the systems of record. Précis uses ClickHouse for analytical reads and planning data and PostgreSQL for platform state. The full Précis application uses outbound TLS to the customer's selected supported language-model provider; optional web access can be disabled and restricted per deployment. The standalone Finance MCP server has no model-provider egress of its own.
Bring your own model provider
Précis keeps the model relationship under the customer's control, but the route differs by surface.
For application model calls, only the context needed for the interaction can cross the configured outbound TLS route: conversation and task instructions, tool schemas, authorised tool results and file content the user explicitly selects. Database credentials, platform secrets, unattached files and raw source rows not selected by an authorised operation remain outside that model request.
Governed finance layer
Metrics, statement layouts, hierarchies, scenarios and aggregation behaviour live in governed catalogue definitions over semantic views. A client asks for a named finance operation; deterministic code applies the approved definition to the permitted data.
The language model does not estimate a missing number or calculate a financial statement in prose. When the requested definition or data is absent, the correct response is to say so.
What is a finance semantic layer? →
Enforced at the tool boundary
Précis delegates authentication to an OpenID Connect issuer: the bundled Keycloak reference configuration or a customer's external OIDC provider. The server validates signed tokens and resolves the caller to a platform identity.
Authorisation is enforced before a tool body runs. An access profile can grant specific finance data domains and scenarios, then narrow them by dimension—for example, to one division. The engine intersects the requested filters with that permitted scope before retrieval. The user or agent cannot remove or widen it. The application, Excel add-in and external MCP transport converge on the same permission gate.
Different surfaces, explicit permissions
Evidence behind the answer
Results retain the definition and available dimensions needed to understand the figure: scenario, period, account, cost centre and other approved context. Finance can move from a statement or metric towards the permitted source detail without asking a model to reconstruct the calculation.
Security denials, profile changes and administrative actions have durable audit records. Tool execution is also traced.
Reporting a vulnerability
For the source-available engine, use GitHub private vulnerability reporting in the Précis Finance MCP repository. Do not open a public issue for a suspected security problem.
Report privately →We can walk through the deployment, model-provider, identity, access and evidence boundaries against your requirements.