Bring Firebird's Hidden Schema Structure into the Open

DbSchema connects to Firebird through the Jaybird driver and renders the complete schema — tables, stored procedures, triggers, and generators — as ER diagrams and documentation fit for system deliveries and compliance audits.

Diagram tables together with procedures, triggers, and generators
Run PSQL and system-table queries in the SQL editor
Export audit-ready documentation of the complete schema
Compare database copies to spot structural drift

available for

ISO-27001 certified

Free Community Edition No signup required 15-day Architect trial included

Free Download

DbSchema visualizing a Firebird database schema as an ER diagram

Trusted by teams at

Embedded for a Decade,
Documented Never

Firebird ships inside desktop and industrial applications, then runs for years at customer sites with no DBA nearby — while much of the logic sits in stored procedures, triggers, and generators. When the audit or the rewrite arrives, the .fdb file is often the only documentation left.

DbSchema turns that file's schema into a diagram, a document, and a baseline you can compare against.

Reverse Engineer, Document & Compare
Firebird Databases

From an inherited .fdb to a schema your team can discuss.

Reverse engineer a Firebird schema with stored procedures and triggers

Everything in the Database, on a Canvas

DbSchema reads the full schema — including stored procedure and trigger metadata — and lays out table relationships and generator usage visually, not as a bare table list.

Generate HTML documentation for a Firebird database

Ship the Schema With the System

Generate structured HTML documentation covering tables, constraints, procedures, triggers, and generators — ready to attach to a delivery package or an audit file.

Compare Firebird database copies for structural differences

Know What Changed at the Customer Site

Compare two Firebird database copies, or a copy against the model, and get every structural difference listed before you decide what to do about it.

A Model File for a Database
That Ships Inside an Application

DbSchema keeps the Firebird schema in a design model file, versioned with the application that embeds it. Design offline, review changes in Git, and read the SQL before any customer database is touched.

Design the Firebird schema without a connection

No Connection Needed

Work on the schema from the model while installed databases stay untouched.

Version the Firebird schema with the application in Git

Versioned With the App

The model file commits next to the code that ships with Firebird inside.

Read the generated Firebird SQL before it runs

SQL You Read First

Preview the exact statements a schema change will run before applying it.

Apply one reviewed Firebird change across installations

Same Change, Every Site

Carry one reviewed change consistently across the installations that need it.

Firebird Connection Details

DbSchema connects through Jaybird, the official Firebird JDBC driver, downloaded from the Firebird download page and added in the driver manager. The default port is 3050, and the URL takes the form jdbc:firebirdsql://host:3050//path/to/database.fdb — Jaybird requires the double slash before the absolute file path. Embedded Firebird uses jdbc:firebirdsql:embedded:/path/to/database.fdb with the embedded Jaybird build.

For databases with UTF-8 encoding, append ?encoding=UTF8 so character data is read and written correctly. More on the Firebird JDBC driver page.