Skip to content
Tarsoft

IT Service Management

How to Build an Enterprise ITSM Platform Using Laravel

Published on 27 October 2026  |  11 min read

Commercial ITSM platforms cover most organisations’ needs. But some find that their approval chains, data-hosting requirements, integrations or per-user licence costs do not fit what is on the market. For them, building or extending an ITSM platform can be the better option, and Laravel is a strong framework to build it on.

This article walks through how we would approach an enterprise ITSM platform in Laravel: the architecture, the modules, the data model, the SLA engine, workflow automation, security, integrations and deployment. It assumes familiarity with ITSM concepts; if you need a refresher, see essential ITSM software features.

Why use Laravel for ITSM development?

Laravel is not the only option, and commercial platforms are not inherently worse. But it provides most of the building blocks an ITSM system needs out of the box:

  • MVC architecture that keeps controllers, domain logic and views organised as the system grows
  • Eloquent ORM for modelling tickets, users, assets and their relationships
  • Queues and background jobs for notifications, integrations and SLA checks without slowing down requests
  • Events and listeners for reacting to changes, such as “ticket assigned” or “SLA breached”
  • Notifications over mail, database, and other channels
  • Authentication and authorisation through guards, gates and policies
  • API development with resources, rate limiting and token authentication
  • Testing with a mature feature and unit test toolkit
  • Maintainability, with a large ecosystem and a pool of Malaysian developers who know it

Understanding ITSM system architecture

A practical layered structure:

  1. Frontend: web portal for users and agents (Blade with Livewire, or Inertia with Vue or React), plus a mobile app if needed.
  2. Laravel application: routing, controllers, validation, authorisation.
  3. ITSM domain services: ticket lifecycle, SLA engine, workflow and approval logic, kept in service classes rather than controllers.
  4. Database, cache and queue: MySQL or PostgreSQL, Redis for cache and queues.
  5. External integrations: identity provider, email, monitoring, SIEM, asset inventory, via APIs and webhooks.

Keeping domain logic in dedicated services makes it testable and reusable from the web UI, API, queued jobs and console commands alike.

  • User and role management: users, groups, roles and permissions, synced from the directory where possible.
  • Ticket management: the shared base for incidents, requests and other ticket types.
  • Incident management: priority, major incident handling, resolution.
  • Service request management: catalogue items, forms, fulfilment tasks.
  • SLA engine: policies, calendars, timers and breach handling.
  • Change request management: risk, approvals, schedule, rollback.
  • Workflow management: configurable states, transitions and approvals.
  • Knowledge base: articles, categories, visibility, search.
  • Asset management: inventory, ownership, lifecycle.
  • CMDB: configuration items and relationships.
  • Notification engine: templates, channels, preferences.
  • Audit logging: who did what, when, from where.
  • Reporting and analytics: dashboards and scheduled reports.

Suggested database architecture

An illustrative core schema:

TablePurpose
usersUser identities
rolesAccess roles
ticketsSupport tickets
ticket_commentsTicket activity
incidentsIncident records
service_requestsStandard requests
sla_policiesService level definitions
sla_eventsSLA state changes
change_requestsChange records
approvalsApproval decisions
assetsIT asset records
configuration_itemsCMDB records
audit_logsSecurity and activity audit

A few design notes:

  • Relationships. Incidents and service requests can extend tickets with a one-to-one table, or share it with a type column and type-specific tables. Approvals work well as a polymorphic relationship, so the same table serves requests and changes.
  • Indexing. Index the columns used to filter queues: status, assigned_group_id, priority, due_at, created_at. Composite indexes matching common queue queries make a noticeable difference at scale.
  • Foreign keys keep data consistent. Use soft deletes carefully: a deleted user should not erase the history of tickets they handled.
  • Retention. Decide how long tickets, attachments and audit logs are kept, and archive accordingly, especially where personal data is involved.

Ticket management workflow

A typical lifecycle:

  1. Submitted: via portal, email or API.
  2. Categorised: type, category, affected service.
  3. Priority assessed: from impact and urgency.
  4. Assigned: to a group, then an individual.
  5. Investigation: work notes, communication with the user.
  6. Resolved: with a resolution note.
  7. Closed: after user confirmation or a set period.

Two scenarios need deliberate handling. Reopening: if the user says the issue is not fixed within a set window, the ticket returns to “in progress”, and the SLA policy decides whether the clock resumes or restarts. Escalation: functional escalation moves a ticket to a more specialised group; hierarchical escalation notifies a manager when targets are at risk.

Modelling allowed status transitions explicitly, rather than letting any status change to any other, prevents a whole class of data problems.

Designing an SLA engine

The SLA engine is where most custom ITSM projects become difficult. It needs to handle:

  • Policy selection: which SLA applies, based on priority, category, client or service.
  • Business calendars: working hours, weekends (which differ between some Malaysian states) and public holidays.
  • Response and resolution deadlines calculated in business time.
  • Pause and resume: stopping the clock while waiting for the user or a third party, and resuming when they reply.
  • Escalation: warnings at, for example, 75% of the target.
  • Breach detection and recording.
  • Historical reporting: whether each ticket met its targets.

Store SLA timers as their own records with start, pause and stop events (the sla_events table above), rather than a single due date on the ticket. That makes pauses, reopens and reporting accurate. A scheduled job, run every minute through Laravel’s scheduler, checks timers approaching or past their deadlines and dispatches events.

Write thorough tests for boundary cases: a ticket logged at 5:59pm on a Friday before a public holiday is exactly where SLA engines fail.

Building workflow automation

Laravel’s event system fits ITSM automation naturally:

  • Events describe what happened: TicketCreated, TicketAssigned, SlaBreached, ChangeApproved.
  • Listeners react: assign by rule, notify the requester, create a task, call an integration.
  • Queued jobs do slow work, such as sending email or calling external APIs, in the background with retries.
  • Scheduled tasks handle time-based work: SLA checks, reminders, auto-closing resolved tickets, scheduled reports.

Rules that business users may want to change, such as assignment by category, are better stored in the database and edited through an admin screen than hard-coded.

Authentication and authorisation

  • Laravel authentication for local accounts, if any are needed at all.
  • Role-based access control for what each role can do, refined with policies for record-level decisions, such as “can this agent view this HR ticket?”.
  • Enterprise SSO through SAML or OpenID Connect against Active Directory Federation Services, Microsoft Entra ID or another identity provider. Packages such as Laravel Socialite (with community providers) can help.
  • API authentication with Laravel Sanctum for first-party and token use, or Laravel Passport where a full OAuth 2.0 server is needed.
  • MFA, ideally enforced at the identity provider.
  • Least privilege: agents see the queues they work, administrators are few, and permissions are reviewed.

Security requirements

An ITSM system holds sensitive information: user details, system weaknesses, incident notes. Treat it accordingly, following OWASP guidance:

  • Input validation on every form and API endpoint, using form requests.
  • CSRF protection (on by default in Laravel for web routes).
  • Secure file uploads: restrict types and sizes, store outside the public directory, scan if possible, and serve through authorised downloads.
  • Rate limiting on login, API and ticket creation.
  • Encryption in transit (TLS) and for sensitive fields at rest.
  • Audit logs for logins, permission changes, approvals, exports and record deletions.
  • Secret management: keep credentials out of code and restrict access to .env and deployment secrets.
  • Secure API authentication with scoped, revocable tokens.
  • Sensitive data minimisation: do not collect what you do not need, and avoid putting passwords or personal data into ticket text.

Integrating Laravel ITSM with external systems

Email integration

Create tickets from a support mailbox and thread replies into the right ticket using a reference in the subject or reply address. Inbound email can be received through a mail provider’s webhook or by polling the mailbox.

Enterprise SSO

Users log in with their organisation account, and group membership from the identity provider can map to roles in the ITSM system.

Infrastructure monitoring

Monitoring tools can call an ITSM API or webhook when a service goes down, creating or updating an incident automatically.

SIEM integration

Confirmed security alerts can become incident tickets with an owner and SLA. This needs deduplication and careful field mapping; we cover it in depth in ITSM and SIEM integration.

Webhooks and REST APIs

Expose a documented REST API, versioned and authenticated, and outbound webhooks for key events so other systems can react to ticket changes.

Asset inventory systems

Sync hardware and software inventory from discovery or endpoint management tools rather than maintaining it by hand.

Laravel ITSM deployment architecture

  • Nginx in front, terminating TLS.
  • PHP-FPM running the application, on a supported PHP version that is kept patched.
  • Database: MySQL or PostgreSQL, with backups and, for larger deployments, replication.
  • Redis for cache, sessions and queues.
  • Queue workers supervised by Supervisor or systemd, or Laravel Horizon for Redis queues.
  • Scheduler triggered every minute by cron.
  • Object storage for attachments.
  • Backups of database and attachments, tested by restoring.
  • Monitoring of application errors, queue backlog, failed jobs and server health.
  • CI/CD pipeline running tests before each deployment.

Testing and quality assurance

  • Unit tests for domain logic such as priority calculation.
  • Feature tests for ticket creation, assignment and status transitions.
  • Authorisation tests confirming each role can and cannot see and do the right things. These catch some of the most serious bugs.
  • Workflow tests for approval chains and automatic routing.
  • SLA boundary tests around business hours, weekends, holidays, pauses and reopens.
  • Integration tests with faked external services, plus checks against staging versions of real ones.

Custom ITSM development vs commercial ITSM platforms

Consider custom whenConsider commercial when
Approval chains and workflows are specific to your organisationYour processes fit standard ITSM patterns
Data must be hosted in a particular place or networkVendor-hosted SaaS meets your policies
You need deep integration with in-house systemsPre-built connectors cover your integrations
Per-user licence costs are high because of many requestersUser numbers keep subscription costs reasonable
You have, or can contract, development and support capacityYou prefer the vendor to own the product

Custom development is a long-term commitment: someone must maintain, secure and improve the system for years. Factor that in from the start.

How Tarsoft Care fits a Laravel-based ITSM strategy

Tarsoft Care is Tarsoft’s IT support and service management platform. Its current capabilities cover support ticket management, assignment and status tracking, activity history, workflow and milestone tracking, change requests, SLA tracking and operational reporting.

These form the base described in this article. Modules such as incident and problem management, service catalogue, knowledge base, asset management, CMDB and SIEM integration are on the roadmap, and can be developed or prioritised around an organisation’s own requirements.

Frequently asked questions

Can Laravel be used to develop ITSM software?

Yes. Laravel provides the building blocks: data modelling, queues, events, notifications, authorisation, APIs and testing. The real work is in the domain logic, especially workflows and the SLA engine.

Can Laravel ITSM integrate with Active Directory?

Yes, typically through SAML or OpenID Connect via ADFS or Microsoft Entra ID for login, and LDAP or directory APIs for user and group information.

How do you implement SLA tracking in Laravel?

Store SLA policies and business calendars in the database, record timer start, pause and stop events per ticket, and run a scheduled job that checks deadlines and dispatches warning and breach events.

Can Laravel ITSM support multiple organisations?

Yes, through multi-tenancy, either with a tenant column scoped on every query, or separate databases per tenant. Authorisation and reporting must respect tenant boundaries.

How can Laravel ITSM integrate with SIEM?

By exposing an authenticated API or webhook that receives alerts, validating and normalising them, deduplicating repeats, and creating or updating incident tickets according to routing rules.

What security controls should an ITSM system include?

Strong authentication with SSO and MFA, role- and record-level authorisation, input validation, secure file handling, encryption, rate limiting, audit logging and careful handling of sensitive data.

Conclusion

Building ITSM in Laravel is very achievable, and the framework handles much of the plumbing. The hard parts are domain design: clear ticket types and transitions, an SLA engine that handles real-world calendars and pauses, and authorisation that keeps sensitive tickets private. Get those right, test them thoroughly, and you have a platform that fits your organisation instead of the other way round. For the bigger picture, start with What is ITSM?

Build your ITSM platform with Tarsoft

Tarsoft builds Laravel systems for Malaysian organisations, and our engineers teach Laravel too. If you are considering custom ITSM development or extending Tarsoft Care, talk to our team. Government agencies can request a quotation directly.

References

  • #Laravel
  • #ITSM
  • #IT Service Management
  • #Software Architecture
  • #Malaysia

← All articles

WhatsApp

What can we help with?

Answer two quick questions so the right person replies with what you need.

Topic

We reply Mon–Fri 9am – 6pm and Sat 9am – 12pm.