Yes, you can set BASEROW_ENTERPRISE_AUDIT_LOG_RETENTION_DAYS to control how long audit logs are kept. Setting this to 30 days would automatically prune logs older than a month.
Actions (which power the undo/redo functionality) can also take up significant space. Consider setting BASEROW_JOB_CLEANUP_INTERVAL_MINUTES to run cleanup more frequently.
You can also adjust BASEROW_ROW_HISTORY_RETENTION_DAYS to limit how long row history is kept.

I am not familiar with Cloudron but make sure you are also removing old docker images as they also often take up space

and if you are on a Debian based OS and you do updates often the occasional sudo apt auto-remove won’t hurt…
I suspect you have the bulk of the data in the table you found but these are a couple more things you can check that I often see people forget as well

From my discussion with the Cloudron team

# Add Baserow customizations here (https://baserow.io/docs/installation/configuration)

export BASEROW_BACKEND_LOG_LEVEL=INFO

# Changed default because I don't have Enterprise plan and don't have a need for audit log
# But I'm interested in retention history for a bit longer
# See https://forum.cloudron.io/topic/13193/postgre-db-is-big-20-gb-how-can-i-understand-what-s-stored-there/9?_=1738227461250
export BASEROW_ROW_HISTORY_RETENTION_DAYS=365
export BASEROW_ENTERPRISE_AUDIT_LOG_RETENTION_DAYS=30

SELECT relname AS table_name,
       pg_size_pretty(pg_total_relation_size(relid)) AS total_size,
       pg_size_pretty(pg_relation_size(relid)) AS table_size,
       pg_size_pretty(pg_total_relation_size(relid) - pg_relation_size(relid)) AS index_size
FROM pg_catalog.pg_statio_user_tables
ORDER BY pg_total_relation_size(relid) DESC;

And got

So it seems what's taking space are 2 items:

• History of audit, which is useless to me because I'm not "enterprise" (and don't plan on switching plan)
• History of rows, which is definitely useful but I need to be careful because I'm storing data related to crypto and value of each crypto, so changes happen every couple minute on each row

So, db7fdba71d461b44c481e0b8aa8ec62681 is taking 21GB

So it'd be db7fdb, where is the "Dashboard" you mentioned? I didn't understand that part

docker exec -it postgresql /bin/bash
psql -Uroot  --dbname=postgres

Then, run this query in postgresql prompt:

SELECT pg_database.datname AS database_name,
       pg_size_pretty(pg_database_size(pg_database.datname)) AS size
FROM pg_database
ORDER BY pg_database_size(pg_database.datname) DESC;

This gives a bunch of daabase names like dbf88f51a1c41249a6947427dedb491dfd. Take the first 6 characters like f88f51a1 and put in the search field in the dashboard. This will reveal the app.