Use cases

Internal operations dashboards your team builds itself

An internal operations dashboard puts the numbers and queues a team works from every day on one screen, such as orders by status, cash position or service health. With Diakrin, a team describes the dashboard to its coding agent, IT approves read access to each named data source, and the dashboard runs in the company's own cloud where only its audience can open it.

Last reviewed

An internal operations dashboard puts the numbers and queues a team works from every day on one screen: orders moving from received to shipped, daily cash position, service health per environment, or leads and spend by channel. Teams usually know exactly what they want to see. What slows them down is getting the data access approved and the dashboard hosted somewhere IT accepts.

What does the app do?

  • Shows current state. Key figures and queues for the team's own work, on one screen.
  • Shows trends. Values over a chosen period, with the underlying rows available in a table.
  • Filters and drills down. By team, owner, status or environment, from a number to the records behind it.
  • Flags what needs attention. Items past a threshold the team defines, such as low stock or overdue orders.

Who uses it?

WhoWhat they do
The operations teamWorks from the dashboard every day
Team leads and leadershipReview trends and exceptions
The app ownerDecides what the dashboard shows and who can open it
ITApproves the data sources it reads and its releases

For example, an operations team might track stock and orders, a finance team cash position, or an engineering team release health.

What data does it touch?

This is the main question for any dashboard. With Diakrin, a dashboard reads only what IT has approved. Each company source is requested by the app as a named operation; IT approves it with resource and field limits; an authorized owner enters credentials on a customer-hosted form; and the connection is verified in your cloud before the app can use it. The app and each employee need their own grants, so being in the audience does not by itself give someone access to every source. Data the dashboard keeps for itself lives in its own PostgreSQL database in your cloud.

Scheduled jobs are not offered yet, so design the first version to read approved data on request or from its own database. See Review capabilities and deployment.

How is it built?

Describe the dashboard to your coding agent, starting with synthetic data so you can agree on the layout before real access is approved:

text
App: Orders and stock overview
Purpose: Show today's orders by status and items below their reorder level.
Audience: The warehouse team and its leads.
Initial data: Synthetic examples only.
Success: A team lead sees open orders by status and the items to reorder, and can filter by location.
Before launch: Confirm approved read access to the order and stock sources, the audience and the cloud setup.

The agent connects through MCP or the Diakrin CLI with your permissions, reads the app's approved requirements and builds on the company template. When the dashboard needs a real source, it requests access instead of asking for credentials. See Connect your coding tool.

How does IT approve it?

IT approves each data source separately, then approves the release. Diakrin prepares a plan with the exact image, target, cost estimate and access implications, and, under your approval policy, an eligible reviewer who is not the requester approves or denies it. The app's monthly budget ceiling is checked before each deployment. See Preview, approve and deploy.

Where does it run?

In your company cloud setup on AWS or Google Cloud, next to the data it is allowed to use. Employees open it with company sign-in, and only its audience gets in. IT sees its cost, data and activity alongside every other app. See deploy internal apps in your AWS account.

Related: admin panels and request trackers.

Frequently asked questions

What data can an operations dashboard read?

Its own database, plus company data sources IT approves. Each source is a named operation with resource and field limits, and the app and each employee need their own grants.

Can the dashboard refresh on a schedule?

Scheduled jobs are not offered yet. Plan the first version so the dashboard reads approved data when someone opens it, or works from data stored in its own database.

Does Diakrin see the numbers on the dashboard?

No. Business data stays in your cloud account. On AWS, Diakrin's data view reports sizes and names, such as tables and estimated row counts, never row values.

Can we limit a dashboard to leadership?

Yes. The app's audience can be named people, a directory group from your identity provider, an access group or everyone in the organization. Access changes apply without a new release (on Google Cloud, IAP picks them up at the next deployment).

How do we know what the dashboard costs to run?

Each app has a monthly budget ceiling and a cost estimate based on its observed usage and the cloud provider's public prices. The estimate is not your cloud bill.

See Diakrin with your own cloud

Let your team build internal apps with the AI tools they already use, while IT keeps control of identity, data, approvals and spend.