Use cases

Internal request tracker apps for any team

An internal request tracker app gives a team one place to take in requests from colleagues, assign them and show their status, instead of chat threads and spreadsheets. With Diakrin, the team describes the tracker to its coding agent, starts with synthetic data, and runs it in the company's own cloud after IT approves the release, with only the intended audience able to open it.

Last reviewed

An internal request tracker app gives a team one place to take in requests from colleagues, assign them and show where each one stands. Operations, IT, people and support teams all run some version of this, often in a shared inbox or a spreadsheet. A request tracker is also the example first app in the Diakrin documentation, because it has a clear owner, a clear audience and works well with sample data.

What does the app do?

  • Intake. Employees submit a request with a category, description and urgency.
  • Queue. The team sees open requests, filters them and assigns an owner.
  • Status. Team leads update the status; requesters see their own requests and the latest status.
  • Resolution. Closed requests keep their history, so the team can see what came in and how it was handled.

Who uses it?

WhoWhat they do
Requesters across the companySubmit requests and check their status
The owning teamTriage, assign and resolve requests
Team leadsReview the queue and update statuses
The app ownerManages who can open the app and changes the workflow

What data does it touch?

Requests, comments and statuses live in the app's own PostgreSQL database in your cloud. Attachments, if the app needs them, go to the app's own file storage. A first version needs no company systems at all. If the team later wants, for example, a list of employees or systems to pick from, the app requests a named read operation and IT approves it with resource and field limits.

How is it built?

Describe the app in the console or from your coding tool. This brief is taken from Create your first app:

text
App: Team request tracker
Purpose: Employees submit requests; team leads review and update their status.
Audience: The operations team and its assigned reviewers.
Initial data: Synthetic examples only.
Success: A requester can see their own request and its latest status.
Before launch: Confirm ownership, reviewer access, approved data and the cloud setup.

Then ask your coding agent: "Use this app's approved requirements to build a request tracker with synthetic examples. Show any missing access or deployment prerequisites before continuing." The agent works through MCP or the Diakrin CLI with your own permissions. Saving a version builds and checks it in your cloud; before the first publish it goes to a private preview. See Connect your coding tool.

How does IT approve it?

IT can prepare the app for a team before building starts, which sets up building access, a draft approval policy and spending ledgers together. Before launch, IT confirms the environment, audience, data, runtime, cost, approver and recovery path. Under your approval policy, an eligible reviewer who is not the requester then approves the exact release plan. See Review capabilities and deployment.

Where does it run?

In your company cloud setup on AWS or Google Cloud. Employees open it with company sign-in, and only the app's audience gets in: named people, directory groups, access groups or everyone in the organization. Removing someone from the organization ends their app sessions. See Sign in to company apps.

Related: approval workflows and admin panels.

Frequently asked questions

Why build a request tracker instead of buying a ticketing tool?

Teams often need a small, specific intake flow with their own fields and statuses. A purpose-built tracker can match that flow and keep the data in the company's own cloud, with company sign-in and IT approval.

Who can see the requests?

Only people in the app's audience can open it. Within the app, which records each person sees is decided by the app itself, for example requesters see their own requests and team leads see all of them.

Where are the requests stored?

In the app's own PostgreSQL database in your AWS account or Google Cloud project. On AWS, Diakrin reports sizes and names of what is stored, never row values.

Is a request tracker a good first app?

Yes. The Diakrin documentation uses a team request tracker as the example first app, because it has a clear owner and audience and works well with synthetic data.

Can we change the tracker after launch?

Yes. The builder saves a new version, it passes its checks, and publishing it is an approved rolling update that replaces the old version only when the new one is healthy.

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.