Overview

Fontana connects your workflows to 600+ upstream and downstream integrations through governed ingestion, secure processing, and export in the workflow engine. You bring data in on File Input, REST triggers, or PyAirbyte connectors; the workflow engine stores and transforms it as JSONL datasets on an encrypted, workspace-scoped file store; you push results to files, APIs, or catalog destinations on the way out.

Where data runs

File uploads, connector fetch, transforms, and exports execute on the workflow engine in your workspace namespace. Workspace secrets resolve from Vault at runtime; they are distinct from BYOK LLM keys. See Workflow orchestration for the reactive execution model.

Topics

• Ingress - File Input, REST Input, PyAirbyte connectors, and the upstream connector catalog
• Supported formats - File Input extensions for tabular, financial, office, markup, and image uploads
• Storage and processing - immutable, durable, auditable JSONL storage and Core Fontana data principles
• Data lineage - atomic provenance on the run, inspected from a selected cell in Flow, with optional OpenLineage export
• Egress - Save File Export, REST and GraphQL API nodes, downstream connectors, and export paths
• REST API node - HTTPS API calls in Manual or OpenAPI mode, with workspace secrets, typed output, and request limits

Connector catalog

Fontana ships mirror-pinned, digest-pinned connector images on GHCR with Trivy CRITICAL scanning as part of the SOC 2 supply-chain control set. Browse representative sources and destinations on the ingress and egress pages; the full Airbyte catalog runs inside the workflow engine via PyAirbyte with no separate Airbyte platform server.

Secrets for connectors and APIs

Data Connector and REST API credentials are workspace secrets. You add them in the Secrets section of the workspace Config tab, or with New secret… in a node’s secret field; the node stores a {{secret.NAME}} reference, and the value resolves from HashiCorp Vault when a run executes the node.

• Write-only: once saved, a value is never returned to the browser, agents, run files, or logs
• Resolved from the workflow’s own workspace only
• Distinct from BYOK LLM keys (separate scope and Admin surfaces)

Related documentation

• Security - encryption at rest, workspace isolation, supply chain
• Compliance evidence - data lineage and immutable audit trail
• Workflow orchestration - reactive execution engine and node families
• Deployment - supply-chain pinned connector images on production hosts