Choosing the Right Gudu Product

Three products, one parse engine. Use the interactive guide below, compare features side-by-side, or jump to use case examples.

Interactive Decision Guide

Step 1 of 3

What do you want to do?

Step 2 of 3

How will you integrate?

Step 2 of 3

What matters most for your team?

Step 2 of 3

What is your primary concern?

Step 3 of 3

How large is your team?

Recommended

General SQL Parser (GSP)

GSP is the right choice when you need to embed lineage analysis directly in your own application. It gives you full control over the parse tree, supports batch processing, and runs entirely in-process with zero network overhead.

Get started with GSP →
Recommended

SQLFlow

SQLFlow is a full lineage platform with a web UI, REST API, database connectors, role-based access, and scheduled jobs. It is designed for data governance teams that need a shared, enterprise-grade lineage solution.

Get started with SQLFlow →
Recommended

SQLFlow REST API

Use SQLFlow's REST API to call the lineage engine from any programming language. You get the same parsing power as GSP without needing Java. Deploy SQLFlow on-premise and call it over HTTP.

Explore SQLFlow API →
Recommended

Gudu SQL Omni

SQL Omni runs 100% offline inside VS Code. Your SQL never leaves your machine. Instant column-level lineage, impact analysis, and ER diagrams — right where you write code.

Install SQL Omni →
Recommended

Gudu SQL Omni (for each engineer)

For small teams, each engineer can install SQL Omni independently. Everyone gets private, offline lineage analysis. No shared server needed. Export lineage as JSON or PNG to share findings.

Install SQL Omni →
Recommended

SQLFlow (Team Platform)

For larger teams, SQLFlow provides a shared lineage platform with role-based access, scheduled scans, and a web UI that non-technical stakeholders can use. Consider pairing with SQL Omni for individual engineers.

Get started with SQLFlow →

Detailed Feature Comparison

Feature GSP SQLFlow SQL Omni
Lineage Analysis
Column-level lineage
Table-level lineage
Schema-level lineage
Impact analysis
Stored procedure lineage
CTE / subquery / UNION handling
Dynamic SQL tracing
SQL Dialect Support
Number of dialects 20+ 20+ 34
Auto-detect dialect
dbt model support
Interface & Integration
Java API
CLI Tool
REST API
Interactive graph UI
VS Code integration
ER diagrams
Export to JSON
Export to PNG / SVG
Deployment & Operations
Runs fully offline On-prem option
Air-gapped deployment
Database metadata import
Scheduled lineage jobs
Multi-user / RBAC
Workspace / project scanning
Licensing & Pricing
Free tier Cloud demo ✓ (10 tables)
Starting price Contact sales Contact sales $10/month
OEM licensing

Use Case Examples

GSP — Library / SDK

Data Governance Platform

"We are building a data catalog product and need to extract column-level lineage from customer SQL automatically."
How GSP helps: Embed the GSP JAR in your Java application. Call the lineage API on each SQL statement, get structured lineage output, and store it in your catalog's graph database. Process millions of queries in batch with no network overhead.
GSP — Library / SDK

SQL Migration Validator

"We are migrating from Oracle to Snowflake and need to verify that transformed SQL preserves the same data flow."
How GSP helps: Parse the original Oracle SQL and the target Snowflake SQL with GSP. Compare the lineage graphs programmatically to confirm column mappings are preserved after translation.
SQLFlow — Platform

Enterprise Data Governance

"Our compliance team needs to trace how PII flows through 500+ stored procedures across three database systems."
How SQLFlow helps: Connect SQLFlow to your Oracle, SQL Server, and PostgreSQL instances. It imports metadata automatically, builds a unified lineage graph, and lets compliance officers search for sensitive columns in the web UI.
SQLFlow — Platform

CI/CD Lineage Gate

"Before any SQL migration ships, we want to validate that no critical downstream reports break."
How SQLFlow helps: Call the SQLFlow REST API from your CI pipeline. Submit the changed SQL, get the impact analysis result, and fail the build if protected columns are affected.
SQL Omni — VS Code

Daily Development Workflow

"I am refactoring a complex reporting query and need to understand which output columns depend on which source tables."
How SQL Omni helps: Open the SQL file in VS Code, press Ctrl+Alt+L, and get an interactive lineage graph instantly. Click any column to trace its upstream sources. No setup, no accounts, no data uploaded anywhere.
SQL Omni — VS Code

Regulated Environment

"Our security policy prohibits sending SQL to external services, but engineers still need lineage analysis."
How SQL Omni helps: SQL Omni runs entirely on the developer's machine. The bundled parser processes everything locally. No internet connection required after installation. Meets air-gapped and FedRAMP-adjacent requirements.

Get Started

GSP Quickstart

  1. Download the GSP SDK (Java)
  2. Add the JAR/DLL to your project
  3. Call TGetStatementColumn to extract lineage
  4. Process the lineage result in your application
www.sqlparser.com →

SQLFlow Quickstart

  1. Try the online demo at gudusoft.com
  2. Request an on-premise evaluation license
  3. Deploy via Docker or installer
  4. Import database metadata and explore lineage
www.gudusoft.com →

SQL Omni Quickstart

  1. Open VS Code Extensions (Ctrl+Shift+X)
  2. Search "Gudu SQL Omni" and install
  3. Open any .sql file
  4. Press Ctrl+Alt+L for instant lineage
Full getting started guide →