Product Overview
DbFace is a workspace for internal data products and report delivery. It combines datasource access, SQL querying, DSDL authoring, chart rendering, publishing, sharing, and embedding in one product surface.
Positioning
DbFace is not only a charting tool and not only a SQL IDE. It is closer to a lightweight data application builder that helps teams move from a query to a deliverable dashboard page more quickly.
Core modules
| Module | Purpose | Typical use |
|---|---|---|
| Datasources | Manage database connections and access configuration | Connect MySQL, PostgreSQL, SQLite, ClickHouse, API, or file sources |
| SQL Workshop | Explore data, validate queries, and debug SQL | Verify fields and result shape before building a report |
| Editor | Main report editor with DSDL authoring, AI assistance, and preview | Create dashboards, report pages, and parameterized views |
| Execute / View | Render structure, execute queries, and display final results | Deliver a usable analytics page to business users |
| Embed | Provide embeddable access to reports and dashboards | Place analytics pages into internal systems |
| Cloud Code | Extend the standard widget set with custom components | Add interactive panels, compound views, or domain-specific components |
Who it is for
Business teams
Teams that need to ask questions faster and review analytics pages without learning editor internals.
Analysts
People who want to keep SQL control while improving layout, publishing, and collaboration speed.
Internal product teams
Teams embedding analytics pages into internal back-office, operations, or management products.
Platform teams
Teams that need a unified way to manage access, permissions, and report delivery standards.
What DbFace is good at
- Connecting structured datasources and validating queries quickly.
- Defining dashboards, inputs, widgets, and interactions through DSDL.
- Generating a first report draft with AI, then refining it in the editor.
- Publishing final pages for direct viewing or embedding into other systems.
What it is not trying to be
- It is not positioned as a broad self-service BI suite for every use case.
- It is not a public BI portal product for anonymous external audiences.
- It is not a replacement for a data warehouse or ETL infrastructure.
Standard workflow
- Connect a datasource and verify access.
- Validate fields and query logic in SQL Workshop or the Editor.
- Use AI or manual editing to write DSDL, widgets, inputs, and layout.
- Preview the page and verify rendering and parameter behavior.
- Save, publish, and deliver the final page through View or Embed.