Vorkar connects by protocol, not by a fixed list of named systems — so you don't need us to "support" your specific system. You need to know how it speaks. This guide shows how to connect anything, including software you built yourself.
The same four steps work for a big-name SaaS, a database, or an app your team wrote. Only the details change.
Does your system speak REST, SOAP, SQL, NoSQL, or does it expose files (SFTP or a network drive)? Most systems state this in their own docs.
How does it prove who you are — an API key, OAuth, a username & password, a token, or a certificate / connection string?
The endpoint or host, the credentials for your auth type, and what you want Vorkar to read.
Enter the details. Vorkar tests the connection, installs any driver or library it needs automatically, and connects — about 5–10 minutes when the prerequisites are in place.
The named systems below are examples, not a catalog. If your system speaks one of these protocols, it can connect — including software you built yourself. Nothing is "coming soon"; the protocol is what matters, not the brand.
HTTP/JSON web APIs — the common language of modern cloud apps and services.
XML web services described by a WSDL — common in older enterprise apps and ERPs.
Relational databases and warehouses queried with SQL.
Document and key-value stores that don't use SQL.
Systems that expose files rather than an API — file shares and exported data.
System and product names are the trademarks of their respective owners, shown only as examples of systems that speak each protocol — not partnerships or endorsements. Wording is Vorkar's own; follow each link for the vendor's official documentation.