Skip to content
APFerrer
P-DAT-03 · ProductCross-industry (transport and logistics, services, operations)

SLA and internal deadline monitoring with evidence for every result

Turns commitments such as "we respond within 4 business hours" into deadlines that are checked automatically against your systems' data, with their financial impact and stored evidence for every result.

Source codeExclusivity availableInstalledOEM

Most companies have internal commitments like "we answer an incident within 4 business hours" or "every quote goes out within 48 hours". Very few measure them with objective data. This SLA compliance monitoring software turns each commitment into a deadline that checks itself against what your systems already record: email, calendar, shared spreadsheets or your management software. Every result is stored with the evidence that supports it and the amount of money at stake.

Who it is for

  • Operations managers who want to know which deadlines are met, which are not and what each delay costs.
  • Internal audit and compliance teams that need results anyone can review and reproduce.
  • Transport, logistics and service companies whose processes run through email, calendars or their management software.
  • Integrators that want to offer their clients a compliance monitoring service.

What SLA compliance monitoring solves

  • Deadlines nobody measures. You define when each deadline starts and ends, and whether it counts calendar days or business days, using your own holiday calendar.
  • Breaches that were not breaches. If a system was down, the result is marked "no evidence" instead of counting as a breach. If the evidence arrives late but is dated within the deadline, the result is corrected.
  • Arguments about the data. Each result keeps the original record that supports it, and that record cannot be modified.
  • Hidden cost. Each evaluation calculates the amount at stake in its own currency.

What you can do with it

  • Create obligations in an editor or from a sentence ("urgent incidents are answered within 2 business hours"). The system proposes the rule and you review it before saving.
  • Start from a library of templates for common obligations.
  • Follow each deadline through these states: in progress, met, documented exception, no evidence or breached. States can be justified and reviewed by an auditor.
  • Read the reason for each result in plain language, with the technical detail kept separate for whoever needs it.
  • Manage findings by severity, follow them up with notes that cannot be deleted and open cases.
  • Organize the company by departments, roles and teams, synchronized with your directory.
  • Receive email alerts, check indicators and generate PDF reports with an executive summary.
  • Ask questions in natural language about stalled cases, outstanding amounts, delays by process or workload by department.
  • Serve several companies from a single installation, with each company's data kept separate.
  • Decide how much is read from each source: metadata only, or the content too. Reading content requires a recorded authorization.

Benefits

  • You move from opinions to data: you know what is met, what is not and why.
  • You prioritize by financial impact, not by who complains the loudest.
  • You arrive at an audit with the evidence for every result already stored.
  • You avoid unfair internal penalties: if the cause was a system outage, it is on record.

Industry context

General industry data with its public source. These are not results of this product.

  • More than 90% of mid-sized and large companies estimate that a single hour of downtime costs them over USD 300,000, and 41% put it at between USD 1 million and more than USD 5 million. Source: ITIC, "ITIC 2024 Hourly Cost of Downtime Report Part 1", September 2024 (survey of more than 1,000 companies worldwide).

What you get with each license

Price upon request, depending on license type and scope. Maintenance and support are contracted separately for every license type.

  • The complete source code, to adapt it to your processes and data sources.
  • Installation and configuration documentation.
  • A technical handover session with your team.
  • A warranty against defects for the agreed period.

Technical specifications

Language and runtime: TypeScript 5.9 on Node.js. Minimum supported version: Node.js 20.19 (required by Prisma 7 and other dependencies).

Frameworks: Next.js 16.4 and React 19.3, with Prisma 7.10 as the ORM and Tailwind CSS 4.3.

Database: PostgreSQL. Minimum supported version: 16 (it uses role-switching permissions introduced in PostgreSQL 16).

Operating systems: A server with Node.js.

Interface languages: Spanish.

Required infrastructure:

  • PostgreSQL 16 or later.
  • A scheduled task that runs the reading of sources and the evaluation of deadlines every hour.
  • An SMTP server for alerts.
  • Amazon S3-compatible storage with Object Lock, optional, to keep the evidence outside the database (if it is an external service, it requires the buyer's own account).
  • For Google Workspace, a Google Cloud project with a service account and domain-wide delegation (requires the buyer's own account).
  • For Notion, a Notion integration (requires the buyer's own account).
  • An AI provider with the Anthropic API or an OpenAI-compatible API, optional (requires the buyer's own account).
  • Sentry for error logging, optional (requires the buyer's own account).

Private deployment: It can run on its own in your infrastructure with sources that arrive by webhook or through CSV and Excel imports. The Google Workspace and Notion connectors need a connection to those services. AI is optional.

Main libraries:

Library Version License
next 16.4.6 MIT
react 19.3.0 MIT
@prisma/client and @prisma/adapter-pg 7.10.1 Apache-2.0
pg 8.23.1 MIT
next-auth 5 ISC
@auth/prisma-adapter 2.11.3 ISC
bcryptjs 3.0.3 BSD-3-Clause
@react-pdf/renderer 4.9.0 MIT
pdf-lib 1.17.1 MIT
@aws-sdk/client-s3 3.1165.0 Apache-2.0
nodemailer 7.0.13 MIT-0
zod 4.6.7 MIT

Dependencies with specific license terms:

  • @img/sharp-libvips-* 1.3.4 (libvips binaries used by sharp 0.35.5, an optional dependency of Next.js): LGPL-3.0-or-later. The @img/sharp-win32-* and @img/sharp-wasm32 0.35.5 packages: Apache-2.0 AND LGPL-3.0-or-later.
  • lightningcss 1.33 (and its per-platform binaries): MPL-2.0, build time only.

Compatibility and integrations: Google Workspace: Admin SDK Directory API v1 and Reports API v1, Gmail API v1, Google Calendar API v3, Google Drive API v3, Google Sheets API v4 and Google Meet API v2; Notion API (version 2025-09-03); Anthropic Messages API (version 2023-06-01) and OpenAI-compatible API (v1); Amazon S3 with Object Lock in compliance mode and compatible services; HTTP webhooks; CSV and Excel import (Visual Trans exports and Vodafone One Net call logs); SMTP email.

Redistribution terms

The asset's own code can be integrated into the licensee's commercial products under the source code license, the exclusive license by sector or territory and the OEM license, on the terms of the contract. With the installed license, the software is used and not redistributed. The libvips binaries used by sharp (LGPL-3.0-or-later) and lightningcss (MPL-2.0, build time only) have specific license terms, as listed under Technical specifications.

Installation requirements

Installed on your server or in your cloud, with a PostgreSQL database. If you want to keep the evidence outside the database, you can use Amazon S3-compatible storage with a deletion lock. To read Google Workspace, the domain administrator has to authorize access. AI is optional and works with your own provider's key.

Integrations

Google Workspace (directory, Gmail, Calendar, Drive, Sheets, Meet and audit logs), Notion, Visual Trans exports in CSV or Excel, Vodafone One Net call logs, webhooks for your own software, Amazon S3, AI providers with your own key and SMTP email.

FAQ

Frequently asked questions

  • Does the AI decide whether a deadline was missed?

    No. The result is calculated with fixed rules on dates and verifiable records. The AI only helps draft rules and answer questions.

  • What happens if one of our systems was down?

    That period is recorded, and the affected deadlines show as "no evidence", not as breached.

  • Does the evidence stand up legally?

    The original record is stored in a way that prevents it from being modified or deleted. That makes it strong technical evidence, but it does not replace a qualified timestamp or an expert witness report.

  • Can it connect to our management software?

    Yes, by webhook or by importing CSV or Excel exports. If your system is not on the list, a connector can be added.

  • Do we have to inform our staff?

    If the deadlines relate to identifiable people, yes. Under the GDPR, the company has to inform them, justify that the measure is proportionate and consider a data protection impact assessment. The system lets you read only the level of detail each obligation needs.

  • Is maintenance included?

    No. Maintenance (updates and bug fixes) and support (questions, training and adaptations) are contracted separately.

Request

Request information on P-DAT-03

Fill in the form with the asset reference and the license type you're considering. I reply in writing. If you need to review code, tick the NDA box and we'll sign one before anything is shared.

Controller: APFerrer. Purpose: to answer your request. You can exercise your rights as described in the privacy policy.

Price upon request, depending on license type and scope. Maintenance and support are contracted separately.