Quick Start
Get a working pipeline with materialised dbt models in under 5 minutes. Every guide follows the same pattern: init a project, connect your warehouse and source, run doctor to check everything, then run the pipeline.
If you need to reset project state during testing, re-run init with:
skippr init <project-name> --resetThat resets the project's accumulated run state and recreates a clean working environment. Your skippr.yaml config is preserved.
Quick start guides
| Warehouse | Source in example | Best for | Guide |
|---|---|---|---|
| Snowflake | MSSQL | Production-style evaluation and the strongest launch path | Quick Start: Snowflake |
| PostgreSQL | S3 | Local evaluation without a cloud warehouse account | Quick Start: PostgreSQL |
| BigQuery | S3 | GCP-first evaluation | Quick Start: BigQuery |
Snowflake is the recommended starting point -- it's the most common production deployment. If you're evaluating locally, the PostgreSQL guide is a great option with no cloud account required.
All supported warehouses
Skippr supports nine warehouse destinations. The CLI workflow is identical for every one -- only the skippr connect warehouse command changes.
| Warehouse | Connector docs |
|---|---|
| Snowflake | Setup guide |
| BigQuery | Setup guide |
| PostgreSQL | Setup guide |
| Redshift | Setup guide |
| ClickHouse | Setup guide |
| MotherDuck | Setup guide |
| Athena | Setup guide |
| Databricks | Setup guide |
| Synapse | Setup guide |
Each connector guide covers authentication, permissions or network requirements, and troubleshooting. See the full Destinations overview for cloud storage and messaging destinations.
What every quickstart proves
- The runner reads source data and writes it directly to the destination.
- Skippr generates reviewable dbt output instead of hiding the result in a proprietary format.
- Authentication and control-plane services are cloud-backed, but row-level source data is not routed through that cloud path.
Not sure which to pick?
Start with whichever warehouse you already have access to. If you're just exploring, PostgreSQL is the easiest to run locally. You can always add more warehouses later -- Skippr projects support multiple destinations.