Integrations
Terri connects to what you already run.
93 systems across ERP, plant-floor equipment, labor and harvest, quality, databases, message queues and files. Your ERP stays the system of record, and nobody changes how they work.
93systems across 11 shelves
- 74 self-serve
- 8 assisted
- 11 on request
One outbound-only tunnel to your private network.
Every system, by shelf
- Self-serve
- You connect it yourself.
- Assisted
- Terrantic configures the source per site first.
- On request
- Terri can consume it, and the connector is built when you need it.
Labor & harvest
Crew time, piece counts and payroll exports from the field and the packing floor.
Self-serveFieldClock
Labor payouts, crews, blocks and piece rates.
Self-serveHarvest Clock
Harvest tickets and crew hours.
Self-servePickTrace
Payroll exports by site, job, crew and employee, plus a file-drop template.
- Self-serve
UKG
Time and attendance exports.
Self-serveTimeClock Plus
Punch data and job codes.
ERP & packhouse
The systems of record for lots, inventory, sales, settlements and sizer output. Vendor connectors ship with the tables, change signals and first datasets already declared.
- Self-serve
Famous
Inventory, sales orders, AR, grower accounting, runs; pre-authored datasets on day one.
AssistedCompac
SizerResults: batches, drops, grades, sizes, growers over the site tunnel.
AssistedUnitec
Lot, process and calibration tables; one row per packed unit.
- Assisted
MAF Roda
Lot delivery grading results per season.
AssistedGreefa
Sorting results from report exports or per-lot machine files.
AssistedCompu-Tech AS/400
Direct IBM i read with packed, non-packed and pallet-tracking views.
AssistedCompu-Tech SFTP
Scheduled CSV drop ingested on arrival.
AssistedSIMS
Packing-line telemetry, one line per integration.
Self-serveHectre
Image and quality datasets with source reconciliation and gated promotion.
- Self-serve
VanDoren / Tomra
Machine endpoints via change data capture.
On requestRedLine WMM
Warehouse and material movement.
On requestFreshCloud
Cloud packhouse platform.
- On request
Ellips
Optical grading.
- On request
Elifab
Sorting lines.
- On request
Aweta
Grading and packing lines.
On requestCVM
Packhouse software.
Plant floor, MES & business systems
Line controllers and enterprise systems the platform states it can consume; a connector is built when a customer needs it.
- On request
Siemens
MES and S7 controllers (S7 also reachable today as a plant-floor protocol below).
- On request
AVEVA
Historian and MES.
- On request
PTC
Kepware and ThingWorx.
- On request
Microsoft Dynamics
Business Central and F&O.
Quality & food safety
Inspection and compliance records.
On requestProvision Analytics
Food safety records and audits.
Sheets, forms & files
Where a lot of a packhouse still lives. Drag a workbook onto the Datasets page or connect the sheet.
- Self-serve
Google Sheets
A sheet as a scheduled source.
Self-serveSmartsheet
Sheets and reports on a cadence.
- Self-serve
Excel workbook
xlsx, xlsm, xls, xlsb, ods; sheet picker and region read.
- Self-serve
Parquet
Columnar files, plus CSV, TSV, JSON and BSON.
- Self-serve
Terrantic Forms
Targets, QC and shift entries captured in-app and queried like any dataset.
Databases (direct)
Browse the live schema, pick tables, set each table’s change signal and cadence. Modern relational systems connect natively.
- Self-serve
SQL Server
Row version, timestamp or key change signals; catalog scope across databases.
- Self-serve
PostgreSQL
- Self-serve
MySQL / MariaDB
- Self-serve
Oracle
System change number as the change signal.
- Self-serve
ClickHouse
- Self-serve
Snowflake
- Self-serve
Trino
- Self-serve
IBM Db2
Native driver, or the jcc bridge on Linux/Unix/Windows.
- Self-serve
BigQuery
Google Cloud warehouse.
- Self-serve
Redshift
AWS warehouse.
- Self-serve
Cassandra
Wide-column store.
Databases (legacy & single-file, via bridge)
The same five verbs and the same live exploration, through a platform bridge. One selection on the Database integration, not a separate path.
- Self-serve
IBM i (AS/400)
jt400 bridge; write-back available under a separate account. Green-screen programs can be driven where logic lives only in RPG.
- Self-serve
SQL Server 7.0 to 2005
jTDS bridge for legacy instances.
- Self-serve
Sybase ASE
jTDS bridge; write-back available.
Self-serveFirebird
Jaybird bridge.
- Self-serve
IBM Informix
- Self-serve
Microsoft Access
A file inside a mount; whole-table export per sync.
- Self-serve
DuckDB
A file inside a mount; change signal sent as data, never in the statement.
- Self-serve
SQLite
Read as a file source.
Message queues
Always-on consumers. Every message lands as a row stamped with receive time and source; batch by count, bytes, time or condition.
- Self-serve
Kafka
SASL PLAIN and SCRAM.
- Self-serve
MQTT
Including Sparkplug B payloads, one row per metric.
Self-serveAMQP 0.9
RabbitMQ and compatible brokers.
Self-serveAMQP 1.0
Azure Service Bus, ActiveMQ.
- Self-serve
NATS
Core and JetStream.
- Self-serve
Redis
List, pub/sub and streams.
- Self-serve
NSQ
Authenticates by network reachability and TLS.
Self-serveNanomsg
PULL and SUB sockets.
- Self-serve
Azure Queue Storage
- Self-serve
AWS SQS
- Self-serve
AWS Kinesis
Plant-floor protocols
Read over the site tunnel by a bridge inside the stream. Sizers, lines, chillers, dock doors and PLCs, without a gateway product in between.
Self-serveOPC UA
Subscribe to named nodes; one row per value change, optionally per server event.
- Self-serve
Modbus TCP
Declare each register’s address, type and meaning; rows only on change if wanted.
- Self-serve
EtherNet/IP
Rockwell ControlLogix and CompactLogix; the controller publishes its tag list.
- Self-serve
Siemens S7
S7-1200 and S7-1500; one data block fetched in a single read.
- Self-serve
BACnet
Chillers, cold rooms, dock doors, air handling; polled every 10 seconds by default.
- Self-serve
Sparkplug B
MQTT payload format; metrics named as the equipment names them.
Storage & file locations
Attach a file location as a read-only synced copy, or push files to storage Terrantic hands you. Only changed files transfer, and a file is replaced whole.
- Self-serve
AWS S3
And every S3-protocol service.
- Self-serve
Google Cloud Storage
- Self-serve
Azure Blob Storage
- Self-serve
Azure Files
- Self-serve
Oracle Cloud Object Storage
- Self-serve
Cloudflare R2
- Self-serve
Backblaze B2
- Self-serve
NetApp StorageGRID
- Self-serve
Dell ECS
- Self-serve
IBM Cloud Object Storage
- Self-serve
Alibaba Cloud OSS
- Self-serve
Huawei Cloud OBS
- Self-serve
Tencent Cloud COS
- Self-serve
Windows file share (SMB)
Mounted read-only; credentials stay in the copying sidecar.
- Self-serve
SFTP / FTP
Pull from yours, or push to a Terrantic SFTP account.
- Self-serve
SharePoint
Document libraries over WebDAV.
- Self-serve
Nextcloud / ownCloud
WebDAV.
- Self-serve
HTTP directory
A listing page as a location.
- Self-serve
Email attachments
A dedicated Terrantic address; attachments land as files.
- Self-serve
Terrantic storage
S3-compatible bucket and SFTP account minted per customer; WinSCP, rclone, AWS CLI.
Outbound
The same platform writes back: to systems, storage, queues and people.
- Self-serve
Webhooks
HTTP POST on a schedule or an event.
- Self-serve
Database writes
ClickHouse, MySQL/MariaDB, PostgreSQL, SQL Server, SQLite, Oracle, Snowflake; insert, upsert or full replace.
- Self-serve
Cloud storage writes
S3, Azure Blob, SFTP, FTP/FTPS as CSV, Parquet, JSON or Avro.
- Self-serve
Queue writes
Kafka, RabbitMQ, SQS, Kinesis, Azure Service Bus, Event Hubs, NATS, Redis Streams.
- Self-serve
Reports & exports
PDF, Excel, CSV, JSON; scheduled and emailed.
- Assisted
IBM i, legacy SQL Server, Sybase write-back
Inserts and statements under a separate, write-capable account.
No systems match that search. Tell us what you run and we’ll show you how Terri connects to it.
Names and logos belong to their owners and identify the systems Terri reads from or writes to.
One outbound-only tunnel.
Everything reaches your private network through one outbound-only tunnel. Terri reads from each system as often as that system allows, up to real time, and maps everything into one data model through the Context Layer. From graders and sorters it takes the structured results, such as grade, size and defects by lot, rather than raw camera feeds.
No rip and replace.
Your ERP keeps recording transactions, and your crews keep working the way they do today. Terri reads from your systems, writes back where you want it to, and adds the intelligence on top. New data sources are options you can add over time, never a requirement.
Don’t see your system?
Tell us what you run, and we’ll show you how Terri connects to it.
Tell us what you run.
In a demo, we’ll map your systems to Terri and show you what it sees once they’re connected.

