| Organization | An isolated Venice workspace with its own Connector Configs, End User’s and Users | Your Company DevYour Company Prod
| Developer (You) |
| User | A developer using Venice to deliver great experiences! May belong to multiple Organizations. | | Developer (You) |
| End User | A customer of yours gives you access to their Resource as part of using your product. | james@gmail.comsama@openai.com
| Developer (You) |
| Provider | A product or service that your customers use (e.g. Chase, Quickbooks). This is a concept we may reference in docs / user interface but does not yet exist as an actual entity in the Venice API / Database. | | N/A |
| Connector | Source code adhering to the Venice Protocol, can be a direct connector (e.g. Quickbooks) which provides a single Integration or an aggregator connector (e.g. Plaid) that provides many Integration’s | | Venice Repo |
| Integration | An integration represents a Provider supported by a Connector. There can be multiple integrations for a single provider if multiple connectors support the same provider (e.g. Merge and Railz both gives you the ability to connect to Quickbooks, in addition we have a direct Quickbooks connector for a total of 3 Quickbooks Integrations). | Plaid’s integration with Chase- Venice Direct integration with
Notion
| Venice Connector |
| Connector Config | A specific configuration of a Connector. Contains developer account credentials (e.g. client_id, client_secret), and misc configs (sandbox vs. production). Some connectors does not require configuration (e.g. Postgres). In the future can also contain sync settings (e.g. Automatically sync all Plaid items using this config to our main postgres Resource). | Plaid sandbox credentialsQuickbooks clientId and secret
| Developer (You) |
| Resource | Associated with a specific Connector Config. Contains customer credentials (e.g. access_token) and gives you the ability to call Provider APIs. Typically created by an End User but could also created by you in the dashboard (which then belongs to your organization). Resource can also be used as either a Source or Destination within a Pipeline | Plaid ItemQuickbooks Company
| End User (Your customer) |
| Pipeline | Pipeline moves data from a Source to a Destination and contains persistent state used for incremental syncs. | - Customer
Plaid Item -> Developer Postgres - Customer
Quickbooks Company -> Developer BigQuery
| Developer (You) |
