Please check the following page for the old SQLFlow installation:
If you have SQLFlow 5.x installed on your server and would like to upgrade to SQLFlow 6.x, please refer to this page:


  • A linux server with at least 8GB memory (ubuntu 20.04 is recommended).
  • Java 8
  • Port needs to be opened. (The default port is 8165 but you can customized this port)

Setup Environment (Ubuntu for example)

sudo apt-get update
sudo apt-get install default-jre -y

Upload Files

create a directory :
# it must be created start with root path
sudo mkdir -p /wings/sqlflow
upload your zip file including backend and frontend file to sqlflow folder, and unzip like this :
You should get files organized like this:
└── sqlflow
├── backend
│   ├── bin
│   │   ├── backend.bat
│   │   ├──
│   │   ├── eureka.bat
│   │   ├──
│   │   ├── eureka.vbs
│   │   ├── gspLive.bat
│   │   ├──
│   │   ├── gspLive.vbs
│   │   ├──
│   │   ├── monitor.bat
│   │   ├──
│   │   ├── sqlservice.bat
│   │   ├──
│   │   ├── sqlservice.vbs
│   │   ├── stop.bat
│   │   ├──
│   │   ├── taskscheduler.bat
│   │   ├──
│   │   └── taskscheduler.vbs
│   ├── conf
│   │   └── gudu_sqlflow.conf
│   └── lib
│   ├── eureka.jar
│   ├── gspLive.jar
│   ├── sqlservice.jar
│   └── taskscheduler.jar
set folder permissions :
sudo chmod -R 755 /wings/sqlflow

Customize the port

If you don't want to change the default service port you can just ignore this section. Otherwise this section will show you how to customize the port.

1. Default port

  1. 1.
    Web port is 8165
  2. 2.
    SQLFlow backend service port:

2. Change the default port in

You can change the web or backend api port from 8165 to any available port.
Add the following section in gspLive.bat in Windows):

Start Backend Services

start service in background:
sudo /wings/sqlflow/backend/bin/
You can assign the RAM to SQLFlow by specifying the boot parameter when starting the service. /m <RAM_VALUE>
The RAM_VALUE could be: 4g 8g 16g 32g or 64g.
SQLFlow will automatically allocate the memory based on the status of the installed server if this parameter is not given. SQLFlow would allocate less than 31 GB memory if that is the case. However, if your total memory is less than 32 GB, SQLFlow would allocate all the remaining memory on your server.
please allow 3-5 minutes to start the service.
use ps -ef|grep java to check those 3 processing are running.
ubuntu 11047 1 0 Nov02 ? 00:04:44 java -server -jar eureka.jar
ubuntu 11076 1 0 Nov02 ? 00:04:11 java -server -Xmn512m -Xms2g -Xmx2g -Djavax.accessibility.assistive_technologies= -jar sqlservice.jar
ubuntu 11114 1 0 Nov02 ? 00:05:17 java -server -jar gspLive.jar

Open SQLFlow

open to see the SQLFlow.
open or http://localhost:8165/api/gspLive_backend/doc.html?lang=en to see the Restful API document.
To login, please check the following default user credentials:

Gudu SQLFlow License file

If this is the first time you setup the Gudu SQLFlow on a new machine, then, you will see this license UI:
  1. 1.
    You send us the Gudu SQLFlow Id (6 characters in red).
  2. 2.
    We will generate a license file for you based on this id.
  3. 3.
    You upload the license file by click the "upload license file" link.

Backend Services Configuration

sqlflow provides several options to control the service analysis logic. Open the sqlservice configuration file(conf/gudu_sqlflow.conf)
  • user_token_expire_hours: default value is 24. User can customize the TTL of the token by setting this field. In case user_token_expire_hours less than or equals to 0, the user token would never expire.
  • ignore_user_token: default value is false, token auth is skipped in case the value is set to true.
  • relation_limit: default value is 1000. When the count of selected object relations is greater than relation_limit, sqlflow will fallback to the simple mode, ignore all the record sets. If the relations of simple mode are still greater than relation_limit, sqlflow will only show the summary information.
  • big_sql_size: default value is 4096. If the sql length is greater than big_sql_size, sqlflow submit the sql in the work queue and execute it. If the work queue is full, sqlflow throws an exception and returns error message "Sorry, the service is busy. Please try again later."

SQLFlow client api call

  • Get userId from the account profile page and generate the secrete key
  • Generate token by invoking the token generate API
generate token
curl --location --request POST 'http://localhost:8165/api/gspLive_backend/user/generateToken?userId=%3CUSER_ID%3E&secretKey=%3CSECRET_KEY%3E' \
--header 'Accept: application/json;charset=utf-8'
  • Test webapi by curl
    • test sql:
    select name from user
    • curl command:
    curl --location 'http://localhost:8165/api/gspLive_backend/sqlflow/generation/sqlflow' \
    --header 'accept: application/json;charset=utf-8' \
    --form 'userId="<USER ID>"' \
    --form 'dbvendor="dbvoracle"' \
    --form 'sqltext="select name from user"' \
    --form 'token="<TOKEN>"'
    • response:
    "code": 200,
    "data": {
    "dbvendor": "dbvoracle",
    "dbobjs": [
    "relations": [
    "sessionId": ...
    • If the code returns 401, please check the userId is set or the userId is valid.

Enable Regular Job

If you need to enable regular job feature on your sqlflow on-premiser, you will also need to install Clickhouse on your server. Check here for Clickhouse installation: