Asset managers and allocators
Client books, positions, and operating specifications are sensitive. Uploading operational payloads to a vendor-only cloud can conflict with confidentiality commitments and data-residency policies.
Operating data stays on infrastructure you control.
Fontana ships as modular Docker images in one signed platform release. Run managed cloud, dedicated single-tenant, or on-premises behind your firewall; the same governed workflows, controls, and audit evidence in every model.
When "cloud-only" is a dealbreaker.
For regulated financial operations, running the control layer only as someone else's multi-tenant SaaS is not a small inconvenience; it can block legal review, residency commitments, and internal security policy.
Banks and regulated markets firms
Internal security policy and supervisory expectations often require workloads, credentials, and evidence to remain inside approved jurisdictions, or entirely inside the firm's network.
Administrators and custodians
High-volume file intake, reconciliations, and exception evidence cross many clients. Teams need isolation, retention control, and replay without sending that context to an unmanaged third-party plane.
Procurement and risk review
Questionnaires ask where customer data lives, who operates the environment, and whether AI context leaves the estate. Cloud-only answers stall deals that require dedicated or on-premises paths.
One platform. Three clean deployment models.
Same governed workflows, deterministic execution, lineage, replay, and audit evidence, whether you start in the cloud, isolate a dedicated tenant, or run entirely on-premises.
SaaS
Cloud
Multi-tenant or your cloud account
- Fastest path to a governed environment with Fontana-managed or customer-operated cloud
- Same release artefact and Terraform modules on AWS, GCP, or Azure
- Automatic platform updates on managed footprints
- Ideal when reviewers accept a qualified cloud boundary
Single-tenant
Dedicated
Isolated environment
- Dedicated compute, storage, secrets, and observability per buyer
- Managed by Fontana or operated in your account with isolation guarantees
- No shared multi-tenant plane for operational data or evidence
- Ideal for enterprises that need cloud convenience with bounded blast radius
On your floor
On-premises
Full control
- Modular Docker composition behind your firewall or in an air-gapped enclave
- Customer data, workflow context, and audit evidence stay on infrastructure you operate
- Same product build as cloud and dedicated, with no parallel fork
- Ideal when policy requires on-prem or private-network deployment
All deployment options include the full control layer: knowledge graph context, approval gates, deterministic workflow execution, model governance where enabled, and evidence packs by default, with no feature tiers tied to where you host.
Container-native delivery, not a cloud-only fork.
Fontana is engineered for deploy-anywhere operations: pre-built release contents, mount-based updates, and infrastructure declared in Terraform so technology and risk teams can reproduce what they reviewed.
Modular Docker images
Each platform service ships as a container image. Compose them into one environment without installing application code onto bare hosts beyond boot and orchestration.
One signed release artefact
A single `fontana-release.tar.gz` drives first boot and upgrades. Replace the release to refresh every mounted service, with no per-service rebuild cycle for operations teams.
Cloud-agnostic by design
The same images and operational footprint run on hyperscaler VMs, dedicated fleets, Kubernetes, or on-premises Docker. Move environments without rewriting the product.
Compute
Hardened fleets with health-checked rollouts; dedicated and on-prem paths use the same container entrypoints as managed cloud.
Data
Encrypted storage, scoped secrets, and tenant-aware boundaries, configured for the deployment model procurement approves.
Evidence
Lineage, approvals, replay material, and audit trails are produced in the run, wherever that run executes.
Choose the hosting model reviewers will sign off.
Every column is the same product. The difference is where compute runs, who operates it, and how data residency commitments are met.
Capability
Cloud
Dedicated
On-premises
Who operates the environment
Fontana-managed or your cloud account
Fontana-managed or your team on isolated resources
Your operations team on your network
Data residency
Qualified cloud region or customer cloud boundary
Isolated tenant; no shared operational plane
Stays inside your building or private network
Release and updates
Signed platform release with rolling cutover
Same release artefact; isolated rollout
Same release artefact; customer-controlled schedule
AI and model context
Governed routing; approved providers and logging
Same governance; isolated execution boundary
Policy-bound; can limit or disable model calls
Audit and replay
Full lineage and evidence packs
Full lineage and evidence packs
Full lineage and evidence packs