support@vorkar.io — or use the form below. It reaches the same place.
An account on platform.vorkar.io and one system you can reach: a URL plus credentials (an API key, a DB user, or OAuth). That's it — nothing to install in your network, no data to migrate first.
Sign in, open Build, and click + Add connection. You pick a protocol (SOAP, REST, SQL, NoSQL, documents, chat) rather than a vendor. Test the connection, and the system appears on the canvas around Aura. Then go to Ask and ask it something.
Anything that speaks a standard protocol — REST, SOAP, SQL, NoSQL — or systems that expose files. That includes custom and in-house applications, not just major vendors.
Yes. Vorkar connects by protocol, so if your system speaks REST, SOAP, or SQL — or exposes files — it can connect, including software you built yourself.
Vorkar installs what the connection needs automatically when you configure it. You don't set up dependencies by hand.
The Vorkar platform runs in any modern browser. The downloadable device agent — used to connect a machine's local files — is available for Windows and Linux today. A macOS agent is in progress. You don't need the agent to use Vorkar with cloud and networked systems; it's only for connecting a local machine.
Roughly 5–10 minutes per connection when the prerequisites are already in place.
No — that's your call. Vorkar connects to a sandbox or test environment just as easily, and many teams start there before connecting production.
No. Anyone can ask questions in plain English. Connecting systems is an admin task; asking isn't.
Those show what each system reports about itself. Vorkar correlates records, logs, and health across systems to explain what actually happened — an answer that isn't in any single system.
Not by default. Training on your data is off unless your organization's admin turns it on. If you do enable it, it's used only to improve results on your own data — and we never sell your data to anyone. Enable it if you want the system to learn from your data and improve for you.
$0 platform fees to start. Try it with our evaluator package, and buy when it's proven itself for you. See the pricing page for how usage-based billing works beyond the free tier.
Open Build and click the system — the node shows its live status and the real error. Most red nodes are one of: expired credentials (use the node's reconnect control), a system that's unreachable right now, or credentials not configured for that environment.
Still stuck? Email support@vorkar.io with the system name and the error text shown on the node, and we'll dig in.
Goes to the same inbox as support@vorkar.io. Include the system and the exact error if you have one.