CLI vs Platform
CloudQuery offers two paths to get value from your cloud data: the CLI (self-managed) and the Platform (managed service). Both share the same powerful integration ecosystem — the right choice depends on your team’s needs and priorities.
Comparison
| CloudQuery CLI | CloudQuery Platform | |
|---|---|---|
| Deployment | Self-hosted on your infrastructure | Managed service |
| Interface | YAML config + CLI commands | Web UI + REST API |
| Setup time | Minutes (install + configure) | Minutes (sign up + connect) |
| Best for | Teams with infra expertise who want full control | Teams who want fast time-to-value with less ops overhead |
| Data storage | Your choice: PostgreSQL, BigQuery, Snowflake, and more | Built-in ClickHouse + optional export to any destination |
| Scheduling | Your orchestrator (cron, Airflow, etc.) | Built-in scheduling via UI |
| Querying data | SQL in your chosen destination database | Built-in SQL console + AI-powered query writer |
| Reports & visualization | DIY with external BI tools (Grafana, Metabase, etc.) | Built-in reports with 40+ templates |
| Customization | Full — custom integrations, transforms, SDK | Platform features + ability to export to any destination |
| Cost | Infrastructure costs only | Platform pricing (free tier available) |
Platform-exclusive features
The Platform includes capabilities beyond data syncing that aren’t part of the CLI:
- Asset inventory — Search and explore cloud assets with a built-in UI, saved searches, and custom columns
- Policies — Customizable compliance rules across all your cloud providers
- Automations — Event-driven triggers that respond to resource changes and policy violations
- Alerts — SQL-based alerting with webhook, Slack, and Jira notifications
- AI query assistant — Natural language to SQL for exploring your cloud data
Choose CLI if…
- You want maximum control over your data pipeline and infrastructure
- You already have orchestration tooling (Airflow, cron, CI/CD) in place
- You need to integrate CloudQuery into existing CI/CD workflows
- You prefer a code-first, config-as-code approach
- You have strict data residency or compliance requirements that demand full self-hosting
- You want to build custom integrations using the SDK
Choose Platform if…
- You want faster onboarding with minimal infrastructure setup
- You prefer a web UI for managing syncs, schedules, and configurations
- You want built-in features like asset inventory, SQL console, saved searches, alerts, policies, automations, reports, and an AI query assistant
- Your team is smaller or doesn’t have dedicated infrastructure resources
- You want managed scheduling, monitoring, and notifications without maintaining orchestration tooling
Get started with the Platform →
Can I use both?
Yes. Many teams use both the CLI and Platform together:
- Use Platform for day-to-day cloud visibility, asset inventory, and alerting
- Use CLI for custom data pipelines, CI/CD-integrated syncs, or advanced transformations
- Export Platform data to the same destinations the CLI supports, keeping everything in one place
The CLI and Platform share the same integration ecosystem, so your source and destination configurations translate between the two.
Next steps
- CLI Getting Started Guide — Install the CLI and complete your first sync
- Platform Getting Started Guide — Sign up and connect your first cloud account
- Core Concepts — Understand how integrations, syncs, and destinations work