IT Ticketing on the database you already run

IT Ticketing that lets you handle requests and approvals in one place. Connect your database. Control who sees what. Self-host it.

Trusted by Some of the World’s Best Product Teams

Build exactly what your team needs

Ticket, asset and user records stay in the systems you already run. Jet adds intake, routing and SLA tracking, shaped around your queues rather than a vendor's.

Build secure app fast

Describe how requests reach IT and Jet builds the intake, triage and resolution views on your data. Adjust queues, priorities and SLAs visually.
Connect to Your HR Database or HRIS API Directly
Whether HR data lives in Postgres, MySQL, or a third-party HRIS REST API, Jet Admin builds the employee portal on top — no migration, no re-entering employee records, always live from your HR system.
Each Employee Sees Only Their Own HR Data
Row-level access ensures every employee sees only their own pay stubs, leave balances, and performance records — even when all employees share the same database table. No data leakage, no custom code.
Manager Dashboards with Direct Report Visibility
Give managers a view of all their direct reports — leave requests pending approval, performance notes, and headcount — without exposing other teams' HR data. Role-based access at the team level.
Self-Service Leave Requests and Approvals
Employees submit time-off requests through a form that writes to your HR database. Managers approve with one click from their dashboard. The entire workflow is tracked and logged without email chains.
Benefits and Payroll Document Access
Let employees download their own pay stubs, tax documents, and benefits summaries directly from the portal — scoped to their own records, without HR needing to email documents individually.

Data sources

IT Ticketing System alongside the rest of your stack

Frequently asked questions

What is an IT ticketing system?

Software that turns an IT request into a tracked item with an owner, a priority and a resolution, so work is visible rather than living in a shared inbox and three Slack threads.

Can staff raise tickets without training?

Yes, through a short form that captures what you need to triage — which is usually the difference between a ticket queue and a queue of tickets that say 'it is broken'.

Does it handle SLAs?

Yes. Response and resolution targets by priority drive what appears at the top of the queue, and breaches are visible before they are explained.

Can tickets link to the asset involved?

Yes. A ticket against a specific laptop or system builds a history, so recurring failures on one device or one integration become visible.

Can we automate routine requests?

Yes. Common requests can trigger an API call rather than a human task — access grants, provisioning and resets are the usual first candidates.