Custom Integrations
How Vendo handles custom and managed integrations that are not available as self-serve setup.
Last reviewed September 15, 2026
Some integrations are available only as managed or custom implementations. Vendo does not offer them as general self-serve setup until a customer need justifies the product work and the connector passes the launch-readiness checks.
What Custom Means
| Status | Meaning |
|---|---|
| Live | Available through the normal product setup path and tested for the documented use case |
| Managed | Available through setup that Vendo does for selected customers or early users |
| Custom | Built or enabled when a customer asks and the implementation is scoped |
| Coming soon | Planned, but not available for customer use yet |
How Setup Works
- Contact Vendo with the source or destination you need.
- Vendo confirms the necessary APIs, permissions, expected data, and business use case.
- Vendo scopes the setup, validation checks, known limits, and support expectations.
- Vendo implements or enables the integration for the account.
- Vendo validates the first sync against row counts, timestamps, duplicate checks, and expected fields.
Before Requesting a Custom Integration
Have this information ready:
- Platform name and account/workspace URL
- Source or destination direction
- Necessary data objects or events
- Owner of the credential or OAuth permission
- Expected warehouse tables or destination objects
- Launch deadline and success criteria
Support Expectations
Managed and custom integrations get high-touch support during setup. They can require manual validation, more monitoring, and runbooks for the account. Vendo will not present a custom integration as self-serve until the setup path, docs, credential checks, and operational recovery path are part of the product.
Last updated on