Connectors

Connect any source.

Orves Kore is designed to connect to the systems your company already runs on, then keep every answer linked to the exact source it came from. If we do not have a connector yet, the connector SDK is designed to build one.

Get a demo

Catalogue

Every kind of source, by category.

Status is shown connector by connector. We never list a connector as available before it is.

available built, works today built and verified with an acceptance receipt verified on recorded data passes acceptance on recorded API traffic; live-account certification pending roadmap planned

Category	Connectors	Status
Documents and media	PDF, Office files, audio and video	available
SaaS apps	Salesforce, HubSpot, RD Station	verified on recorded data
SaaS apps	Support, IT service and engineering tools, such as Zendesk, Jira, Confluence, ServiceNow and GitHub	roadmap
Business suites	SAP, TOTVS Protheus and RM	verified on recorded data
Business suites	Omie, Sankhya	roadmap
Databases	Postgres, MySQL and MariaDB, SQL Server, Oracle: read-only, incremental sync, change capture where the database offers it	built and verified
Data warehouses	Databricks, Snowflake: read in place	verified on recorded data
Data warehouses	BigQuery, Redshift	roadmap
File storage	CSV, XLSX and JSON files; cloud buckets, SFTP and SMB shares	built and verified
File storage	Parquet files	roadmap
Email and chat	Microsoft productivity suite, Google Workspace	verified on recorded data
Email and chat	Slack	roadmap
APIs	Any REST API with an OpenAPI description, any SOAP service with a WSDL: generated adapters	built and verified
Anything else	Your own connector, built on the connector SDK	built and verified

Connector SDK

One contract every connector must pass.

Each connector, ours or yours, is admitted by the same conformance suite before it runs.

Rate limits

Designed to respect each source's limits, with retry and exponential backoff when a source pushes back.

request → limit → backoff → retry

Schema evolution

Designed to detect when a source changes shape and carry the change through, instead of breaking the sync.

source schema → change detected → mapped

Resumable sync

Designed for full and incremental sync, deletes, change capture where available, and checkpoints that resume after a failure.

cursor → checkpoint → resume

Read-only, permissions kept

Designed to read without writing back, to capture source permissions, and to keep credentials in your own vault, out of logs.

source ACL → Orves Kore → per-caller access

Ways in

Bring a source we do not list.

Option	What it does	Status
Connector SDK	Write a connector in Rust and run it through the conformance suite	built and verified
Generic REST adapter	Generate a connector from an OpenAPI description	built and verified
SOAP adapter	Generate a connector from a WSDL description	built and verified
Generic database adapter	Generate a connector from SQL table definitions, read-only	built and verified
MCP	Serve Orves Kore knowledge and verification to any MCP client, with per-caller authorization	built and verified