How to use Liam ERD with a private GitHub repository?

Run 'npx @liam-hq/cli init' for an interactive setup that generates diagrams from your private repo's schema without exposing it publicly. Check the documentation for detailed configuration steps.

Liam ERD vs MySQL Workbench for ER diagrams?

Liam ERD is web-based and excels at quick, zero-config reverse engineering from existing schemas, while MySQL Workbench is a desktop tool with forward engineering and comprehensive database management. Choose Liam for visualization speed and MySQL Workbench for full design cycles.

Can Liam ERD handle PostgreSQL schemas?

Yes, Liam ERD supports PostgreSQL and other databases by processing schema files or connections. Provide your schema in a compatible format, and refer to the docs for specific examples.

Is Liam ERD free for commercial use?

Yes, it's open-source under Apache License 2.0, allowing free commercial use. However, for public repos, the web service might have usage limits, so review the terms.

How to customize the appearance of Liam ERD diagrams?

As an open-source project, you can modify the codebase for deep customization. The UI offers built-in interactive features, but for visual tweaks, fork the repository or contribute changes.

Does Liam ERD support real-time database updates?

No, it generates static diagrams from schema snapshots and doesn't sync with live database changes. It's designed for documentation, not real-time monitoring.

/create-pull-request — Automated Pull Request Tool

What is /create-pull-request?

Liam ERD is an open-source tool that automatically generates beautiful and interactive entity-relationship diagrams from database schemas. It solves the problem of visualizing complex database structures by providing a clear, readable representation that enhances understanding and documentation. The tool works with both public and private repositories, requiring minimal setup.

Target Audience

Database administrators, backend developers, and software engineers who need to visualize, document, or collaborate on database schemas in projects of any size.

Value Proposition

Developers choose Liam ERD for its zero-configuration setup, high performance with large schemas, and fully open-source nature, allowing customization and community contributions unlike many proprietary diagramming tools.

Automatically generates beautiful and easy-to-read ER diagrams from your database.

Use Cases

Best For

Visualizing complex database schemas with 100+ tables
Documenting database structures for team collaboration
Reverse engineering existing databases into diagrams
Improving understanding of legacy database systems
Generating ER diagrams for public or private repositories
Creating interactive diagrams with panning and zooming features

Not Ideal For

Projects requiring real-time database monitoring or synchronization
Teams needing forward engineering from diagrams to schema code
Environments with strict offline requirements or no internet access
Organizations with policies against using external services for sensitive schemas

Pros & Cons

Pros

Interactive Visualization

Features panning, zooming, and filtering allow easy exploration of complex schemas, as demonstrated in the demo GIF for intuitive navigation.

Zero-Config Setup

For public repositories, simply insert a URL into liambx.com; for private repos, use 'npx @liam-hq/cli init' with minimal steps, requiring no prior configuration.

Scalable Performance

Optimized to handle large databases with 100+ tables efficiently, ensuring smooth performance even for extensive schemas.

Open-Source Flexibility

Fully open-source under Apache License 2.0, enabling community contributions and customization, unlike proprietary alternatives.

Cons

Web Service Dependency

Public repository visualization relies on liambx.com, which may introduce privacy risks or downtime concerns for sensitive data.

No Forward Engineering

Only supports reverse engineering from schemas to diagrams, lacking features to generate code from diagrams, which limits design-first workflows.

Limited Database Support Clarity

README doesn't explicitly list all supported databases, potentially causing compatibility issues with less common systems.

What is /create-pull-request?

Target Audience

Database administrators, backend developers, and software engineers who need to visualize, document, or collaborate on database schemas in projects of any size.

Value Proposition

Use Cases

Best For

Visualizing complex database schemas with 100+ tables
Documenting database structures for team collaboration
Reverse engineering existing databases into diagrams
Improving understanding of legacy database systems
Generating ER diagrams for public or private repositories
Creating interactive diagrams with panning and zooming features

Not Ideal For

Projects requiring real-time database monitoring or synchronization
Teams needing forward engineering from diagrams to schema code
Environments with strict offline requirements or no internet access
Organizations with policies against using external services for sensitive schemas

Pros & Cons

Pros

Interactive Visualization

Features panning, zooming, and filtering allow easy exploration of complex schemas, as demonstrated in the demo GIF for intuitive navigation.

Zero-Config Setup

For public repositories, simply insert a URL into liambx.com; for private repos, use 'npx @liam-hq/cli init' with minimal steps, requiring no prior configuration.

Scalable Performance

Optimized to handle large databases with 100+ tables efficiently, ensuring smooth performance even for extensive schemas.

Open-Source Flexibility

Fully open-source under Apache License 2.0, enabling community contributions and customization, unlike proprietary alternatives.

Cons

Web Service Dependency

Public repository visualization relies on liambx.com, which may introduce privacy risks or downtime concerns for sensitive data.

No Forward Engineering

Only supports reverse engineering from schemas to diagrams, lacking features to generate code from diagrams, which limits design-first workflows.

Limited Database Support Clarity

README doesn't explicitly list all supported databases, potentially causing compatibility issues with less common systems.

/create-pull-request

What is /create-pull-request?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

/create-pull-request

What is /create-pull-request?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?