Skip to main content
PawSQL can run as a public cloud service or inside your organization’s environment. Its SQL quality check and optimization capabilities are available through the web console, IDE extensions, APIs, webhooks, and MCP. Choosing the right setup involves two separate decisions: where PawSQL runs and how it fits into your workflow.
Want the fastest path to a working result? Start with PawSQL Cloud and the web console, then follow Optimize Your First SQL Query.

​
Choose a path

Deployment and access are independent choices. For example, an IDE extension may connect to either a cloud service or a privately deployed PawSQL service, depending on the edition and configuration available to your organization.

​
Step 1: Choose where PawSQL runs

The deployment model determines where the service operates, which network boundary the analysis data crosses, and who is responsible for operating the system.

PawSQL Cloud

Best for evaluation, individual use, and teams that want to avoid installing and maintaining the service. Once access is enabled, users can connect through supported clients.

Private deployment

Best for organizations with specific requirements for data boundaries, network isolation, access control, or internal platform integration. PawSQL runs on infrastructure designated by the organization.

​
Deployment comparison

If your policies prohibit SQL, DDL, database metadata, or execution plans from being sent to a public service, choose a private deployment and complete the required security and permission reviews before connecting a database.

​
Choose PawSQL Cloud when

  • You want to evaluate SQL quality check, automatic rewriting, and index recommendations immediately.
  • You do not want to provision servers or operate the PawSQL service.
  • You primarily analyze development, test, or sanitized SQL.
  • Your organization permits the use of a public service for this workload.

​
Choose a private deployment when

  • SQL, DDL, statistics, or database connections must remain within your network.
  • PawSQL needs to connect to production or pre-production databases.
  • You need centralized identity, approval workflows, CI/CD, or internal platform integration.
  • Multiple teams, database instances, and review policies must be managed centrally.
Before installation, confirm the required compute resources, operating system, network access, database connectivity, identity configuration, and product license. Requirements may vary by the delivered edition.

​
Step 2: Choose how users connect

After selecting a deployment model, choose the entry points that match where SQL is created and who needs to work with the results. A team can use several entry points together.
Best for: developers, testers, DBAs, and SQL reviewers.Use it to: create workspaces, submit individual or batch SQL, inspect findings, compare rewrites, evaluate index recommendations, and review validation evidence.The web console is usually the clearest entry point for a first PawSQL session.

​
Common combinations

​
Developer self-service optimization

Developers analyze SQL from an IDE extension and open the web console when they need more context or detailed validation evidence. Recommended combination: Cloud or private deployment + IDE extension + web console.

​
SQL quality gates in CI/CD

A pipeline sends changed SQL through an API or webhook. Findings can trigger a notification, request manual approval, or block a release according to policy. Recommended combination: Cloud or private deployment + API/webhook + web console.

​
Production slow-SQL governance

Performance patrol discovers slow queries, while DBAs use the web console to assess findings, rewrites, index candidates, and validation evidence. Recommended combination: Private deployment + performance patrol + web console.

​
Before you start

Confirm the following for any setup:
  • Database compatibility: The database type, version, and required PawSQL capabilities are supported.
  • Data boundaries: Your policies permit the selected handling of SQL, DDL, statistics, and execution plans.
  • Network connectivity: PawSQL, databases, IDEs, and pipelines can reach the required endpoints.
  • Identity and permissions: User roles, read-only database accounts, API credentials, and organization permissions are ready.
  • Scope: You know whether the target is individual optimization, team review, a release gate, or production patrol.
  • Validation process: Rewritten SQL and index changes have a path through test validation and controlled release.
See Supported Databases for database, version, and capability coverage.

​
Next steps

Optimize your first query

Create a workspace in the web console and submit your first SQL statement.

Install and connect

Configure cloud access, private deployment, IDE extensions, APIs, and MCP.

Check database support

Confirm compatibility for your database, version, and required capabilities.

Explore use cases

Plan a workflow for development, CI/CD, DBA operations, or enterprise governance.