MERIDIAN
Enterprise ITSM Built for Municipal Operations
MERIDIAN is a full-stack IT service management and asset-operations platform for teams that need modern service delivery, operational traceability, and AI that stays behind a governed server boundary.
52
API Routes
111
Database Tables
278+
RLS Policies
AI
Governed Delivery
Core Capabilities
Built for organizations that need more than a ticket queue and less risk than a pile of disconnected admin tools.
Incident Management
AI-assisted intake, SLA-aware triage, assignment support, and workflow visibility for service teams running real operational volume.
Asset Management
Lifecycle tracking, assignments, maintenance history, and asset context that extends beyond a simple inventory list.
Change Management
ITIL-style change workflows, approvals, and operational discipline for teams that need controlled delivery.
CMDB and Operations Data
Configuration relationships, dependency awareness, vendor records, contracts, and administrative context in one system of record.
Knowledge Base
Searchable self-service knowledge, markdown-backed articles, and support documentation linked to live operational work.
Reporting
Operational reporting across SLAs, technician throughput, backlog, assets, audits, and service health.
Platform Scope
- Unified operating surface for service desk, asset management, knowledge, reporting, notifications, and administration
- ITIL-style modules covering incidents, requests, changes, problems, service catalog, approvals, and CMDB
- Vendor, contract, announcement, and organizational-management workflows for broader IT operations
- Installable PWA delivery for distributed teams that still need fast mobile access and accountable work history
Target Organizations
- Municipal IT departments
- County IT operations
- Government technology teams
- Organizations replacing fragmented service and asset workflows
AI Capabilities
AI inside MERIDIAN is routed toward specific operational jobs instead of generic automation claims.
Triage and Routing
- Ticket categorization, priority suggestion, and likely duplicate detection
- Assignment recommendation based on category and workload context
- Sentiment and urgency interpretation for higher-risk incidents
Self-Service
- Conversational support patterns for common service requests
- Knowledge-base article suggestion during incident handling
- Auto-resolution evaluation against existing issue patterns
Knowledge and Resolution
- Resolution summaries and ticket-history compression for faster context
- Draft knowledge creation from resolved work
- Natural-language search support for users and technicians
Prediction and Review
- Escalation-awareness support for issues likely to get worse
- Operational-pattern interpretation from live work history
- Human-in-the-loop workflows for sensitive or privileged actions
AI Safety Architecture
MERIDIAN keeps model credentials and privileged action logic off the client. That matters when support automation touches governed workflows, file access, and user data.
- AI requests are routed through a secured server layer rather than exposing model credentials in the browser
- The acting user is authenticated before AI work is processed
- Role context is resolved server-side for privileged workflows instead of trusting client-supplied values
- Sensitive or destructive actions can require confirmation and leave an audit trail
Why This Matters
The point is not to sprinkle AI on top of service operations. It is to introduce assistance without weakening reviewability, role boundaries, or security posture.
Security Posture
- TOTP MFA with enrollment, verification, backup-code support, and administrative reset workflows
- Five-tier role model spanning end users through super-admin governance
- RLS-backed access patterns and storage segmentation for operational data and files
- Signed attachment URLs with one-hour expiry instead of permanent public links
- Security policy controls for passwords, lockout, sessions, MFA enforcement, and audit retention
Operational Control Surface
MERIDIAN is built so administrators can review sessions, audit logs, security settings, role assignments, and operational evidence from within the product.
Implementation Approach
MERIDIAN is suited to both greenfield rollout and structured replacement of fragmented tools. The rollout sequence is practical rather than ceremonial.
Phase 1
Discovery
Phase 2
Foundation
Phase 3
Data preparation
Phase 4
Workflow configuration
Phase 5
Pilot
Phase 6
Production launch
Phase 7
Hypercare
Rollout Stakeholders
- IT leadership and service-desk management
- Technicians and application owners
- Security and compliance stakeholders
- Platform admins responsible for production cutover
Related Proof
Start with the operating problem, not the software demo
MERIDIAN fits teams dealing with queue pressure, fragmented tooling, asset accountability, and governance concerns. The adjacent tools and case studies show the operating discipline behind the product.
Ready to Modernize Your IT Operations?
MERIDIAN is for teams that need service delivery, asset governance, and operational accountability in one place.