Current Source Status
Adequate Data should be marketed only around source paths that are implemented end to end.
Current customer-facing source paths: Snowflake, Google BigQuery, Amazon Redshift, PostgreSQL, MySQL, MariaDB, SQL Server, CSV upload, Excel upload.
| Source | Customer-facing status | What that means |
|---|---|---|
| Snowflake | Available to test | Available for a read-only connection test. Answers become verified only after the connection succeeds and proof is attached. |
| Google BigQuery | Available to test | Available for a read-only connection test. Answers become verified only after the connection succeeds and proof is attached. |
| Amazon Redshift | Available to test | Available for a read-only connection test. Answers become verified only after the connection succeeds and proof is attached. |
| PostgreSQL | Available to test | Available for a read-only connection test. Answers become verified only after the connection succeeds and proof is attached. |
| MySQL | Available to test | Available for a read-only connection test. Answers become verified only after the connection succeeds and proof is attached. |
| MariaDB | Available to test | Available for a read-only connection test. Answers become verified only after the connection succeeds and proof is attached. |
| SQL Server | Available to test | Available for a read-only connection test. Answers become verified only after the connection succeeds and proof is attached. |
| CSV upload | File workflow available | Available for uploaded files. Answers become verified only when rows are checked, saved, and tied to proof. |
| Excel upload | File workflow available | Available for uploaded workbooks. Answers become verified only when the workbook sheet, rows, and proof details are captured. |
| Amazon S3 file source | Not customer-ready | Not shown in the customer connector setup yet. |
| Oracle | Not customer-ready | Not shown in the customer connector setup yet. |
| Databricks SQL | Not customer-ready | Not shown in the customer connector setup yet. |
| MongoDB | Not customer-ready | Not shown in the customer connector setup yet. |
| SQLite | Not customer-ready | Not shown in the customer connector setup yet. |
| Generic SQL | Not customer-ready | Not shown in the customer connector setup yet. |
Do not claim blanket connector coverage until each source is enabled, tested, and documented end to end.
Connection Guidance
Use read-only credentials for connected sources. The product should not need write access to answer business questions.
Recommended setup:
- Create a dedicated read-only user
- Limit access to the schemas needed for the questions
- Enable encrypted connections where the source supports them
- Confirm warehouse query limits before running a proof workflow
- Document the source, schema, filters, and definitions in the receipt
CSV Evidence
CSV and Excel upload are useful lightweight evidence paths.
A receipt export for a file answer should capture:
- File name
- Sheet name when relevant
- Row count
- Data fingerprint
- Columns used
- Cleaning or normalization assumptions
- The calculation used against the file
Data Flow Note
Do not describe the product with absolute data-residency language unless a deployment is explicitly designed and documented that way.
For the hosted app, use a specific statement instead: Adequate Data connects to supported sources, runs SQL for the investigation, processes result data in the application workflow, and may use configured AI services to generate explanations. Source credentials should be encrypted at rest and protected with least-privilege access.