diff --git a/public/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection/image-20260713-045912.png b/public/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection/image-20260713-045912.png
new file mode 100644
index 000000000..a7c7f54f0
Binary files /dev/null and b/public/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection/image-20260713-045912.png differ
diff --git a/public/overview/QueryPie_ACP.png b/public/overview/QueryPie_ACP.png
new file mode 100644
index 000000000..ead42776b
Binary files /dev/null and b/public/overview/QueryPie_ACP.png differ
diff --git a/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx b/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx
index 64ebcff25..c2bdd1e12 100644
--- a/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx
+++ b/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx
@@ -14,9 +14,8 @@ This feature allows you to upload custom JDBC drivers to register and use Custom
Previously, only the DB Vendors provided by QueryPie by default (MySQL, PostgreSQL, etc.) were available, but with this feature you can also connect to unsupported databases (e.g., Cubrid, Tibero, Altibase) by uploading their JDBC drivers directly.
-This feature is provided as **Beta**.
-To use it, you must set the **Custom JDBC Configuration** option to `Enable` in the Experimental section on the `Admin > Databases > General > Configurations` page.
-After activation, the `Admin > Databases > Connection Management > Custom JDBC Configs` menu will appear.
+This feature is available in version 11.6.x and later.
+(Provided as Beta from 11.6.0 through 11.6.4 and as a GA feature in 11.6.5)
### Registering a Custom JDBC Vendor
diff --git a/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx b/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx
index 9a88aeab5..e980ad5ce 100644
--- a/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx
+++ b/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx
@@ -12,9 +12,7 @@ import { Callout } from 'nextra/components'
Starting from QueryPie ACP 11.6.0, the Custom JDBC Configs feature allows administrators to register a JDBC Driver and create a Databricks connection with policies applied.
The query parser (QSI) supported by QueryPie ACP for Databricks is ANSI query, so Databricks-specific syntax may not work correctly.
-This feature is provided as **Beta**.
-To use it, you must set the **Custom JDBC Configuration** option to `Enable` in the Experimental section on the `Admin > Databases > General > Configurations` page.
-After activation, the `Admin > Databases > Connection Management > Custom JDBC Configs` menu will appear.
+This feature is available in version 11.6.x and later. (Provided as Beta from 11.6.0 through 11.6.4 and as a GA feature in 11.6.5)
### Registering Databricks as a Custom JDBC Vendor
@@ -32,7 +30,8 @@ After activation, the `Admin > Databases > Connection Management > Custom JDBC C
8. Enter `443` in the Default Port.
9. Enter `--add-opens=java.base/java.nio=ALL-UNNAMED` in the JVM Arguments.
10. Click the `Select JAR file to upload` button in the Driver JAR File section and upload the JDBC Driver.
Databricks: [JDBC Driver Download](https://www.databricks.com/spark/jdbc-drivers-download)
-11. Click the `Save` button to save the configuration.
+11. Dictionary
+12. Click the `Save` button to save the configuration.
### Creating a Databricks Connection with a Custom Vendor
diff --git a/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx b/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx
index b90824683..787f48001 100644
--- a/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx
+++ b/src/content/en/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx
@@ -9,36 +9,38 @@ import { Callout } from 'nextra/components'
### Overview
-**QSI Parser** is an option that can be selected when creating or editing a DB Connection with a Custom JDBC Vendor.
-QSI Parser refers to the parser that QueryPie uses to analyze SQL, and selecting a Parser that matches the syntax characteristics of the DB Vendor can improve query analysis and policy application compatibility.
-
-This feature is provided together with the **Custom JDBC Vendor** feature.
-To use it, you must first set the **Custom JDBC Configuration** option to `Enable` in the Experimental section on the `Admin > Databases > General > Configurations` page, and register the Custom JDBC Vendor you want to use at `Admin > Databases > Connection Management > Custom JDBC Configs`.
+This feature is available in version 11.6.x and later. (Provided as Beta from 11.6.0 through 11.6.4 and as a GA feature in 11.6.5)
-### Configuring the QSI Parser
+**QSI Parser** is an option that can be selected when creating or editing a DB Connection for a Custom JDBC Vendor or a database with selectable parsers.
+QSI Parser refers to the parser that QueryPie uses to analyze SQL, and selecting a Parser that matches the syntax characteristics of the DB Vendor can improve query analysis and policy application compatibility.
-Configure the QSI Parser for a DB Connection that uses a Custom JDBC Vendor.
+| **Database** | **Selectable Parsers** | Version where parser selection became available |
+| ------------------ | --------------------------------------- | ----------------------------------------------- |
+| Custom Jdbc Vendor | `ANSI`, `PostgreSQL`, `MySQL`, `Trino` | `11.6.1` and later |
+| Tibero | `ANSI`, `Trino` | `11.6.1` and later |
+| Presto | `ANSI`, `Trino` | `11.6.1` and later |
+| Teradata | `ANSI`, `PostgreSQL`, `Trino` | `11.6.1` and later |
+| Cubrid | `ANSI`, `MySQL` | `11.6.2` and later |
+| Snowflake | `ANSI`, `PostgreSQL`, `Trino` | `11.6.3` and later |
-
-
-
+### Configuring the QSI Parser
+
+Configure the QSI Parser for a DB Connection where parser selection is available.
1. Navigate to `Admin > Databases > Connection Management > DB Connections`.
2. Click the `Create Connection` button in the upper right corner, or select an existing connection to go to the edit screen.
-3. Scroll down and select the Custom JDBC Vendor you want to use from the **Custom JDBC Vendors** section.
+3. Scroll down and select the Custom JDBC Vendor you want to use from the **Custom JDBC Vendors** section. (Or select one of the previously mentioned Tibero, Presto, Teradata, Cubrid, or Snowflake entries.)
4. Enter the connection information in the `Connection Information` section.
-5. When the **QSI Parser** field appears, select the appropriate Parser for the Vendor.
- * For Custom JDBC Vendors, a list of compatible Parsers is provided in a dropdown.
+5. Select the **Use QSI Parser** checkbox.
+
+ 
+
+ * A list of compatible Parsers is provided in a dropdown.
* Examples: `ANSI SQL`, `Oracle`, `PostgreSQL`, `MySQL`, `Trino`
6. Enter the remaining connection information and click the `Next` button to proceed to the connection creation complete screen.
-
-As of the 11.6.0 admin UI, the **QSI Parser** field is only displayed when a Custom JDBC Vendor is selected.
-Additionally, the dropdown is only shown when there are two or more selectable Parsers for the Vendor.
-
-
### QSI Parser Selection Criteria
It is recommended to select the QSI Parser that most closely matches the SQL syntax of the target database.
@@ -59,7 +61,7 @@ Select a Parser from the same family as the SQL syntax verified when registering
You can change the QSI Parser of an existing DB Connection.
1. Select the connection you want to edit from `Admin > Databases > Connection Management > DB Connections`.
-2. Change the **QSI Parser** value in the `Connection Information` section.
+2. Change the **QSI Parser** value in the `Connection Information` section. (You can also clear the Use QSI Parser checkbox if needed. **If policies are configured, they may be invalidated, so review carefully before changing this setting.**)
3. Click the `Save Changes` button to save.
After changing the setting, query analysis results for the connection may differ, so verify the behavior with representative SQL queries if needed.
diff --git a/src/content/en/administrator-manual/databases/policies/query-rules.mdx b/src/content/en/administrator-manual/databases/policies/query-rules.mdx
index 655ceac87..da61c4d20 100644
--- a/src/content/en/administrator-manual/databases/policies/query-rules.mdx
+++ b/src/content/en/administrator-manual/databases/policies/query-rules.mdx
@@ -16,9 +16,8 @@ For example, you can exclude (SKIP) heartbeat queries periodically executed by C
When multiple rules are registered, they are evaluated in order of Priority, and the first matching rule is applied.
-This feature is provided as **Beta**.
-To use it, you must set the **Query Rules** option to `Enable` in the Experimental section on the `Admin > Databases > General > Configurations` page.
-After enabling, the `Admin > Databases > Policies > Query Rules` menu will appear.
+This feature is available in **version 11.6.x and later**.
+(Provided as `Beta` from 11.6.0 through 11.6.4 and as a `GA` feature in 11.6.5)
diff --git a/src/content/en/installation/product-versions.mdx b/src/content/en/installation/product-versions.mdx
index 165abfdd2..e746941a7 100644
--- a/src/content/en/installation/product-versions.mdx
+++ b/src/content/en/installation/product-versions.mdx
@@ -11,20 +11,20 @@ This page provides information about official releases of QueryPie ACP.
These are the official QueryPie ACP releases currently available for installation and operation.
-| **Version** | **Build Tag** | **Release Note** | **Release Date** | **Status** |
-| ----------- | ---------------- | ------------------------------------------------- | ---------------- | ---------------------------- |
-| 11.6.5 | `11.6.5-ba8dd33` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Jul 2, 2026 | Ready for Community Edition |
-| 11.6.4 | `11.6.4-9be1f67` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Jun 23, 2026 | Outdated |
-| 11.6.3 | `11.6.3-fc0a230` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | May 28, 2026 | Deprecated |
-| 11.6.2 | `11.6.2-151a452` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Apr 16, 2026 | Deprecated |
-| 11.6.1 | `11.6.1-44ad3a9` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Mar 20, 2026 | Deprecated |
-| 11.6.0 | `11.6.0-886d8e8` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Feb 13, 2026 | Deprecated |
-| 11.5.7 | `11.5.7-2db5ae7` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Jul 2, 2026 | Ready for Enterprise Edition |
-| 11.5.6 | `11.5.6-ec6acc4` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | May 28, 2026 | Deprecated |
-| 11.5.5 | `11.5.5-7c5b73d` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Apr 16, 2026 | Deprecated |
-| 11.5.4 | `11.5.4-702dd33` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Mar 20, 2026 | Deprecated |
-| 11.5.1 | `11.5.1-e0fc574` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Jan 23, 2026 | Deprecated |
-| 11.5.0 | `11.5.0-dce9f84` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Dec 16, 2025 | Deprecated |
+| **Version** | **Build Tag** | **Release Note** | **Release Date** | **Status** |
+| ----------- | ---------------- | ------------------------------------------------- | ---------------- | -------------------------------------------------- |
+| 11.6.5 | `11.6.5-ba8dd33` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Jul 2, 2026 | Ready for Community Edition and Enterprise Edition |
+| 11.6.4 | `11.6.4-9be1f67` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Jun 23, 2026 | Outdated |
+| 11.6.3 | `11.6.3-fc0a230` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | May 28, 2026 | Deprecated |
+| 11.6.2 | `11.6.2-151a452` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Apr 16, 2026 | Deprecated |
+| 11.6.1 | `11.6.1-44ad3a9` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Mar 20, 2026 | Deprecated |
+| 11.6.0 | `11.6.0-886d8e8` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | Feb 13, 2026 | Deprecated |
+| 11.5.7 | `11.5.7-2db5ae7` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Jul 2, 2026 | Ready for Enterprise Edition |
+| 11.5.6 | `11.5.6-ec6acc4` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | May 28, 2026 | Deprecated |
+| 11.5.5 | `11.5.5-7c5b73d` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Apr 16, 2026 | Deprecated |
+| 11.5.4 | `11.5.4-702dd33` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Mar 20, 2026 | Deprecated |
+| 11.5.1 | `11.5.1-e0fc574` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Jan 23, 2026 | Deprecated |
+| 11.5.0 | `11.5.0-dce9f84` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | Dec 16, 2025 | Deprecated |
#### Status
@@ -37,13 +37,13 @@ These are the official QueryPie ACP releases currently available for installatio
QueryPie ACP provides container images through the following container registries.
-#### Docker Hub (Recommended)
+#### Docker Hub
Registry location: `docker.io/querypie` ([https://hub.docker.com/u/querypie](https://hub.docker.com/u/querypie))
Example: `docker pull docker.io/querypie/querypie:11.6.4`
-* Available for Community / Standard / Enterprise Editions.
+* This container registry is provided for Community Edition and Standard Edition users.
* Recommended for new installations.
* No authentication required.
* Provides `linux/amd64`, `linux/arm64`, and multi-platform images.
@@ -52,7 +52,8 @@ Example: `docker pull docker.io/querypie/querypie:11.6.4`
Registry location: `harbor.chequer.io/querypie`
-This is a private container registry provided for compatibility with existing installation and operation environments. You must authenticate using the `docker login` command to download container images.
+This is a private container registry provided for Enterprise Edition users.
+All legacy versions used by customers are provided. You must authenticate using the `docker login` command to download container images.
Please contact your technical support partner to obtain the username and password for accessing this container registry.
#### Edition Compatibility
diff --git a/src/content/en/overview.mdx b/src/content/en/overview.mdx
index 87238f317..a5acaf497 100644
--- a/src/content/en/overview.mdx
+++ b/src/content/en/overview.mdx
@@ -14,14 +14,13 @@ It also offers user- and admin-friendly features that improve productivity.
Manage your dispersed assets and permissions in one place with QueryPie ACP.
-
+
How QueryPie Access Control Platform Works
-
### Using This Manual
QueryPie ACP continuously explores ways to securely protect sensitive data within enterprises, even in cloud environments.
diff --git a/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx b/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx
index 1c367b6d2..db8898344 100644
--- a/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx
+++ b/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx
@@ -14,9 +14,8 @@ import { Callout } from 'nextra/components'
従来はQueryPieがデフォルトで提供するDB Vendor（MySQL、PostgreSQLなど）のみ使用可能でしたが、この機能を通じてサポートされていないDB（例：Cubrid、Tibero、Altibaseなど）もJDBCドライバを直接アップロードして接続できます。
-本機能は**ベータ（Beta）**として提供されます。
-使用するには、`Admin > Databases > General > Configurations` ページのExperimentalセクションで **Custom JDBC Configuration** オプションを `Enable` に設定する必要があります。
-有効化後、`Admin > Databases > Connection Management > Custom JDBC Configs` メニューが表示されます。
+本機能は11.6.xバージョン以降で提供されます。
+（11.6.0〜11.6.4まではBeta、11.6.5で正式機能として提供）
### Custom JDBC Vendorを登録する
diff --git a/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx b/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx
index 16eaa6617..2343072da 100644
--- a/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx
+++ b/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx
@@ -12,9 +12,7 @@ import { Callout } from 'nextra/components'
QueryPie ACP 11.6.0から提供されるCustom JDBC Configs機能を通じて、管理者がJDBC Driverを登録し、Databricksコネクションを作成してポリシーを適用できます。
QueryPie ACPでDatabricksに対してサポートするquery parser（QSI）はANSI queryであるため、Databricks特化構文については正常に動作しない場合があります。
-本機能は**ベータ（Beta）**として提供されます。
-使用するには、`Admin > Databases > General > Configurations` ページのExperimentalセクションで **Custom JDBC Configuration** オプションを `Enable` に設定する必要があります。
-有効化後、`Admin > Databases > Connection Management > Custom JDBC Configs` メニューが表示されます。
+本機能は11.6.xバージョン以降で提供されます。（11.6.0〜11.6.4まではBeta、11.6.5で正式機能として提供）
### Custom JDBC VendorとしてDatabricksを登録する
@@ -32,7 +30,8 @@ QueryPie ACP 11.6.0から提供されるCustom JDBC Configs機能を通じて、
8. Default Portに `443` を入力します。
9. JVM Argumentsに `--add-opens=java.base/java.nio=ALL-UNNAMED` を入力します。
10. Driver JAR Fileセクションで `Select JAR file to upload` ボタンをクリックしてJDBC Driverをアップロードします。
Databricks：[JDBC Driverダウンロード](https://www.databricks.com/spark/jdbc-drivers-download)
-11. `Save` ボタンを押して設定を保存します。
+11. Dictionary
+12. `Save` ボタンを押して設定を保存します。
### Custom VendorでDatabricks Connectionを作成する
diff --git a/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx b/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx
index b2238d503..0aa099736 100644
--- a/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx
+++ b/src/content/ja/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx
@@ -9,36 +9,38 @@ import { Callout } from 'nextra/components'
### Overview
-**QSI Parser**は、Custom JDBC VendorでDB Connectionを作成または修正する際に選択できる項目です。
-QSI ParserはQueryPieがSQLを分析する際に使用するパーサーを意味し、DB Vendorの文法特性に合ったParserを選択するとクエリ分析およびポリシー適用の互換性を高めることができます。
-
-本機能は **Custom JDBC Vendor** 機能とともに提供されます。
-使用するには、まず `Admin > Databases > General > Configurations` ページのExperimentalセクションで **Custom JDBC Configuration** オプションを `Enable` に設定し、`Admin > Databases > Connection Management > Custom JDBC Configs` で使用するCustom JDBC Vendorを登録する必要があります。
+本機能は11.6.xバージョン以降で提供されます。（11.6.0〜11.6.4まではBeta、11.6.5で正式機能として提供）
-### QSI Parserを設定する
+**QSI Parser**は、Custom JDBC VendorまたはParserを選択可能なDatabaseのDB Connectionを作成または修正する際に選択できる項目です。
+QSI ParserはQueryPieがSQLを分析する際に使用するパーサーを意味し、DB Vendorの文法特性に合ったParserを選択するとクエリ分析およびポリシー適用の互換性を高めることができます。
-Custom JDBC Vendorを使用するDB ConnectionでQSI Parserを設定します。
+| **Database** | **選択可能なParser** | Parserを選択可能になったバージョン |
+| ------------------ | --------------------------------------- | ---------------------------------- |
+| Custom Jdbc Vendor | `ANSI`, `PostgreSQL`, `MySQL`, `Trino` | `11.6.1` 以降 |
+| Tibero | `ANSI`, `Trino` | `11.6.1` 以降 |
+| Presto | `ANSI`, `Trino` | `11.6.1` 以降 |
+| Teradata | `ANSI`, `PostgreSQL`, `Trino` | `11.6.1` 以降 |
+| Cubrid | `ANSI`, `MySQL` | `11.6.2` 以降 |
+| Snowflake | `ANSI`, `PostgreSQL`, `Trino` | `11.6.3` 以降 |
-
-
-
+### QSI Parserを設定する
+
+Parserを選択可能なDB ConnectionでQSI Parserを設定します。
1. `Admin > Databases > Connection Management > DB Connections` メニューに移動します。
2. 右上の `Create Connection` ボタンをクリックするか、既存のコネクションを選択して修正画面に移動します。
-3. 画面を下にスクロールし、**Custom JDBC Vendors** 項目で使用するCustom JDBC Vendorを選択します。
+3. 画面を下にスクロールし、**Custom JDBC Vendors** 項目で使用するCustom JDBC Vendorを選択します。（または前述のTibero、Presto、Teradata、Cubrid、Snowflake項目を選択します。）
4. `Connection Information` セクションで接続情報を入力します。
-5. **QSI Parser** 項目が表示されたら、該当Vendorに適したParserを選択します。
- * Custom JDBC Vendorでは互換可能なParser一覧がドロップダウンで提供されます。
+5. **Use QSI Parser** チェックボックスにチェックを入れます。
+
+
+
+ * 互換可能なParser一覧がドロップダウンで提供されます。
* 例：`ANSI SQL`、`Oracle`、`PostgreSQL`、`MySQL`、`Trino`
6. 残りの接続情報を入力した後、`Next` ボタンをクリックして `コネクション作成完了` 画面に移動します。
-
-11.6.0管理者UI基準で **QSI Parser** 項目はCustom JDBC Vendorを選択した場合にのみ表示されます。
-また、該当Vendorで選択可能なParserが2つ以上の場合にのみドロップダウンが表示されます。
-
-
### QSI Parser選択基準
QSI Parserは接続先DBのSQL文法と最も類似した項目を選択することをお勧めします。
@@ -59,7 +61,7 @@ Custom JDBC Vendorを登録する際に検証したSQL文法と同じ系列のPa
既存のDB ConnectionのQSI Parserを変更できます。
1. `Admin > Databases > Connection Management > DB Connections` メニューで修正するコネクションを選択します。
-2. `Connection Information` セクションで **QSI Parser** の値を変更します。
+2. `Connection Information` セクションで **QSI Parser** の値を変更します。（必要に応じてUse QSI Parserのチェックを外すこともできます。**ポリシーが設定されている場合は無効化される可能性があるため、慎重に確認してから設定することを推奨します。**）
3. `Save Changes` ボタンをクリックして保存します。
設定変更後は該当コネクションを使用するクエリ分析結果が変わる可能性があるため、必要に応じて代表的なSQLで動作を再確認してください。
diff --git a/src/content/ja/administrator-manual/databases/policies/query-rules.mdx b/src/content/ja/administrator-manual/databases/policies/query-rules.mdx
index c7de8fa71..fc0f20eea 100644
--- a/src/content/ja/administrator-manual/databases/policies/query-rules.mdx
+++ b/src/content/ja/administrator-manual/databases/policies/query-rules.mdx
@@ -16,9 +16,8 @@ Query Ruleは、QueryPieを経由するSQLクエリに対して許可、ブロ
複数のルールが登録されている場合、Priority（優先順位）の順序で評価され、最初にマッチしたルールが適用されます。
-本機能は**ベータ（Beta）**として提供されます。
-使用するには、`Admin > Databases > General > Configurations`ページのExperimentalセクションで**Query Rules**オプションを`Enable`に設定する必要があります。
-有効化すると`Admin > Databases > Policies > Query Rules`メニューが表示されます。
+本機能は**11.6.xバージョン以降**で提供されます。
+（11.6.0〜11.6.4までは `Beta`、11.6.5で `正式` 機能として提供）
diff --git a/src/content/ja/installation/product-versions.mdx b/src/content/ja/installation/product-versions.mdx
index a95f550dc..303489420 100644
--- a/src/content/ja/installation/product-versions.mdx
+++ b/src/content/ja/installation/product-versions.mdx
@@ -11,20 +11,20 @@ QueryPie ACPの公式リリースバージョン情報を提供します。
現在インストールおよび運用が可能なQueryPie ACP公式リリースバージョンです。
-| **Version** | **Build Tag** | **Release Note** | **Release Date** | **Status** |
-| ----------- | ---------------- | ------------------------------------------------- | ---------------- | ---------------------------- |
-| 11.6.5 | `11.6.5-ba8dd33` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 07. 02. | Ready for Community Edition |
-| 11.6.4 | `11.6.4-9be1f67` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 06. 23. | Outdated |
-| 11.6.3 | `11.6.3-fc0a230` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 05. 28. | Deprecated |
-| 11.6.2 | `11.6.2-151a452` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 04. 16. | Deprecated |
-| 11.6.1 | `11.6.1-44ad3a9` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 03. 20. | Deprecated |
-| 11.6.0 | `11.6.0-886d8e8` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 02. 13. | Deprecated |
-| 11.5.7 | `11.5.7-2db5ae7` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 07. 02. | Ready for Enterprise Edition |
-| 11.5.6 | `11.5.6-ec6acc4` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 05. 28. | Deprecated |
-| 11.5.5 | `11.5.5-7c5b73d` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 04. 16. | Deprecated |
-| 11.5.4 | `11.5.4-702dd33` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 03. 20. | Deprecated |
-| 11.5.1 | `11.5.1-e0fc574` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 01. 23. | Deprecated |
-| 11.5.0 | `11.5.0-dce9f84` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2025. 12. 16. | Deprecated |
+| **Version** | **Build Tag** | **Release Note** | **Release Date** | **Status** |
+| ----------- | ---------------- | ------------------------------------------------- | ---------------- | -------------------------------------------------- |
+| 11.6.5 | `11.6.5-ba8dd33` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 07. 02. | Ready for Community Edition and Enterprise Edition |
+| 11.6.4 | `11.6.4-9be1f67` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 06. 23. | Outdated |
+| 11.6.3 | `11.6.3-fc0a230` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 05. 28. | Deprecated |
+| 11.6.2 | `11.6.2-151a452` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 04. 16. | Deprecated |
+| 11.6.1 | `11.6.1-44ad3a9` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 03. 20. | Deprecated |
+| 11.6.0 | `11.6.0-886d8e8` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 02. 13. | Deprecated |
+| 11.5.7 | `11.5.7-2db5ae7` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 07. 02. | Ready for Enterprise Edition |
+| 11.5.6 | `11.5.6-ec6acc4` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 05. 28. | Deprecated |
+| 11.5.5 | `11.5.5-7c5b73d` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 04. 16. | Deprecated |
+| 11.5.4 | `11.5.4-702dd33` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 03. 20. | Deprecated |
+| 11.5.1 | `11.5.1-e0fc574` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 01. 23. | Deprecated |
+| 11.5.0 | `11.5.0-dce9f84` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2025. 12. 16. | Deprecated |
#### Status
@@ -37,13 +37,13 @@ QueryPie ACPの公式リリースバージョン情報を提供します。
QueryPie ACPは以下のコンテナレジストリを通じてコンテナイメージを提供します。
-#### Docker Hub (推奨)
+#### Docker Hub
レジストリの場所: `docker.io/querypie` ([https://hub.docker.com/u/querypie](https://hub.docker.com/u/querypie))
例: `docker pull docker.io/querypie/querypie:11.6.4`
-* Community / Standard / Enterprise Editionすべてで利用可能です。
+* Community Edition、Standard Edition利用者向けに提供されるコンテナレジストリです。
* 新規インストール環境に推奨します。
* 認証なしで使用できます。
* `linux/amd64`、`linux/arm64`、マルチプラットフォームイメージを提供します。
@@ -52,7 +52,8 @@ QueryPie ACPは以下のコンテナレジストリを通じてコンテナイ
レジストリの場所: `harbor.chequer.io/querypie`
-既存のインストールおよび運用環境との互換性を目的として提供される非公開コンテナレジストリです。`docker login`コマンドで認証を行う必要があります。
+Enterprise Edition利用者向けに提供される非公開コンテナレジストリです。
+お客様が使用中の過去バージョンがすべて提供されます。`docker login`コマンドで認証を行う必要があります。
技術サポートを担当するパートナーを通じて、コンテナレジストリにアクセスするためのユーザー名とパスワードを取得してください。
#### エディションの互換性
diff --git a/src/content/ja/overview.mdx b/src/content/ja/overview.mdx
index 3ae69066e..34da12602 100644
--- a/src/content/ja/overview.mdx
+++ b/src/content/ja/overview.mdx
@@ -14,14 +14,13 @@ QueryPie ACPはセキュリティ作業自動化、多様なプラットフォ
複雑に散らばっている資産と権限をQueryPie ACPを通じて一箇所で管理してみてください。
-
+
How QueryPie Access Control Platform Works
-
### マニュアル使用
QueryPie ACPはクラウド環境でも企業内の機密データを安全に保護できる方向性について絶えず検討しています。
diff --git a/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx b/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx
index 69452b43e..bd4065bce 100644
--- a/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx
+++ b/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs.mdx
@@ -14,9 +14,8 @@ import { Callout } from 'nextra/components'
기존에는 QueryPie가 기본 제공하는 DB Vendor(MySQL, PostgreSQL 등)만 사용 가능했지만, 이 기능을 통해 지원하지 않는 DB(예: Cubrid, Tibero, Altibase 등)도 JDBC 드라이버를 직접 업로드하여 연결할 수 있습니다.
-본 기능은 **베타(Beta)** 로 제공됩니다.
-사용하려면 `Admin > Databases > General > Configurations` 페이지의 Experimental 섹션에서 **Custom JDBC Configuration** 옵션을 `Enable`로 설정해야 합니다.
-활성화 후 `Admin > Databases > Connection Management > Custom JDBC Configs` 메뉴가 나타납니다.
+본 기능은 11.6.x 버전 이상에서 제공됩니다.
+( 11.6.0 ~ 11.6.4까지 Beta, 11.6.5에서 정식 기능으로 제공)
### Custom JDBC Vendor 등록하기
diff --git a/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx b/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx
index a37d4f81e..c31ec4e85 100644
--- a/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx
+++ b/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs/custom-jdbc-configs-databricks-example.mdx
@@ -12,9 +12,7 @@ import { Callout } from 'nextra/components'
QueryPie ACP 11.6.0 부터 제공되는 Custom JDBC Configs 기능을 통해 관리자가 JDBC Driver를 등록하고 Databricks 커넥션을 생성 후 정책을 적용할 수 있습니다.
QueryPie ACP에서 Databricks에 대해 지원하는 query parser (QSI)는 ANSI query 이므로 Databricks 특화 구문에 대해서는 정상 작동하지 않을 수 있습니다.
-본 기능은 **베타(Beta)** 로 제공됩니다.
-사용하려면 `Admin > Databases > General > Configurations` 페이지의 Experimental 섹션에서 **Custom JDBC Configuration** 옵션을 `Enable`로 설정해야 합니다.
-활성화 후 `Admin > Databases > Connection Management > Custom JDBC Configs` 메뉴가 나타납니다.
+본 기능은 11.6.x 버전 이상에서 제공됩니다.( 11.6.0 ~ 11.6.4까지 Beta, 11.6.5에서 정식 기능으로 제공)
### Custom JDBC Vendor 로 Databricks 등록하기
@@ -32,7 +30,8 @@ QueryPie ACP 11.6.0 부터 제공되는 Custom JDBC Configs 기능을 통해 관
8. Default Port에 `443` 을 입력합니다.
9. JVM Arguments에 `--add-opens=java.base/java.nio=ALL-UNNAMED` 를 입력합니다.
10. Driver JAR File 섹션에서 `Select JAR file to upload` 버튼을 클릭하고 JDBC Driver 를 업로드합니다.
Databricks : [JDBC Driver 다운로드](https://www.databricks.com/spark/jdbc-drivers-download)
-11. `Save` 버튼을 누르고 설정을 저장합니다.
+11. Dictionary
+12. `Save` 버튼을 누르고 설정을 저장합니다.
### Custom Vendor로 Databricks Connection 생성하기
diff --git a/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx b/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx
index 4b08a1831..52fab811d 100644
--- a/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx
+++ b/src/content/ko/administrator-manual/databases/connection-management/custom-jdbc-configs/qsi-parser-selection.mdx
@@ -9,36 +9,38 @@ import { Callout } from 'nextra/components'
### Overview
-**QSI Parser**는 Custom JDBC Vendor로 DB Connection을 생성하거나 수정할 때 선택할 수 있는 항목입니다.
-QSI Parser는 QueryPie가 SQL을 분석할 때 사용하는 파서를 의미하며, DB Vendor의 문법 특성에 맞는 Parser를 선택하면 쿼리 분석 및 정책 적용 호환성을 높일 수 있습니다.
-
-본 기능은 **Custom JDBC Vendor** 기능과 함께 제공됩니다.
-사용하려면 먼저 `Admin > Databases > General > Configurations` 페이지의 Experimental 섹션에서 **Custom JDBC Configuration** 옵션을 `Enable`로 설정하고, `Admin > Databases > Connection Management > Custom JDBC Configs`에서 사용할 Custom JDBC Vendor를 등록해야 합니다.
+본 기능은 11.6.x 버전 이상에서 제공됩니다.( 11.6.0 ~ 11.6.4까지 Beta, 11.6.5에서 정식 기능으로 제공)
-### QSI Parser 설정하기
+**QSI Parser**는 Custom JDBC Vendor 또는 파서가 선택가능한 Database의 DB Connection을 생성하거나 수정할 때 선택할 수 있는 항목입니다.
+QSI Parser는 QueryPie가 SQL을 분석할 때 사용하는 파서를 의미하며, DB Vendor의 문법 특성에 맞는 Parser를 선택하면 쿼리 분석 및 정책 적용 호환성을 높일 수 있습니다.
-Custom JDBC Vendor를 사용하는 DB Connection에서 QSI Parser를 설정합니다.
+| **Database** | **선택 가능한 파서** | Parser 선택 가능해진 버전 |
+| ------------------ | -------------------------------------- | ------------------------- |
+| Custom Jdbc Vendor | `ANSI`, `PostgreSQL`, `MySQL`, `Trino` | `11.6.1` 이상 |
+| Tibero | `ANSI`, `Trino` | `11.6.1` 이상 |
+| Presto | `ANSI`, `Trino` | `11.6.1` 이상 |
+| Teradata | `ANSI`, `PostgreSQL`, `Trino` | `11.6.1` 이상 |
+| Cubrid | `ANSI`, `MySQL` | `11.6.2` 이상 |
+| Snowflake | `ANSI`, `PostgreSQL`, `Trino` | `11.6.3` 이상 |
-
-
-
+### QSI Parser 설정하기
+
+Parser 선택이 가능한 DB Connection에서 QSI Parser를 설정합니다.
1. `Admin > Databases > Connection Management > DB Connections` 메뉴로 이동합니다.
2. 우측 상단의 `Create Connection` 버튼을 클릭하거나, 기존 커넥션을 선택하여 수정 화면으로 이동합니다.
-3. 화면을 아래로 스크롤한 뒤 **Custom JDBC Vendors** 항목에서 사용할 Custom JDBC Vendor를 선택합니다.
+3. 화면을 아래로 스크롤한 뒤 **Custom JDBC Vendors** 항목에서 사용할 Custom JDBC Vendor를 선택합니다. (또는 앞에서 언급된 Tibero, Presto, Teradata, Cubrid, Snowflake 항목을 선택합니다.)
4. `Connection Information` 섹션에서 연결 정보를 입력합니다.
-5. **QSI Parser** 항목이 표시되면, 해당 Vendor에 적합한 Parser를 선택합니다.
- * Custom JDBC Vendor에서는 호환 가능한 Parser 목록이 드롭다운으로 제공됩니다.
+5. **USe QSI Parser** 체크 박스에 체크합니다.
+
+
+
+ * 호환 가능한 Parser 목록이 드롭다운으로 제공됩니다.
* 예: `ANSI SQL`, `Oracle`, `PostgreSQL`, `MySQL`, `Trino`
6. 나머지 연결 정보를 입력한 뒤 `Next` 버튼을 클릭하여 `커넥션 생성 완료` 화면으로 이동합니다.
-
-11.6.0 관리자 UI 기준으로 **QSI Parser** 항목은 Custom JDBC Vendor를 선택한 경우에만 표시됩니다.
-또한 해당 Vendor에서 선택 가능한 Parser가 두 개 이상일 때만 드롭다운이 노출됩니다.
-
-
### QSI Parser 선택 기준
QSI Parser는 연결 대상 DB의 SQL 문법과 가장 유사한 항목을 선택하는 것이 좋습니다.
@@ -59,7 +61,7 @@ Custom JDBC Vendor를 등록할 때 검증한 SQL 문법과 동일한 계열의
기존 DB Connection의 QSI Parser를 변경할 수 있습니다.
1. `Admin > Databases > Connection Management > DB Connections` 메뉴에서 수정할 커넥션을 선택합니다.
-2. `Connection Information` 섹션에서 **QSI Parser** 값을 변경합니다.
+2. `Connection Information` 섹션에서 **QSI Parser** 값을 변경합니다. (필요에 따라 Use QSI Parser의 체크를 해제 할 수도 있습니다. **정책이 설정되어 있는 경우 무효화 될 수 있으므로 신중히 검토 후 설정 권장 드립니다.**)
3. `Save Changes` 버튼을 클릭하여 저장합니다.
설정 변경 후에는 해당 커넥션을 사용하는 쿼리 분석 결과가 달라질 수 있으므로, 필요한 경우 대표 SQL로 동작을 다시 확인하세요.
diff --git a/src/content/ko/administrator-manual/databases/policies/query-rules.mdx b/src/content/ko/administrator-manual/databases/policies/query-rules.mdx
index b91b7ebcf..ee214d3fd 100644
--- a/src/content/ko/administrator-manual/databases/policies/query-rules.mdx
+++ b/src/content/ko/administrator-manual/databases/policies/query-rules.mdx
@@ -16,9 +16,8 @@ Query Rule은 QueryPie를 경유하는 SQL 쿼리에 대해 허용, 차단, 감
여러 규칙이 등록된 경우 Priority(우선순위) 순서로 평가되며, 가장 먼저 매칭되는 규칙이 적용됩니다.
-본 기능은 **베타(Beta)** 로 제공됩니다.
-사용하려면 `Admin > Databases > General > Configurations` 페이지의 Experimental 섹션에서 **Query Rules** 옵션을 `Enable`로 설정해야 합니다.
-활성화 후 `Admin > Databases > Policies > Query Rules` 메뉴가 나타납니다.
+본 기능은 **11.6.x 버전 이상**에서 제공됩니다.
+( 11.6.0 ~ 11.6.4까지 `Beta`, 11.6.5에서 `정식` 기능으로 제공)
diff --git a/src/content/ko/installation/product-versions.mdx b/src/content/ko/installation/product-versions.mdx
index c7176ba3a..3a079819f 100644
--- a/src/content/ko/installation/product-versions.mdx
+++ b/src/content/ko/installation/product-versions.mdx
@@ -11,20 +11,20 @@ QueryPie ACP의 공식 출시 버전 정보를 제공합니다.
현재 설치 및 운영이 가능한 QueryPie ACP 공식 출시 버전입니다.
-| **Version** | **Build Tag** | **Release Note** | **Release Date** | **Status** |
-| ----------- | ---------------- | -------------------------------------------------- | ---------------- | ---------------------------- |
-| 11.6.5 | `11.6.5-ba8dd33` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 07. 02. | Ready for Community Edition |
-| 11.6.4 | `11.6.4-9be1f67` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 06. 23. | Outdated |
-| 11.6.3 | `11.6.3-fc0a230` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 05. 28. | Deprecated |
-| 11.6.2 | `11.6.2-151a452` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 04. 16. | Deprecated |
-| 11.6.1 | `11.6.1-44ad3a9` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 03. 20. | Deprecated |
-| 11.6.0 | `11.6.0-886d8e8` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 02. 13. | Deprecated |
-| 11.5.7 | `11.5.7-2db5ae7` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 07. 02. | Ready for Enterprise Edition |
-| 11.5.6 | `11.5.6-ec6acc4` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 05. 28. | Deprecated |
-| 11.5.5 | `11.5.5-7c5b73d` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 04. 16. | Deprecated |
-| 11.5.4 | `11.5.4-702dd33` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 03. 20. | Deprecated |
-| 11.5.1 | `11.5.1-e0fc574` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 01. 23. | Deprecated |
-| 11.5.0 | `11.5.0-dce9f84` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2025. 12. 16. | Deprecated |
+| **Version** | **Build Tag** | **Release Note** | **Release Date** | **Status** |
+| ----------- | ---------------- | -------------------------------------------------- | ---------------- | -------------------------------------------------- |
+| 11.6.5 | `11.6.5-ba8dd33` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 07. 02. | Ready for Community Edition and Enterprise Edition |
+| 11.6.4 | `11.6.4-9be1f67` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 06. 23. | Outdated |
+| 11.6.3 | `11.6.3-fc0a230` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 05. 28. | Deprecated |
+| 11.6.2 | `11.6.2-151a452` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 04. 16. | Deprecated |
+| 11.6.1 | `11.6.1-44ad3a9` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 03. 20. | Deprecated |
+| 11.6.0 | `11.6.0-886d8e8` | [11.6.0 ~ 11.6.5](../release-notes/11.6.0-11.6.5) | 2026. 02. 13. | Deprecated |
+| 11.5.7 | `11.5.7-2db5ae7` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 07. 02. | Ready for Enterprise Edition |
+| 11.5.6 | `11.5.6-ec6acc4` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 05. 28. | Deprecated |
+| 11.5.5 | `11.5.5-7c5b73d` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 04. 16. | Deprecated |
+| 11.5.4 | `11.5.4-702dd33` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 03. 20. | Deprecated |
+| 11.5.1 | `11.5.1-e0fc574` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2026. 01. 23. | Deprecated |
+| 11.5.0 | `11.5.0-dce9f84` | [11.5.0 ~ 11.5.7](../release-notes/11.5.0-11.5.7) | 2025. 12. 16. | Deprecated |
#### Status
@@ -37,13 +37,13 @@ QueryPie ACP의 공식 출시 버전 정보를 제공합니다.
QueryPie ACP는 다음 Container Registry를 통해 Container Image를 제공합니다.
-#### Docker Hub (Recommended)
+#### Docker Hub
Registry 위치: `docker.io/querypie` ([https://hub.docker.com/u/querypie](https://hub.docker.com/u/querypie))
예시: `docker pull docker.io/querypie/querypie:11.6.4`
-* Community / Standard / Enterprise Edition 모두 사용 가능합니다.
+* Community Edition, Standard Edition 이용자에게 제공되는 Container Registry 입니다.
* 신규 설치 환경에 권장합니다.
* 인증 없이 사용할 수 있습니다.
* `linux/amd64`, `linux/arm64`, 멀티 플랫폼 이미지를 제공합니다.
@@ -52,7 +52,8 @@ Registry 위치: `docker.io/querypie` ([https://hub.docker.com/u/querypie](https
Registry 위치: `harbor.chequer.io/querypie`
-기존 설치 및 운영 환경과의 호환성을 목적으로 제공되는 비공개 Container Registry입니다. `docker login` 명령으로 인증을 수행해야 Container Image를 내려받을 수 있습니다.
+Enterprise Edition 이용자에게 제공되는 비공개 Container Registry 입니다.
+고객사에서 사용 중인 과거 버전이 모두 제공됩니다. `docker login` 명령으로 인증을 수행해야 Container Image를 내려받을 수 있습니다.
기술지원을 담당하는 파트너를 통해, Container Registry 에 접근하기 위한 Username, Password 를 제공 받아야 합니다.
#### Edition Compatibility
diff --git a/src/content/ko/overview.mdx b/src/content/ko/overview.mdx
index 52a588aad..8bc163b50 100644
--- a/src/content/ko/overview.mdx
+++ b/src/content/ko/overview.mdx
@@ -14,14 +14,13 @@ QueryPie ACP는 보안 작업 자동화, 다양한 플랫폼과의 손쉬운 연
복잡하게 흩어져 있는 자산과 권한을 QueryPie ACP를 통해 한 곳에서 관리해 보세요.
-
+
How QueryPie Access Control Platform Works
-
### 매뉴얼 사용하기
QueryPie ACP(Access Control Platform)는 클라우드 환경에서도 기업 내 민감한 데이터들을 안전하게 보호할 수 있는 방향성에 대해 끊임없이 고민합니다.