Celiq
v0.12Open app โ†—
Docs/Getting Started/Quick start

Quick start

Go from an empty workspace to your first live Reveal in three steps โ€” connect, model, explore.

LuminaryWeaverTracerUpdated June 2026 ยท 6 min read
โœฆ
In this section
Build your first semantic node in 2 minutes. Connect a warehouse, let Orion generate the CML, run your first Reveal โ€” no SQL needed.
๐Ÿ’ก
Tip
What it is โ€” the fastest path from a fresh Celiq workspace to a live query: connect a warehouse, generate a semantic node with Orion in Forge, and run your first Reveal in Discover.
When to use it โ€” your very first session in a new workspace, or any time you need a refresher on the connect โ†’ model โ†’ explore arc.
Where to find it โ€” everything below lives on the bottom floating navigation bar (the PillNav): Lumen for connections, Loom โ†’ Forge for modelling, and Discover for exploring.
Who can use it โ€” connecting a warehouse is Luminary only; building nodes in Forge is Weaver or Luminary; running Reveals in Discover is open to all roles (Lens, Tracer, Weaver, Luminary).

This guide walks you through the three things every workspace needs before anyone can ask a question: a connected warehouse, at least one modelled node, and a saved Reveal. If your workspace is already set up and you just want to query, jump straight to Run your first Reveal and pick a node that already exists.

Overview

Celiq turns raw warehouse tables into a governed semantic layer your whole team can query in plain language or by clicking. Getting there is three moves:

  1. Connect your data warehouse through the Connection Wizard, an Orion-guided flow that generates a read-only setup script for you to run.
  2. Model a table as a node in Forge โ€” you can write CML by hand, or let Orion generate the node from your schema.
  3. Explore by running a Reveal in Discover โ€” pick fields, run the query with Cmd/Ctrl + Enter, switch to a chart, and save it.

Navigation in Celiq lives on the PillNav, the floating pill-shaped bar pinned to the bottom-centre of the screen. It auto-hides as you scroll down and reappears when you scroll up. Which pills you see depends on your role.

When to use it

  • You just created a workspace and there is nothing to query yet.
  • You are a Luminary onboarding a new data source.
  • You are a Weaver who needs to expose a new table to the team.
  • You are a Tracer learning where things live before running your first query.

If your workspace already has connections and nodes, you do not need to repeat the connect and model steps โ€” go straight to Discover.

Concepts

TermWhat it means
ConnectionA read-only link to a data warehouse (Snowflake, BigQuery, PostgreSQL, Redshift, or MySQL). Created with the Connection Wizard. Managed under Lumen โ†’ Connections.
NodeCeliq's semantic representation of a warehouse table. A node defines the dimensions and metrics that map to that table's columns. Built in Forge.
DomainA grouping of related nodes (with their joins) that backs the Reveals your team queries.
RevealA live query session in Discover โ€” a selection of dimensions and metrics, optional filters, and a visualization.
PrismA saved Reveal. Reusable, shareable, and pinnable to a Mosaic. (Prisms were formerly called "Scenes.")
VaultThe space a Prism is saved into. Your personal Vault is the default home for things you create.
OrionCeliq's AI layer. It guides the Connection Wizard, generates nodes from your schema, and answers questions about the semantic model.

Getting started

You need an account in a Celiq workspace. The role you need depends on which step you are doing:

StepMinimum roleWhere it lives in the PillNav
Connect a warehouseLuminaryLumen โ†’ Connections (/lumen/connections)
Build a nodeWeaverLoom โ†’ Forge (/forge)
Run a RevealLens (any role)Discover (/discover)

If you are a Tracer or Lens joining a workspace that already has nodes built, you can skip the first two steps โ€” a Luminary or Weaver has already done them for you.

Step-by-step

1

Open the Connection Wizard

On the PillNav, open the Lumen pill (visible to Luminaries) and go to Connections, then start a new connection to launch the Connection Wizard. Orion introduces itself and asks you to choose your warehouse type: BigQuery, Snowflake, PostgreSQL, Redshift, or MySQL.

For the full walkthrough, see Connection Wizard.

2

Answer Orion's questions and run the setup script

After you pick a warehouse, Orion asks a short series of questions (host, database, and the like). When it has enough, it generates a read-only setup script for you to run against your warehouse. Run the script, copy its output, and paste it back into the wizard. Orion extracts the credentials automatically โ€” you never type secrets into a form.

3

Test the connection

The wizard tests the connection live. On success you see "You're connected!"; if it fails, fix the credentials and choose Try Again. Click Continue to Setup to hand off to Auto-Provisioning, where Celiq inspects your schema and proposes starter nodes โ€” the fastest way to get something queryable. See Auto-Provisioning.

4

Open Forge to model a node

On the PillNav, open the Loom pill (visible to Weavers and Luminaries) and choose Forge. Forge is where you build the semantic layer. If Auto-Provisioning already created nodes for you, you will see them here; otherwise you will create one in the next step.

5

Generate a node with Orion

In the Forge editor, click Generate with Orion โœฆ. Tell Orion which table to model and which columns to include. Orion reads your schema, infers field types, writes sensible labels, and produces a draft node in CML. Review the generated dimensions and metrics, edit any labels or descriptions, and run Validate to check for errors.

6

Save your changes through the Check & Save gate

When the node is right, save it. Forge runs a Check & Save gate that validates your work before it is committed โ€” if anything is off, it tells you what to fix first. Once saved, the node is available to query in Discover. See Forge for the full Build / Browse / Validate / Evals workflow.

7

Open Discover and pick a node

On the PillNav, click Discover (available to every role). Choose the domain and Reveal โ€” or the node you just created โ€” from the field picker on the left. You will see dimensions and metrics you can add to the canvas.

8

Build and run your first Reveal

Add at least one dimension (for example, Status) and one metric (for example, Total Revenue) from the field picker. Then run the query by pressing Cmd/Ctrl + Enter (or clicking Run). Results appear in the table below the canvas.

9

Visualize and save it as a Prism

Switch to a chart โ€” a bar chart is a good first pick โ€” and Celiq maps your dimension and metric to the axes automatically. When you are happy, save the Reveal (press Cmd/Ctrl + S), name it, choose a Vault (your personal Vault is fine), and save. It is now a reusable Prism you can share or pin to a Mosaic.

Examples

A minimal node Orion might generate for an orders table looks like this. You can review and edit it in Forge before saving:

orders.yml
class=c-name>cml</span><span
<span class="c-key">node</span><span class="c-punc">:</span> <span class="c-name">orders</span>
  <span class="c-attr">label</span><span class="c-punc">:</span> <span class="c-name">Orders</span>
  <span class="c-attr">sql_table</span><span class="c-punc">:</span> <span class="c-name">analytics.orders</span>

  <span class="c-key">dimension</span><span class="c-punc">:</span> <span class="c-name">order_id</span>
    <span class="c-attr">type</span><span class="c-punc">:</span> <span class="c-name">string</span>
    <span class="c-attr">label</span><span class="c-punc">:</span> <span class="c-name">Order</span> <span class="c-name">ID</span>
    <span class="c-attr">sql</span><span class="c-punc">:</span> %%CODEBLOCK0%%lt;span class="c-punc">{</span><span class="c-name">TABLE</span><span class="c-punc">}</span>.<span class="c-name">order_id</span>
    <span class="c-attr">primary_key</span><span class="c-punc">:</span> <span class="c-bool">true</span>

  <span class="c-key">dimension</span><span class="c-punc">:</span> <span class="c-name">status</span>
    <span class="c-attr">type</span><span class="c-punc">:</span> <span class="c-name">string</span>
    <span class="c-attr">label</span><span class="c-punc">:</span> <span class="c-name">Status</span>
    <span class="c-attr">sql</span><span class="c-punc">:</span> %%CODEBLOCK0%%lt;span class="c-punc">{</span><span class="c-name">TABLE</span><span class="c-punc">}</span>.<span class="c-name">status</span>

  <span class="c-key">dimension</span><span class="c-punc">:</span> <span class="c-name">created_at</span>
    <span class="c-attr">type</span><span class="c-punc">:</span> <span class="c-name">date</span>
    <span class="c-attr">label</span><span class="c-punc">:</span> <span class="c-name">Created</span> <span class="c-name">At</span>
    <span class="c-attr">sql</span><span class="c-punc">:</span> %%CODEBLOCK0%%lt;span class="c-punc">{</span><span class="c-name">TABLE</span><span class="c-punc">}</span>.<span class="c-name">created_at</span>

  <span class="c-key">metric</span><span class="c-punc">:</span> <span class="c-name">total_revenue</span>
    <span class="c-attr">type</span><span class="c-punc">:</span> <span class="c-name">sum</span>
    <span class="c-attr">label</span><span class="c-punc">:</span> <span class="c-name">Total</span> <span class="c-name">Revenue</span>
    <span class="c-attr">sql</span><span class="c-punc">:</span> %%CODEBLOCK0%%lt;span class="c-punc">{</span><span class="c-name">TABLE</span><span class="c-punc">}</span>.<span class="c-name">revenue</span>
    <span class="c-attr">format</span><span class="c-punc">:</span> <span class="c-name">currency</span>

With that node saved, your first Reveal in Discover is as simple as: add the Status dimension, add the Total Revenue metric, press Cmd/Ctrl + Enter, switch to a bar chart, and save it as a Prism named "Revenue by status."

Best practices

  • Let Orion do the first draft. Generating a node from your schema is far faster than writing CML by hand, especially for wide tables โ€” Orion adds labels and types automatically. Refine afterward.
  • Validate before you save. Run Validate in Forge so the Check & Save gate has nothing to block on.
  • Start small. One node with a few well-labelled fields is enough to prove the connect โ†’ model โ†’ explore loop. Expand once the basics work.
  • Use your personal Vault first. Save your first Prism into your own Vault while you experiment; promote it to a shared Vault when it is ready for the team.

Tips

๐Ÿ’ก
Tip

In Discover, Cmd/Ctrl + Enter runs the current Reveal and Cmd/Ctrl + S opens the save dialog โ€” you rarely need to reach for the mouse while iterating. For the full list, see Keyboard shortcuts.

Common mistakes

โš ๏ธ
Warning
  • Looking for connections in the wrong place. Connections live under Lumen, not on the Discover or Forge screens โ€” and only Luminaries can see the Lumen pill.
  • Expecting the Loom pill as a Tracer. Forge lives under Loom, which is visible only to Weavers and Luminaries. If you cannot see it, you do not have a builder role.
  • Typing credentials into a form. The Connection Wizard never asks you to type secrets โ€” it generates a script, you run it, and you paste the output back. If you are hunting for a password field, you are off the happy path.
  • Saving a node before validating. The Check & Save gate will stop a node with errors. Run Validate first so save is clean.

Troubleshooting

SymptomLikely causeFix
No Lumen pill on the navYou are not a LuminaryConnecting a warehouse is Luminary-only. Ask a Luminary to add the connection, or have your role upgraded.
No Loom pill on the navYou are a Tracer or LensForge is for Weavers and Luminaries. Ask a builder to model the node you need.
Wizard shows a connection-limit messageYour plan's connection limit is reachedThe wizard surfaces an upgrade prompt naming your current plan and limit. Remove an unused connection or upgrade the plan.
"Connection failed" at the test stepWrong credentials or the setup script was not run correctlyChoose Try Again, re-run the read-only script, and paste fresh output. Confirm host and database details.
Generated node has wrong types or labelsOrion inferred from column names and sample dataEdit the dimensions and metrics in Forge, then run Validate before saving.
Save is blocked in ForgeThe Check & Save gate found validation errorsOpen the gate's message, fix the listed issues, re-validate, then save.
Cmd/Ctrl + Enter does nothing in DiscoverNo fields selected, or focus is in a text inputAdd at least one dimension and one metric, click on the canvas, then run again.
  • Connection Wizard โ€” the full Orion-guided warehouse connection flow.
  • Auto-Provisioning โ€” how Celiq inspects your schema and proposes starter nodes.
  • Forge โ€” model nodes and domains with the Build / Browse / Validate / Evals modes.
  • Discover โ€” the full field-picker, query, and visualization workflow.
  • Key concepts โ€” the core building blocks behind nodes, Reveals, and Prisms.
  • Keyboard shortcuts โ€” every shortcut, including Discover's run and save keys.