Skip to content
APFerrer
P-SRV-01 · ProductSoftware and IT services

Support and UAT portal for software companies

A support console for software companies with several products: tickets from a widget inside your applications, by API or by email, customer companies with prepaid hour banks, announcements, user acceptance testing (UAT) with a full trail, manuals and specifications shared by link, and a weekly report.

Source codeExclusivity availableInstalledOEM

A company that builds software for several customers ends up with support spread across emails, chat messages and timesheets, and with acceptance tests in documents nobody knows who has reviewed. This portal works as a help desk for software companies and brings into one console the tickets that arrive from a widget inside each application, by API or by email. It organizes your customers into companies with their prepaid hour banks, sends service announcements and manages user acceptance testing (UAT), manuals and specifications through a link that records who has read and validated what.

Who it is for

  • Custom software companies that maintain several applications for different customers.
  • Software vendors with several products that want a single point of support for their team.
  • Consultancies that offer prepaid support hours and need to justify how they are used.
  • Product teams that validate deliveries with the customer's users and want a record of every test.

What a support and UAT portal for software companies solves

  • Scattered support. Every request comes into the same console, with its product, its company and its history.
  • Hours pieced together at month end. Time spent is logged against each ticket and deducted from the contracted hour bank.
  • UAT with no record. Each test case is marked with who tested it, when and with what result.
  • Documentation nobody knows has been read. Manuals and specifications are shared by link and record reads, ratings and questions.

What you can do with it

  • Register your products with their keys: a public one for the widget, a secret one for your server and another for each customer's dedicated installation.
  • Receive tickets from a widget embedded in your React applications, with its own styles and the user already identified by your server.
  • Create tickets, messages, users, attachments, announcements and hours from your systems through the API.
  • Receive requests by email: replies are threaded into the right ticket and auto-replies are discarded.
  • Work in an inbox with each ticket's thread, statuses, priorities, types, topics per product and attachments, with optional real-time updates.
  • Send acknowledgments and reply by email from the console.
  • Notify the source application with signed webhooks when there is a new ticket, a new message, or a change of status or priority.
  • Check metrics by period: volume, times, and distribution by hour and day.
  • Organize your customers into companies with their users, tickets, installations, announcements and hour banks, and pull the hours report by period, product and company.
  • Send service notices to the users of a company, a product, one or several installations, or everyone, with a record of each send.
  • Share acceptance tests by link: the tester identifies themselves, marks each case as passed, failed or unclear and opens issues.
  • Get the UAT status by email every week.
  • Publish manuals by link with a record of reads, ratings and reader questions.
  • Keep software requirements specifications (SRS) with versions, identified access and a record of PDF exports.
  • Give a coding assistant API access to tickets, UAT, manuals, specifications, topics and announcements.
  • Work with owner and agent profiles, with an audit log.

Benefits

  • You justify every support hour with a report by company and product.
  • You close UAT knowing what was tested, who did it and what failed.
  • Your applications know what is happening with their users' tickets.
  • You tell only the affected users about downtime and updates.

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 portal installed on your server or in your cloud, under a license to use.
  • Initial setup of your products, inbound and outbound email, and the weekly report.
  • Initial training for administrators.

Technical specifications

Language and runtime: TypeScript 5.9 on Node.js. Minimum supported version: Node.js 20.19 (the one Prisma 7 requires).

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

Database: PostgreSQL.

Operating systems: A server with Node.js.

Interface languages: Spanish.

Required infrastructure:

  • PostgreSQL.
  • An SMTP server for outgoing email.
  • Postmark for inbound email (requires your own account).
  • Pusher for real-time updates, optional (requires your own account).
  • A weekly scheduled task for the report.

Private deployment: Can run on your infrastructure, except for receiving email, which needs Postmark. Real-time updates with Pusher are optional.

Main libraries:

Library Version License
next 16.4.2 MIT
react 19.2.4 MIT
@prisma/client and @prisma/adapter-pg 7.10.1 Apache-2.0
pg 8.22.0 MIT
next-auth 5 ISC
argon2 0.45.1 MIT
jose 6.2.4 MIT
nodemailer 10.2.1 MIT-0
pusher and pusher-js 5.3.4 and 8.6.0 MIT
@tanstack/react-query 5.101.4 MIT
react-hook-form 7.82.0 MIT
zod 4.4.3 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.

Compatibility and integrations: Postmark Inbound (inbound email webhook); SMTP email; Pusher Channels; outgoing webhooks signed with HMAC-SHA256; the widget as a React component for your applications; a REST API to create tickets and query data from your applications.

Redistribution terms

The asset's own code can be embedded in 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. Specific license terms apply to the libvips binaries that sharp uses (LGPL-3.0-or-later), as listed in the Technical specifications.

Installation requirements

Installed on your server or in your cloud, with a PostgreSQL database. Sending email needs an SMTP server, and receiving it needs a Postmark account. The weekly report needs a scheduled task. Real-time updates are optional and use a Pusher account. The widget plugs into React applications.

Integrations

Postmark for inbound email, SMTP for outgoing email, Pusher for real-time updates and signed webhooks to each product's applications.

FAQ

Frequently asked questions

  • How does the widget fit into my application?

    You add the component with the product's public key. For the user to arrive already identified, your server signs their identity and passes it to the widget.

  • Can I receive tickets by email?

    Yes. Emails sent to the support address become tickets, or are added to the thread if they are a reply.

  • How are hour banks controlled?

    Each company has its contracted hour banks, and your team logs the time spent on each ticket. The report filters by period, product and company.

  • What does the UAT part add compared with a spreadsheet?

    The tester comes in through a link and identifies themselves, and every result is recorded with who and when, together with the issues and a weekly report.

  • Does it have built-in AI?

    It does not include an AI model. It offers an API so your team's coding assistant can query and update tickets and documentation.

  • Is maintenance included?

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

Request

Request information on P-SRV-01

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.