See Your Database in the Browser: A One-Click SQL Console for Postgres and SQLite

You deployed an app on VibeNest. It is running, it has a database, and now you want to do the most ordinary thing in the world: look at your data. Until today that meant SSH, port-forwarding, or a local SQL client — and pointing one of them at a database that is supposed to stay private.

Now it is a button. We are shipping the Database Console: a web-based SQL console for your project's database, opened in one click and embedded right in your VibeNest dashboard. It works for both managed Postgres and SQLite, it is free, and it closes itself when you are done.

One Click, Right in the Dashboard

Open your project, go to the Storage tab, and click Open DB console. A few seconds later a full SQL browser opens inside the dashboard, already connected to your database. There are no connection strings to copy, no credentials to manage, and nothing to install.

You can browse tables, inspect schema, run queries, and export results as JSON or CSV — the same things you would do in a desktop SQL client, without leaving the browser.

Postgres and SQLite, Both Covered

If your project uses a managed Postgres database, the console connects to it over the internal network. No public port is ever opened to reach it.

Postgres — inspecting a table's structure (columns and types), with tabs for rows, queries, indexes, and activity.

If your project stores data in a SQLite file on a persistent volume, the console reads that exact file.

SQLite — running a read-only SELECT against your app's live .db file, with results rendered right in the dashboard.

SQLite was the harder of the two. A SQLite database is just a file living inside your application's storage volume, and that volume belongs to your app, not to the console. We solved it by mounting your app's live volume into the console as read-only, so you see the same .db file your app is writing — with no change to your project and no copy to keep in sync.

Safe by Design

A database console is a powerful thing to hand out, so we were deliberate about the boundaries:

• Scoped to your database only. The console runs on the same server as your database, inside the same private network. It has no path to anyone else's data.
• Behind your login. Access uses a one-time link tied to your account and that specific console session. The console container also requires its own credentials, so a leaked URL on its own gets you nothing.
• Read-only where it matters. The SQLite console opens your live file strictly read-only, so looking at your data can never corrupt it.
• Temporary by default. The console stops itself after a short idle period and is removed entirely a couple of hours later. Nothing lingers.

How to Use It

1. Open your project and go to the Storage tab.
2. For Postgres: attach a managed database first, if you have not already.
3. For SQLite: make sure your project has a persistent volume where the .db file lives.
4. Click Open DB console and start querying.

What This Enables

Inspecting your production data used to be the kind of task you put off because the setup was annoying. Now it is one click. Whether you are debugging a bad row, checking that a migration ran, or just curious what your app has been storing, your database is right there in the browser — and just as private as it was before you looked.

Questions or feedback? Email us at info@vibenest.net with your project name.