Destinations
Landed supports 5 destination types. Your data is loaded into the destination after each sync, with automatic schema creation and evolution.
| Destination | Type | Setup Guide |
|---|---|---|
| BigQuery | Cloud data warehouse | Guide |
| Snowflake | Cloud data warehouse | Guide |
| PostgreSQL | Relational database | Guide |
| Redshift | Cloud data warehouse | Guide |
| DuckDB | Embedded analytics | Guide |
How Destinations Work
When Landed syncs data from a connector, it:
- Creates tables automatically in your destination using the naming pattern
<connector>__<stream>(e.g.,stripe__customers,hubspot__contacts) - Evolves schema when new fields are detected at source -- columns are added automatically
- Writes metadata columns for tracking:
_landed_synced_at-- when the record was last synced_landed_active-- whether the record is currently active_landed_deleted_at-- timestamp if the record was deleted at source_landed_source-- the connector that produced this record_landed_sync_id-- unique ID of the sync run
Network Access
If your destination is behind a firewall, allow Landed's static egress IPs:
| Environment | IPs |
|---|---|
| Production | 34.170.185.84, 35.192.90.94 |
| Staging | 34.171.93.34 |