Cazana

Delivery and access

How feed files reach you, over SFTP or S3, and what to expect from each delivery.

Feeds are delivered to your own storage. Choose the transport that fits your systems when you subscribe. You can receive different feeds over different transports if you need to.

SFTP

SFTP is the default transport and is managed end to end by Cazana.

  • Connect to sftp.cazana.com with any standard SFTP client or library, using the username we provide.
  • We create an SFTP user scoped to your own directory. You cannot see other clients' files, and they cannot see yours.
  • Authentication is by SSH key (send us your public key; recommended) or password.
  • Files land under your feed directory, for example /feeds/sale-events/.

See Getting started for what we need to set this up.

S3

If you work in AWS, we can deliver to S3 instead.

  • We write to your bucket. You grant a role we can assume, and we deliver to the bucket and prefix you choose.
  • Or you read from ours. We provide a bucket and access for you to pull from.

Cadence and naming

  • Feeds are published daily, overnight.
  • Each file is named for its feed and date, for example sale-events_2026-06-19.jsonl.
  • Recent files are retained so you can re-fetch a delivery you missed. Ask your account manager about the retention window for your subscription.

Full snapshots

Every delivery is a complete snapshot of the dataset as at the build date, not a list of changes since the last file. To stay current you replace your copy with each day's file rather than merging changes. This keeps loading simple, and means a missed day never leaves a gap because the next snapshot is whole.

Coming soon

Further transports are planned, including a direct download portal and an HTTPS push and pull option, along with webhooks that notify you when a delivery is ready. Talk to your account manager if one of these would suit you better than SFTP or S3.