Skip to content
Back to

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 Apache Arrow datasets on an encrypted, workspace-scoped file store; you push results to files, APIs, or catalog destinations on the way out.

Topics

Section titled “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 Arrow storage and Core Fontana data principles
  • Data lineage - atomic provenance from ingress to export, OpenLineage export
  • Egress - Save File Export, REST and GraphQL API nodes, downstream connectors, and export paths

Connector catalog

Section titled “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

Section titled “Secrets for connectors and APIs”

Connector and API credentials never appear in workflow config as plaintext. You configure secrets in Admin or node settings; values resolve from HashiCorp Vault when a run executes.

  • Distinct from BYOK LLM keys (separate scope and Admin surfaces)
  • Scoped to your workspace; never returned to the browser
Section titled “Related documentation”