Traditional BI tools work like an Excel pivot table: Put some fields on the X axis, some fields on the Y axis, and get an aggregation or visualization in the middle. The input is always a single table (or, if you have multiple tables, a flat join across all of them).
Ultorg is better at working with databases that have multiple tables in them, across arbitrary one-to-many relationships (not just warehouse-style star schemas), and where you want to look at actual raw data rather than colorful aggregations. There are specialized automatic table styles that visualize e.g. how one table relates to others through nested or parallel joins. The data displays you see in Ultorg are also editable--you can commit changes back to the database if desired.
You can edit data in existing tables, but there is not yet a "Create Table" action. In fact, Ultorg does not currently host any data at all; it is all assumed to be existing in an external data source.
So for now I'd recommend doing the actual CREATE TABLE statements manually in e.g. an external PostgreSQL database, but then using Ultorg to edit the data.
Schema editing actions (Create Table, Insert Column etc.) are on the TODO list, though.
Traditional BI tools work like an Excel pivot table: Put some fields on the X axis, some fields on the Y axis, and get an aggregation or visualization in the middle. The input is always a single table (or, if you have multiple tables, a flat join across all of them).
Ultorg is better at working with databases that have multiple tables in them, across arbitrary one-to-many relationships (not just warehouse-style star schemas), and where you want to look at actual raw data rather than colorful aggregations. There are specialized automatic table styles that visualize e.g. how one table relates to others through nested or parallel joins. The data displays you see in Ultorg are also editable--you can commit changes back to the database if desired.