Kognitos

Kognitos ships more than a hundred and thirty pre-built connectors to enterprise systems, naming SAP, Oracle, NetSuite, Workday, Salesforce, ServiceNow, Microsoft 365, Google Workspace, Snowflake and Databricks among them. The documentation carries a per-integration reference page for each, covering storage, messaging, document and line-of-business systems. Connections are described as self-healing when the target system changes, and automations take actions in those systems rather than only reading from them.

Sourcekognitos.com/platformread 2026-09-17

An automation is a published, versioned workflow. Drafts are built, tested and published, each publish creating a new locked major version, and the detail view carries a visual diagram of the workflow, the run history and the exceptions raised. Runs execute multi-step processes across the systems the connectors reach, and automations are organized into workspaces so they can be reused across teams.

Sourcedocs.kognitos.com/guides/platform/automationsread 2026-09-17

Documents are read and acted on: the documentation carries document, DOCX, CSV and email file integrations, a document automation type, and connectors to content systems such as Confluence, so data is extracted from files and used in a run. No index, retrieval layer, knowledge base or citation surface is documented, so nothing shows which sources can be indexed, refreshed and permissioned, or which documents influenced an output. Extraction stands in place of grounding rather than answering it.

Sourcedocs.kognitos.com/guides/platform/integrationsread 2026-09-17

When an automation hits a condition it has not been taught to handle, it raises an exception and pauses to ask for help. The run does not proceed until a person supplies guidance, and the Guidance Center is where those requests are answered across automations. Guidance that is saved becomes a Troubleshooting Guide entry that auto-applies to future runs. Guide entries are governed rather than automatic, with guide approval granted and guide approval rejected recorded as audited governance actions in the Audit Log, so an approval sits at both the run and the policy layer.

Sourcedocs.kognitos.com/guides/platform/automations/troubleshooting-guideread 2026-09-17

SOC 2 Type II reports, HIPAA attestations, GDPR addenda and ISO 27001 evidence are published on a continuous-release cadence through the Kognitos trust portal, the vendor states.

It names the customer-facing controls alongside them: role-based access control with a documented roles and permissions model, identity integration with Azure AD or Entra, Okta and Google Workspace, encryption in transit and at rest, tenant isolation and key management.

It also states a hard training boundary, that no customer prompts, documents or extracted values are used to train upstream foundation models.

Sourcekognitos.com/about-usread 2026-09-17

Every run is inspectable step by step through the automation document and diagram views. The run list filters by status, date and trigger type, and a Performance Dashboard covers runs and exceptions. Separately from run history, an audit log records the actor (the person or system that performed an action), the event and the specific operation beneath it, including approval and governance actions. The audit log has filtering, a documented export, and rules for who can see what.

Sourcedocs.kognitos.com/guides/administration/audit-logread 2026-09-17

What persists between runs is a Troubleshooting Guide entry, a resolution saved from an exception that the platform checks and applies automatically the next time the same condition occurs. That is learning absorbed into the automation's own behavior, governed through guide approvals, rather than a memory layer. The documentation shows no memory store, no state carried across sessions for a user or an agent, and no surface for viewing, editing or deleting what an agent retains.

Sourcedocs.kognitos.com/guides/platform/automations/troubleshooting-guideread 2026-09-17

According to Kognitos, its architecture and security document covers regional data residency across North America, EMEA and Asia Pacific, alongside tenant isolation and key management. The documented application and MCP endpoints are regional hosts. The residency statement names three macro-regions without a way to select one, and no self-hosted, on-premises, private-cloud or customer-environment option is documented.

Sourcekognitos.com/about-usread 2026-09-17

Pre-built workflow templates are offered for finance, healthcare, supply chain, human resources and IT, covering the most common starting points, Kognitos states. Only the domain families are named. No catalog page, enumerated template list or anything a buyer can browse and select from appears on the website or in the documentation.

Sourcekognitos.com/platformread 2026-09-17

Three trigger types are documented for a published automation. An email trigger starts a run from an incoming message. A schedule runs the automation automatically and is available for automations without required inputs. A webhook lets an external system start a run and pass its data in as inputs. The run list can be filtered by trigger type, recorded per run as manual, email or webhook, so work reaches the automation without a person starting it.

Sourcedocs.kognitos.com/guides/platform/automationsread 2026-09-17

Kognitos runs its own neurosymbolic engine, where a language model interprets the English instruction and a symbolic engine executes it deterministically. No setting in the documentation lets a customer or administrator choose, route between or supply the model doing that interpretation. Language-model providers do appear in the integration directory, but that is an automation calling a model as a tool rather than choosing the model that runs the platform.

Sourcedocs.kognitos.com/guides/platform/integrationsread 2026-09-17

Kognitos publishes a REST API at a documented base URL with personal access token authentication and reference pages for automations, runs, exceptions, files, books, analytics, workspaces and organizations, including invoking a published automation and reading back a run.

It also hosts its own MCP server at a documented URL over streamable HTTP, with OAuth 2.1 or API key authentication and named tools for listing automations, starting runs, inspecting exceptions and managing schedules. The Kognitos MCP Server page carries an explicit warning about connecting it to automations that ingest untrusted input.

Sourcedocs.kognitos.com/guides/mcp/mcpread 2026-09-17

A draft is where a workflow is built, edited and tested. The documentation has the author review the automation document, then run and test it by providing inputs before publishing, and publishing creates a locked version that can be edited as a draft again. Testing with fixtures, mocks or datasets before production is not documented, nor is scoring output quality over time, and no regression suite appears in the documentation.

Sourcedocs.kognitos.com/guides/platform/draftsread 2026-09-17

Browser automation is documented as an integration in its own right, through the Browser and Browser Use integrations, used to reach applications that expose no interface to integrate against. The documentation describes the agent being confined to a restricted set of approved browser actions rather than arbitrary code execution. This is control of a real interface, and it is the route Kognitos names for legacy systems where a connector does not exist.

Sourcedocs.kognitos.com/guides/platform/integrations/browserread 2026-09-17