Dashboard

What this means

The dashboard is the first place to check the health of your Bilbis organization. It shows setup readiness, active work, recent pipelines, cost movement, throughput, and which engines are spending the most.

Use it as a daily overview. If something needs a response, has failed, or is close to a budget threshold, the dashboard should point you to the right place.

When to use it

Open the dashboard when:

You want to see whether Bilbis is ready to run pipelines.
You need to check if any pipeline is waiting for input.
You want a quick view of cost and pipeline activity.
You need to open a recent pipeline without searching the full list.
You want to start a new pipeline.

Before you start

You need access to an organization. The numbers only reflect the organization currently selected in Bilbis.

Some cards can look empty in a new organization. That usually means Bilbis has not completed any pipelines yet, or setup is not finished.

What you can do here

Area	What it shows	What to do with it
Header	The selected organization and New pipeline button.	Confirm you are in the right organization, then start work if setup is complete.
Setup checklist	Missing LLM credential, Git credential, product, or repository setup.	Complete each item before creating the first useful pipeline.
Active	Pipelines currently running or queued.	Open the filtered pipeline list to see what is in progress.
Needs you	Pipelines awaiting clarification.	Open the pipeline and answer the question before the run can continue.
Failed - 24h	Pipelines that failed in the last 24 hours.	Review the failed runs and decide whether to retry, edit the task, or fix setup.
Budget	Monthly spend compared with the lowest enabled budget alert.	Check Analytics if spend is near or over the threshold.
Cost - 14d	LLM spend over the last 14 days, split into the recent and prior 7 days.	Use it to notice cost movement before opening Analytics.
Throughput - 14d	Completed pipeline activity over the last 14 days.	Use it to see whether Bilbis activity is rising or slowing down.
Recent pipelines	The latest pipelines with state, repository, cost, and start time.	Open a recent result or filter to active, waiting, or failed work.
Top engines	Engines ranked by total spend across completed runs.	Check which engines are driving cost and quality.

Reading the action cards

The four action cards are shortcuts:

Active links to active pipeline work.
Needs you links to pipelines awaiting clarification.
Failed - 24h links to failed pipelines.
Budget links to Analytics, where monthly budget alerts are managed.

If a number is zero, it is informational. If it is highlighted, open the card and review the underlying items.

Reading the trend cards

The dashboard trend cards use short windows:

Cost compares the most recent 7 days with the previous 7 days inside a 14-day view.
Throughput counts pipeline runs in the same 14-day view.

These cards are meant for a quick pulse. Use Analytics for longer 7, 30, and 90 day windows.

What happens next

Most dashboard cards open a more detailed page:

Setup items take you to the setup area.
Pipeline cards take you to filtered pipeline lists or a specific pipeline result.
Budget and cost cards take you to Analytics.
New pipeline opens the form for creating a pipeline.

Problems and fixes

Problem	What to check
The setup checklist is still visible	Finish the missing LLM credential, Git credential, product, or repository setup. The checklist auto-hides when every prerequisite is satisfied.
The dashboard has no pipeline data	Run and complete at least one pipeline. Cost, quality, throughput, and engine cards rely on completed runs.
Costs look lower than expected	In-flight pipeline costs are not counted in Analytics yet. Completed runs are counted.
Budget shows no threshold	Create at least one enabled budget alert in Analytics. The dashboard uses the lowest enabled threshold.
A pipeline needs input	Open the pipeline from Needs you and answer the clarification.
The numbers look like the wrong team	Switch to the correct organization before reading the dashboard.

On this page