Organization database
What it is
The organization database is a private PostgreSQL database that Honeybase provisions for your organization. It is the place to put data that belongs to your workflows themselves — lookup tables, accumulated results, state that outlives a single run — when you do not have an external database to point at.
It behaves like a PostgreSQL integration everywhere it matters: SQL nodes select it the same way, and queries run against it the same way. The difference is entirely in its lifecycle.
There are no connection fields to fill in. Honeybase provisions the database, holds the credentials, and connects to it for you — which is why it appears on the Integrations page but cannot be added from Add integration.
Enabling it
Open Database. Enabling provisions the database and makes it available to SQL nodes; there is nothing to configure and no credential for you to hold.
Barry can also offer to enable it in chat, as a one-click card rather than a connection form.
Inactive trial databases
When trial cleanup is enabled for the deployment, a database may be removed only after the trial has ended for at least 30 days and the workspace has had no sign-in, entry or execution activity for at least 30 days. The owner must receive an email warning at least seven days before removal. Entering the workspace or starting a run cancels pending cleanup.
After removal, members with database-management permission can choose Reactivate database (starts empty) on the Database page. Reactivation creates a new empty database; it does not restore the previous data.
When to use it instead of a PostgreSQL connection
Use the organization database when the data is about your automation and has no home elsewhere. Use a PostgreSQL connection when the data belongs to a system you already run — reporting off your production replica, writing back to an application's schema — because that keeps ownership and backups where they already are.