# Inquiry Regarding Supported Databases for the Read-Only API

**URL:** <https://community.sonatype.com/t/inquiry-regarding-supported-databases-for-the-read-only-api/15988>\
**Category:** Sonatype Nexus Repository\
**Created:** [January 20, 2026, 2:48pm UTC](https://community.sonatype.com/t/inquiry-regarding-supported-databases-for-the-read-only-api/15988 "2026-01-20T14:48:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shogo\_Haruyama](https://avatars.discourse-cdn.com/v4/letter/s/e36b37/32.png) [@Shogo\_Haruyama](https://community.sonatype.com/u/Shogo_Haruyama)\
**Post date:** [January 20, 2026, 2:49pm UTC](https://community.sonatype.com/t/inquiry-regarding-supported-databases-for-the-read-only-api/15988/1 "2026-01-20T14:49:00Z")

</div>

Regarding the documentation at [https://help.sonatype.com/en/read-only-api.html](https://help.sonatype.com/en/read-only-api.html):

The manual states, “This feature is only appropriate for installs that use the legacy OrientDB embedded database.”  
I would like to confirm the detailed meaning of this statement.

My understanding was that by performing a “freeze,” it is possible to prevent input from the GUI and block updates through the API. However, does this statement mean that the read-only API cannot be used if PostgreSQL is used as the database?

In our operational verification, it appears that the freeze function of the read-only API prevents updates from the GUI as expected. We would like to clarify what the actual limitations are.

Thank you in advance.