Data teams
12 min
Source support
Review connector families, supported operations, and credential expectations.
Source support
Connector availability can depend on deployment and plan. The Sources connection dialog is the current source of truth.
Data systems
| Family | Examples | Typical operations |
|---|---|---|
| Relational SQL | PostgreSQL, MySQL, SQLite, SQL Server, Oracle | Introspection, bounded SQL, joins, aggregation |
| Warehouses | ClickHouse, BigQuery, Snowflake, Redshift, Databricks | Analytics queries, aggregation, provenance |
| Document and key-value | MongoDB, DynamoDB, Firestore | Filter, projection, grouping, connector-specific aggregation |
| Files and object storage | JSON, CSV, Parquet, S3, GCS | File discovery and bounded queries |
| SaaS and tools | Stripe, GitHub, Linear, HubSpot, Salesforce, Slack, Notion, Shopify, Airtable, Intercom, Metabase | Approved connector tools and object access |
Capability differences
Not every connector supports the same joins, aggregations, freshness model, or write actions. Answerplane plans against connector capabilities and should not run a SQL engine against a NoSQL-only source.
Credential expectations
Use read-only accounts, narrow projects or schemas, stable network access, and an identified owner. Validate each connector with representative live data before production use.