Databases

Database Studio

Database Studio lets you browse and edit your project databases right from the Lofenta dashboard, with no extra credentials or external client required. Each database engine gets a tailored interface: a full table editor for PostgreSQL and MariaDB, a document browser for MongoDB, and a key explorer for Redis. Every engine also includes a built-in console for raw queries.

What it is

Open Studio from the project page of any database service (PostgreSQL, MariaDB, MongoDB, or Redis). If you have an application project with a linked database, you can also reach Studio from the Connected services panel via the Studio link next to each attached service.

When a project has more than one database linked, a picker at the top of Studio lets you switch between them. You can also jump directly to a specific database with the?target={serviceProjectId} query parameter.

Four engines, one interface

PostgreSQL: full table editor with schema browsing, column types, filters, sorting, and inline cell editing.
MariaDB: same table editor as PostgreSQL, adapted for MySQL-dialect column types and constraints.
MongoDB: document browser showing collections and BSON documents as formatted JSON, with inline editing and deletion.
Redis: key explorer with type-aware value display for strings, hashes, lists, sets, and sorted sets. TTL shown and editable.

The data grid

The table and document views share a consistent grid. Understanding the editing rules saves time:

Click any cell to enter edit mode. Press Enter to save the change, or Esc to cancel and revert.
Tables without a primary key are read-only. Studio cannot safely identify which row to update without a unique anchor, so those tables show data but block all writes.
Binary columns are not editable and display a placeholder instead of raw bytes.
Add filters from the toolbar to narrow rows by column, operator, and value. Multiple filters combine with AND. Sort by any column ascending or descending.
Pages are 50 rows each. Use the pagination controls at the bottom of the grid to move between pages.

Row counts shown next to table names are approximate (from database statistics) and may not match the filtered result count. The exact count appears after a filter is applied.

The console

Each engine includes a console tab for running raw statements directly against the database:

PostgreSQL and MariaDB: standard SQL statements, including SELECT, INSERT, UPDATE, DELETE, and DDL.
MongoDB: shell-style commands (e.g. db.collection.find({})).
Redis: standard Redis commands (e.g. KEYS *, HGETALL mykey).

Destructive statements require confirmation

Statements that drop tables, delete rows without a filter, or flush data trigger a confirmation prompt before running. This applies to DROP, unbounded DELETE, TRUNCATE, FLUSHDB, and similar operations.

Output is capped at 256 KiB. Larger result sets are truncated with a notice.
Statements time out after 30 seconds. Long-running queries are cancelled automatically.

Productivity

A few extras make day-to-day work faster:

Foreign-key navigation. Cells that reference another table are clickable. Click one to jump to the referenced table, already filtered to the matching row.
Exact row count. The sidebar shows an approximate count from database statistics. Press Count in the table footer for the exact number with your current filters applied.
Duplicate a row. Copy any row into the add-row form, minus its primary key, so the database assigns a fresh one.
Export. Download the current table as CSV, or as JSON for PostgreSQL, with your filters and sort applied. Export is not capped at 256 KiB, it streams the full result.
Health tab. See database size, the largest tables, and active connections at a glance for every engine.

Roles and access

Studio respects the same role model as the rest of the dashboard:

Role	Can browse data	Can edit data and run console
Viewer	Yes	No (read-only)
Developer	Yes	Yes
Admin / Owner	Yes	Yes

Personal projects follow the same split: the project owner has full write access, and any collaborators inherit from their assigned role.

Privacy

Studio commands run inside your database container over Lofenta's internal channel. Your database credentials stay in the container and are never sent to your browser or stored by Lofenta. The browser only receives query results, which are transmitted over TLS and discarded from Lofenta servers once delivered.