Existing tools and warehouse
Keep the tools that still do their job
Vendo works with your analytics, CRM, messaging, ecommerce, advertising, and warehouse tools — it connects the stack you have instead of forcing a new one.
Use your existing tools
Replace only the parts that create repeated manual work
Keep every tool that already earns its place. Vendo takes over the imports, shared definitions, reports, and syncs between them — the work nobody wants to do by hand.
Keep your analytics
If your analytics tool already serves your reporting workflow, keep it — Vendo imports from it and delivers to it.
Keep your business tools
Your CRM, messaging, ecommerce, and payment tools stay put. Vendo connects to each with its own authorization, fields, and schedule.
Keep your ad platforms
Import performance data from your ad platforms and sync conversions and audiences back to them.
Vendo handles the work between tools
Vendo does the importing, mapping, reporting, and delivery between your systems — your tools keep doing what they do best.
Choose the operating model
Decide where data lives and which AI client can access it
Bring your own warehouse
Connect BigQuery and keep your data in your own project.
Run Vendo on your own BigQuery project and dataset, with the access method you configure. Athena, Databricks, Redshift, and Snowflake run as managed setups — we’ll map out reads, writes, and data movement with you.
Bring your own AI
Use the built-in Agent or connect your own MCP client.
Claude, Codex, and other MCP clients can use the same Vendo tools as the Agent. Their API key controls which data and actions they can access. Use an existing AI subscription, choose the model provider, and keep control of the data.
Choose managed or customer-managed storage
Make the storage decision from your security and operating requirements.
Vendo-managed storage means zero infrastructure work. Customer-managed BigQuery gives your team full control of the project and dataset. Either way, you decide — and we help you plan any later migration properly.
Architecture you can inspect
See the tables, models, and job records behind every result.
Query the SQL, read the model definitions, trace the source mappings, and check the job records — no black boxes between your question and your answer.
BigQuery
Snowflake
DatabricksBigQuery supports customer-managed storage · Other warehouses use managed source setups
Implementation detail
See how every number is made
With your own BigQuery, the tables sit in your project where you can query them directly. Saved models and job records are open to inspection too — you can always see how a number was made.
Documented connectors
Every connector documents its authorization method, data direction, schedule options, and historical support — no guessing.
Managed jobs
Vendo runs the imports, models, and delivery jobs. You see every configuration, failure, and result.
Queryable warehouse tables
With your own BigQuery, the tables and views Vendo writes sit in your dataset — query them however you like.
Implementation you can trace
Source mappings, saved logic, tables, and run records are all there to inspect — follow any number back to its source.
Open interfaces
MCP, CLI, and REST APIs let approved software and AI clients work with the Vendo data and actions you allow.
Security and governance
Encryption, scoped credentials, and clear data movement for the exact deployment and integrations you choose.
Storage planning
Choose your storage now, migrate on your terms later
Choose the initial storage setup
Pick Vendo-managed storage for zero warehouse operations, or customer-managed BigQuery when you want project control.
Confirm access and data movement
For BigQuery, define the project, dataset, service account, and read or write permissions — we map data movement with you upfront.
Plan any later migration
Migrating storage later? Treat it like a release: inventory tables and history, update credentials, test models and reports, verify every destination.
Document ownership and exit requirements
We agree upfront on which tables live in your project, what you can export, and how offboarding works — your data stays portable.
FAQ