PostgreSQL logo

Kyubit Business Intelligence · PostgreSQL

Business intelligence & analytics for PostgreSQL

Turn PostgreSQL tables and relational data into business-friendly measures, interactive reports and dashboards on your own infrastructure.

Connect natively to PostgreSQL, model relationships visually, and give colleagues a browser-based workspace for exploring their data. Kyubit brings the semantic model and the reporting experience together.

Kyubit visual model designer with related tables, measures and dimensions
Kyubit interface example using sample data.

Give your PostgreSQL schema a business vocabulary

Application schemas describe how data is stored. Business users need to understand revenue, products, customers and time. Use Kyubit's visual semantic modeling to turn those relationships into a reusable analytical structure.

  1. ConnectCreate a PostgreSQL data source and verify access to the required tables.
  2. ModelChoose a fact table, join related tables and define measures and dimensions.
  3. ProcessImport and prepare the selected data in a Kyubit analytic model.
  4. ExploreUse the processed model for grid analysis, reports and dashboards.

Start with one subject area, such as invoice lines linked to customers and products. Check the meaning of each row before adding relationships, so joins do not multiply revenue. Keep transaction identifiers as Dimension Details when users need record-level context rather than another grouping axis.

Native PostgreSQL connectivity, with a deliberate reporting boundary

Connect the tables your team needs

Configure the PostgreSQL endpoint, database and connection account in Kyubit. Confirm that the account can read the intended schemas and objects, then inspect sample records before building the model. Give reporting access to the relevant data rather than exposing every application table.

Prepare clear analytical columns

Use suitable relational columns for amounts, categories and dates. If an application stores nested JSON, arrays or custom values, prepare a reporting view or query that exposes the fields you need as ordinary columns, and validate their mapping. Connectivity is not a promise that every PostgreSQL-specific type is an analytical attribute.

Already have reporting views? Include them in your connection evaluation and use the supported modeling or SQL-query workflow for your objects. The visual model designer guide explains the core setup steps.

Analyze PostgreSQL data without writing SQL for each question

After the model is prepared, users select measures and dimensions instead of writing a new query for every breakdown. Start with revenue by month, add a product category, then filter a country or customer segment.

  • Drill down through configured hierarchies on the analysis grid.
  • Use slicers to focus on a meaningful subset of the data.
  • Compare measures side by side and save useful analyses as reports.
  • Build dashboard charts and KPIs from shared metric definitions.

Explore the wider self-service analytics experience.

Kyubit analysis grid with sales measures, countries and product categories
Kyubit interface example using sample data.

Keep reporting aligned with your PostgreSQL update cycle

A processed semantic model has its own refresh cycle. Choose a schedule that matches the reporting need and the workload of the source database.

  • Full processing: rebuild the model from the selected source data.
  • Partial processing: refresh the configured recent period when transactions can change.
  • Incremental processing: append new data when the source and model are configured for that workflow.

For example, refresh a recent sales window to include corrections, while using an appropriate strategy for newly appended transactions. Do not assume an append-only refresh captures historical edits or deletions.

Kyubit processing dialog offering full, partial and incremental processing
Kyubit interface example using sample data.

Self-hosted PostgreSQL BI with a separate application tier

Your PostgreSQL server can remain in its existing environment, including Linux. Kyubit runs on Windows/IIS and connects over the configured network connection. Users access Kyubit through their browsers; they do not need a PostgreSQL query tool.

Plan the Kyubit environment

Include Windows/IIS and Microsoft SQL Server for Kyubit's internal databases in your deployment plan. PostgreSQL is the analytical source; it does not replace those application prerequisites.

Publish controlled reporting access

Configure Kyubit users and object permissions for models, reports and dashboards. Review the connection account separately: database grants and application permissions serve different purposes.

No upload to a vendor-hosted analytics service is required. Processing brings selected source data into Kyubit's analytic environment; plan access, storage and backups accordingly.

From an application database to a shared dashboard

Bring monthly revenue, product mix and regional performance into one view. Let readers use dashboard slicers, and schedule recurring reports for the people who need a regular update.

Kyubit dashboard with trend chart, KPI cards, bubble chart and product breakdown
Kyubit interface example using sample data.

See dashboard capabilities and scheduled report delivery.

Frequently asked questions about PostgreSQL BI

Can Kyubit connect natively to PostgreSQL?

Yes. Kyubit provides native PostgreSQL connectivity for building analytic models and working with SQL data. Validate access to your schemas, objects and selected column types during setup.

Can business users analyze PostgreSQL without SQL?

Yes. Once a model has been prepared, users can select measures, dimensions and slicers visually. Source preparation and model design remain setup tasks for someone who understands the data.

Can PostgreSQL stay on Linux?

Yes. PostgreSQL can stay on its existing host if it is reachable from the Kyubit server. Kyubit itself runs on Windows/IIS and requires Microsoft SQL Server for its internal databases.

Does my PostgreSQL data have to move to a public cloud?

No. Kyubit can run on your own infrastructure. The semantic-model workflow processes selected source data into the Kyubit environment, so it is not a zero-copy connection.

Can PostgreSQL models be refreshed incrementally?

Yes. Kyubit supports full, partial and incremental model processing. Choose a strategy that handles your new records and any changes to previously imported data.

Try Kyubit with your PostgreSQL data

Connect a PostgreSQL data source, model one business question, and test the complete path from source records to a shared report.