File, batch & object storage
Some consumers still require files on a schedule — SFTP drops for partners, Parquet in a data lake, CSV for legacy reporting. Streamvane extends scheduled export to file and object protocols.
Batch where batch belongs
HTTP feeds are production-proven for real-time operational contracts. File and batch connectors serve historical interval archives, regulatory retention and data-lake landing — usually at lower cadence (hourly or daily), using the same mappers with a different transport package.
Targets in this category
6 targets · 0 implemented / proven
SFTP / FTPS
CSV, JSON or XML drops for partners.
Azure Blob Storage
Parquet or JSON object landing.
Azure Data Lake Gen2
Parquet lake landing.
Amazon S3
Parquet or CSV to S3.
Google Cloud Storage
Parquet to GCS.
Scheduled CSV drop
Local or share-mount delivery.
Why it matters
Archives, retention and lake landing
The same computed KPIs, delivered as governed files for the consumers that need them.
Mercury-style mappers, file transport
File and batch connectors reuse the operational feed mappers and swap the transport — Global.Platform.Sftp, Global.Platform.BlobExport and friends. Ideal for partner batch contracts, regulatory archive and Parquet landing for Databricks Auto Loader.
- Partner batch contracts on SFTP / FTPS
- Parquet to ADLS / S3 for lakehouse ingestion
- Regulatory retention and historical archives
Same engine, same guarantees
Every target inherits the platform
Whichever destination you pick, it runs on the same Reactive Engine — with consistent semantics, client-owned Azure, enterprise security and a delivery lifecycle that fits your estate.
One KPI definition
Every target in this category consumes the same computed metrics — service level is service level, everywhere.
Client-owned Azure
Ingest, reactive processing and storage run inside your subscription. Connectors are the only thing that reaches outward.
Platform-package model
Each target ships as a Global.Platform.* package on the shared core — adding one is a connector, not a rewrite.
Built for your SDLC
Provisioned as code, shipped through your pipelines, secured in Key Vault — like any other service you run.
Map your destinations to the right connectors
Book a connector assessment and we'll match your KPI families to the targets in this category — on your own Azure tenant.
Streamvane by Tessovia · Azure · AWS · GCP · Your data, your keys