Build your own workspace.

Define your fields, compose your screens and try the result. Choose a starting point or design your own.

Loading design…

Analyse project data and follow up

Prepare your question here and select your data in your project’s analysis workspace. This transfers the analysis request, not screen designs or schema changes.

Your goal What question would you like answered? After the measurement

The question travels in the browser-only part of the link and is removed from the address as the project workspace opens. Do not treat it as secret storage; do not include keys, passwords or private customer data. This does not send data to a model, database or external system.

I agree to carry this question to the project workspace. I will separately review source/fields, model use and background permission there.

Connect a project · inspect schema differences

Choose an authorized project using “Design in Studio” in project settings. File comparison below is local; ownership and freshness of the schema file are not verified.

Requires an authorized project and a previously registered isolated workspace source. Reads table/column structure only, not records, connection secrets or commands. Opening a file does not establish this binding.

Open a generator TXT definition or a SQL Server/PostgreSQL/MySQL catalog copy in ogan.database.catalog v1 format. The catalog covers selected tables only; its date or filename is not proof of project ownership or freshness.

The file stays in your browser. Passwords, roles, defaults and records are excluded. Only mappings and a structural fingerprint can be saved with a project draft; this does not prove schema freshness. Standard draft downloads contain only the design.

INSTANT VIEW

Role simulation

Form, table and summary share one data definition. Trial records are not saved to a file or server.

Validation and application requirements

Not checked yet. Edit the draft, then choose Check definition.