Plugins and data endpoints
Understand the capability, installation and target that connect your systems
A plugin defines executable capabilities. An installation configures an available capability in a workspace. A data endpoint gives a selected target a reusable workspace name. They solve different parts of a connection.
Three layers
| Layer | Equipment example |
|---|---|
| Plugin | Postgres provides supported database read/write capabilities |
| Installation | A configured read capability with database connection details and protected credentials |
| Data endpoint | A named source selecting the equipment table through that installation |
An endpoint is not a new database or a copy of the selected records. Saving it configures access. A read, query or pipeline run performs the actual work.
Direction and purpose
An ingress endpoint supplies data for reads. An egress endpoint receives writes. An ontology-store endpoint selects a supported fact store for ontology materialization and reads. Choose a capability and contract that support the intended purpose; a read installation does not become writable because an endpoint is named output.
Internal plugins cover supported systems and operations. Custom plugins can add capabilities that users build and publish. A custom name or manifest alone does not implement a connector; its runtime and contracts must actually support the operation.
Example: equipment measurements
Install Postgres read with credentials permitted to read the equipment table. Create a workspace ingress endpoint targeting that table. A project query can bind Equipment properties to its columns, or a pipeline can read and transform its records. Neither the installation nor the endpoint automatically starts recurring ingestion.
If writing a result, configure a supported write capability, an egress target and the required permissions/policy, then verify the receiving system after a bounded run.
Continue with setup
Use Plugins for installation and custom creation, your first endpoint for a complete connection example, and endpoint installation relationships for capability/target detail.