ActQL Connectorsin development
Connect databases, SaaS APIs, files, and compute engines through capability-aware integrations.
Connectors go from ActQL out to other systems; drivers bring existing tools into ActQL. A Connector is not just an API wrapper: it tells the ActQL planner which physical capabilities it offers — Acquisition, Fixed Compute and Effect — with cost, transfer size and provider-specific constraints, and the common planner chooses the physical plan.
Capability is not authority.
Declaring that a Connector can update a system does not grant permission to run the update. Capability, resource binding, current authority and Effect admission are managed separately.
Application / Agent
↓
ActQL
↓
Connector SPI
↓
SaaS / DB / File / ComputeIn development.