Logify

Logify Enterprise Service & Operations Management

Logify — One incident. Every team that works it. Every hour accounted for.

Logify is self-hosted service and operations ticketing for manufacturing plants and organizations where work crosses departments. One ticket can involve controls, IT, engineering and maintenance: each team states its responsibility, each person has their own assignment and records their own time, and production downtime is recorded separately from labor.

  • Runs on your own server
  • Several teams and people on one ticket
  • Labor in person-hours, apart from downtime
  • 28 permissions, editable roles
$4,995 Organizational license One-time purchase · no subscription
Logify ticket workspace: three participating teams with their responsibilities, three assigned people and required work assignments with a dependency (fictional demo data)
Logify 2.0.0 ticket workspace. Fictional demo plant, people and data.

Built for the incidents that need more than one team

When a line stops, the fix rarely belongs to one department. A PLC fault can need the controls team, IT for the network and engineering to validate the restart. When that work is spread across e-mails, phone calls and separate tickets, nobody can see who is doing what, and the hours spent get mixed up with how long production was down.

Logify keeps it in one ticket: a primary team and a coordinator, participating teams with a stated responsibility, individual work assignments with due dates and dependencies, and time recorded by each person. Labor is the sum of everyone's hours; ticket duration and production downtime are measured separately.

Logify is self-hosted: it runs on your own web server with PHP and MySQL or MariaDB, and your tickets, time and audit records stay in your database.

Designed for

Manufacturing plantsMaintenance, controls and engineering teamsIT service desks that support operationsOrganizations where work crosses departments

One incident, many separate tickets

One Logify ticket holds every participating team with its responsibility, the people assigned and a coordinator who keeps the work moving.

Closed before the work is done

Completing one assignment never closes the ticket. Your closure rule decides when it can be resolved, and an override needs a reason that is written to the audit log.

Labor confused with downtime

Labor is the sum of people's time entries. Production downtime comes from the outage start and end, and shows as unknown, not zero, until both are recorded.

No record of what was fixed

The location, equipment, root cause and corrective and preventive actions are recorded on the ticket, and repeat failures can be linked to earlier tickets.

What Logify solves for your business

When an incident crosses departments, the cost is not only the repair. It is the hours nobody can account for, the downtime nobody measured and the same failure coming back next month. Logify gives managers a record they can act on.

Clear ownership when production stops

Every team on an incident states its responsibility, every person has a named assignment and one coordinator keeps it moving. Nobody has to chase e-mails or phone calls to find out who is doing what.

Labor cost you can account for

Each person records their own time, so labor is reported in real person-hours by team, ticket, equipment or month, with cost visible only to the roles you allow. Budget and staffing discussions start from recorded hours, not estimates.

Downtime figures you can trust

Production downtime is calculated from the recorded outage start and end, never from labor or from how long a ticket stayed open. Downtime reports by location show where production is really lost.

Fewer repeat failures

Root cause, corrective and preventive actions are recorded on the ticket, and repeat failures are linked to earlier ones. Reports show which equipment and categories keep coming back, so improvement work goes where it pays.

Work that is finished before it is closed

Closure rules stop a ticket from being resolved while required work is still open. An override needs a reason, which is written to the audit log, so the record shows what was decided and by whom.

Your data stays on your network

Logify runs on your own server with your own database, and loads no external fonts or scripts, so it also works on isolated plant networks. Tickets, time and audit records never leave your infrastructure.

See Logify at work

Five demonstrations recorded from Logify 2.0.0: a product overview, a cross-team incident from report to resolution, administration, manufacturing operations and installation on Linux. Choose a video; nothing downloads until you press play.

Overview 1:16 Logify 2.0.0

Logify in 90 seconds

A tour of Logify 2.0.0: the operations dashboard and ticket queue, a cross-team incident with its work, time and operations tabs, the Labor & Time report, the production downtime report and the teams page.

5 videos · choose one below

Real screen recordings of Logify 2.0.0 with fictional demonstration data: the plant, its people and its equipment are invented. Captions only, no narration or audio. In the installation video, the terminal panels show command output captured from the Linux test server at the time of recording; they are not recordings of a terminal.

Cross-team incident management

Shared ticket ownership: every team and person involved works in the same ticket, with one consolidated history.

Participating teams, assigned people and a coordinator

A ticket has one primary team and one or more participating teams, each with a stated responsibility and its own "part complete" status. People are assigned on behalf of one of their teams, and one staff member can coordinate the ticket.

Adding a team notifies its leaders. A team with open work assignments, and the primary team, cannot be removed from the ticket.

Logify ticket workspace: three participating teams with their responsibilities, three assigned people and required work assignments with a dependency (fictional demo data)

Work assignments with dependencies

Each assignment has an assignee and a responsible team, a status, priority, due date, estimated effort, the actual time spent and whether it is required. An assignment can depend on another one on the same ticket and cannot start or finish before that work is done; circular dependencies are refused.

My Work lists a person's assignments across all of their teams.

Logify My Work page listing one person's work assignments across all of their teams (fictional demo data)

Closure rules you choose

Choose how tickets close: the coordinator decides, all required assignments complete (the default), a team manager closes, or the requester confirms, with optional auto-close after a set number of days. Set a default for the organization and override it per work type or per ticket.

Completing an assignment never closes the ticket. An authorized user can override a blocker by giving a reason, which is written to the ticket timeline and the audit log.

Logify Operations Settings with the closure rule and email settings (fictional demo data)

One conversation, with internal notes

Public replies and internal notes stay on the ticket, next to the timeline of team additions, assignments, time and status changes. Requesters never see internal notes, and team-only notes are visible only to members of the author's teams.

Logify ticket conversation for a production-line incident, with public replies and internal notes (fictional demo data)

Time and labor

Everyone who works a ticket records their own time. Logify adds people's hours together and never derives labor from how long a ticket was open.

Timers and manual entries

Start and stop a timer while you work, or add an entry in hours or minutes with a date, an assignment, a description and a billable flag. Each person can run one timer at a time, and a double-click or browser retry never creates a duplicate entry.

Three people working the same hour record three person-hours: labor is the sum of everyone's entries, kept separate from ticket duration and production downtime.

Logify ticket Time tab: 3.75 person-hours of labor by person and by team, the record-time form and time entries (fictional demo data)

Cost only for those allowed, corrections with history

Each entry stores the person's labor rate at that moment, so a later rate change never rewrites past cost. Cost is shown only to roles with the cost permission, and is labelled partial when some entries have no rate.

The Labor & Time report groups hours by person, team, ticket, facility, category, work type, project, equipment or month, with billable hours, recurring problems, CSV export and print. Correcting someone else's entry needs permission and a reason, and every change is kept as a revision.

Logify Labor & Time report grouped by team, with billable hours, labor cost and recurring problems (fictional demo data)

Made for manufacturing operations

Logify records who worked on a problem, where, on which equipment, what it cost in labor and what it cost production. It is not a maintenance management system (CMMS): there are no preventive-maintenance schedules, meter readings or spare-parts inventory.

Facility hierarchy

Site, building, area, line and cell. Reports roll tickets and labor up to any level.

Equipment register

Assets with tag, type, manufacturer, model, serial number, facility, owning team and status. Tickets reference the equipment involved, and a report shows which machines have the most incidents.

Production impact and downtime

Mark a ticket as production-impacting, estimate the downtime and record the outage start and end. Downtime is calculated from those times, separately from labor and ticket duration.

Root cause and actions

Record the root cause, the corrective action that restored production and the preventive action that should stop it happening again.

Recurring problems

Link a ticket as a recurrence of an earlier one, and find repeat categories and equipment in the recurring-incidents and Labor & Time reports.

Work types and custom fields

Define work types such as breakdown, quality hold or changeover support, each with its own closure rule, production-impact tracking and custom fields.

Administration, teams, roles and security

Ticket access is decided on the server for every page and action. Security testing to date is internal; Logify has not had an external penetration test or an independent audit, and holds no certifications.

Teams defined by your administrators

No department is hard-coded. People can belong to several teams; each team has leaders and managers, routing, an optional inbound mailbox, business hours and escalation, and can be archived with its history kept.

Roles and granular permissions

Seven seeded roles, from System Administrator to Read-Only Auditor and Requester, built from 26 permissions. Copy a role or create your own; the editor refuses any change that would leave nobody able to manage roles and settings.

Team-scoped access and confidential tickets

Team membership grants access only to tickets that team participates in. Confidential tickets are limited to participants, leaders of participating teams and users with the confidential-ticket permission.

Email to ticket

Incoming mail becomes tickets through POP3 or an MTA pipe. A reply joins a ticket only with an HMAC-signed message reference and an authorized sender. Outgoing mail is queued and sent through your SMTP server, with retries.

SLA, automation, knowledge base and reports

SLA warnings, breaches and team escalations; automation rules with loop protection and a run log; a knowledge base; 16 reports plus Labor & Time, each limited to what the user may see, with CSV export and print.

Secure installation and defaults

A web installer that needs a setup token from the server and locks itself afterwards. Then CSRF protection, parameterized SQL, output escaping, upload validation, session hardening, HSTS and Content-Security-Policy headers, and an audit log.

Inside Logify

Screens from Logify 2.0.0 with a fictional demo plant, people and data. Select an image to view it full size.

Connect your ERP, phones and Teams

Logify 2.1 connects to the systems your plant already uses. Events from them create, update and route tickets through rules you define. Integrations are configured in Logify's administration and are included in the license at no extra charge. Each connector is tested against the provider's documented API; validation with your own provider account is part of setup. Your provider subscriptions and permissions are required.

Microsoft Dynamics 365 Business Central

Reads items, vendors, locations and other data through the Business Central API, with real-time change notifications. Low inventory can open a Purchasing ticket. Maintenance work orders and equipment come from your extension's custom API. Optional write-back of ticket status to linked records is off by default.

Dynamics 365 Finance and Supply Chain

Synchronizes the work-order and asset data entities you choose, for your legal entity, and receives business events. Work orders become or update tickets; optional, field-limited write-back. Postings, journals and inventory are never written.

RingCentral phone-to-ticket

Calls to your support queues become tickets: every call, missed calls, voicemail, or only when a rule matches. Each call creates exactly one ticket with the caller, queue, time and duration, and the caller is identified from your directory. Agents can also create a ticket from any recorded call.

Microsoft Teams

Employees report problems from a form in Teams and get the ticket number back. They can check status, see the work assigned to them and comment, all with their own Logify permissions. Logify sends assignment, escalation and completion notifications. The app reads only messages sent to it.

Automated incident routing

Rules turn events into action: when a missed call reaches the IT queue after hours, or a line-down event arrives, Logify creates the ticket, sets priority, adds teams, assigns people, attaches the equipment and notifies the right group. Test any rule against a sample event before you enable it.

Cross-department response

One event can involve Controls, IT, Engineering and Maintenance on the same ticket. Each team gets its own work assignment, and each person records their own time, exactly like tickets created inside Logify.

ERP-linked equipment and work orders

Map ERP equipment to Logify assets once. Tickets from work orders and equipment events then carry the asset and its location, and keep a link back to the ERP record. A second event for the same record updates the open ticket instead of creating a duplicate.

Secure configuration

Credentials are encrypted on your server and never shown again after entry. Every inbound request is verified with the provider's signature or token, and outbound connections are restricted to approved destinations. Each integration is bound to your tenant or company, and every change is audited.

Under your control, on your servers

Integrations run inside your self-hosted Logify: no cloud relay, no vendor connection. Events wait in a queue and are retried if a provider is unavailable, so an outage never takes Logify down. Slack, Zoom Phone, Twilio and signed webhooks are also supported.

How Logify is deployed

Logify runs on infrastructure you control. There is no Logify cloud service, and your data stays in your own database.

1. Your web server

A PHP 8.1 or later web application on Apache 2.4, tested on Debian 13 Linux. No Docker, Node.js or Composer is needed.

2. Your database

One empty MySQL 8.0+ or MariaDB 10.6+ database, with privileges on that database only.

3. Web installer

Enter the setup token from the server. The installer checks every requirement, creates the database schema and the first administrator, then locks itself.

4. Background jobs

A scheduled task runs the Logify job every 1 to 5 minutes for email, SLA warnings, escalations and auto-close.

5. Email (optional)

Your SMTP server for outgoing mail; a POP3 mailbox or an MTA pipe for incoming mail.

Technical requirements

Tested configurations are named; other configurations are supported but untested.

Technical requirements
Server operating systemLinux with Apache 2.4 (tested on Debian 13). Other systems that run PHP 8.1+ and Apache 2.4, such as Windows Server, are supported but untested.
PHPPHP 8.1 or later (tested on 8.3) with pdo_mysql, mysqli, mbstring, json, openssl, sodium, fileinfo, curl and iconv. The installer checks each requirement and refuses to continue if one is missing.
DatabaseMySQL 8.0+ or MariaDB 10.6+ with InnoDB and utf8mb4 (tested on MySQL 8.0.46, MariaDB 10.11 and MariaDB 12.3). One empty database for a new installation.
Web serverApache 2.4 with mod_rewrite and mod_headers, over HTTPS (tested). nginx and IIS are untested.
SchedulerCron or Task Scheduler running the background job every 1 to 5 minutes.
EmailOutgoing: an SMTP server (STARTTLS, TLS or an internal relay). Incoming: POP3 or an MTA pipe. Tested against SMTP and POP3 servers in our test lab. Microsoft 365 and Gmail have not been tested, and OAuth2 mail sign-in is not supported.
BrowsersCurrent Chrome, Edge, Firefox or Safari, in light and dark themes; layouts tested from desktop down to phone width. Internet Explorer is not supported.
SizingNo load test has been done, so no capacity is stated. A small virtual server (2 vCPU, 4 GB RAM) is a reasonable starting point for a single plant.
Not includedNo single sign-on (SSO, SAML, OIDC), no multi-factor authentication, no OAuth2 for mail, no mobile apps and no hosted (cloud) edition. No maintenance management (CMMS) features: no preventive-maintenance schedules, meter readings or spare parts. No live co-editing: two people editing the same ticket get a conflict message and reload.
LicensingPerpetual license for one organization, with 12 months of technical support and software updates included. Optional Annual Support & Updates afterwards; optional Professional Installation. Activated offline with a signed license certificate from your account. The license does not limit the number of users, teams or tickets.

Pricing & licensing

Pricing and licensing

A one-time license for one organization. You pay once, and the license never expires: Logify keeps working on your server whether or not you renew support.

The first 12 months of technical support and software updates are included. After that, Annual Support & Updates is optional: buy it when you want support and new versions, and it is never charged automatically. Professional Installation is an optional one-time service.

Logify is self-hosted on servers your organization controls, and it is activated with a signed license certificate that works without an internet connection.

  • Perpetual license for one organization
  • 12 months of support and updates included
  • Self-hosted, activated offline
  • No user or team count limit in the license

Additional Organization License

A perpetual license for another organization, such as a subsidiary or a separate legal entity. Requires an existing Logify license.

$3,495 one-time, USD · perpetual license

12 months of technical support and 12 months of software updates included. The license stays valid after they end.

  • One more licensed organization
  • 12 months of technical support and software updates
  • Its own signed license certificate

For customers who already hold a Logify license

After the first year, support and new versions are optional: $999 / year, bought only when you choose and never charged automatically.

Buy Additional Organization License — $3,495

Optional services

Annual Support & Updates

Twelve more months of technical support and new Logify versions for one license. Optional: bought only when you choose and never renewed automatically.

$999per year of support, USD · one-time payment, never renewed automatically
  • 12 months of technical support
  • New Logify versions released during the 12 months
  • Added to the end of your current support period
Buy Annual Support & Updates — $999

Professional Installation

One remote installation of Logify on a server you provide, done with your administrator. Requires a Logify license.

$750one-time, USD · per installation
  • Remote session with your administrator
  • Installation, first administrator and scheduled job
  • Email settings test and license activation
  • Handover of the administration basics
Buy Professional Installation — $750

Secure, encrypted card payment. License issued automatically after payment is confirmed.

Prices are in US dollars. A license covers one organization: its own servers, such as production, test and recovery, and its own users. Versions released after your updates end need a renewal; the version you have keeps working. Integrations are included in the license at no extra charge; providers such as Microsoft or RingCentral may require their own subscriptions or API access.

Frequently asked questions

Can I buy Logify today?

Yes. Choose "Buy Logify", review the price and pay by card through our secure checkout. As soon as the payment is confirmed, your license, the license certificate and the Logify download are in your account under Licenses & downloads. Professional Installation and Annual Support & Updates can be added from the same account at any time.

What does the license include?

A perpetual license for one organization to use every Logify feature, including the integrations in Logify 2.1, on servers it controls, with 12 months of technical support and software updates. The license does not limit the number of users, teams, tickets or servers within that organization. A second organization, such as a subsidiary that is a separate legal entity, needs an Additional Organization License.

What happens when support ends?

Logify keeps working: the license is perpetual and does not depend on support. Versions released after your updates end are not covered until you renew. Annual Support & Updates is optional, adds 12 months of support and updates, and is never charged automatically.

Does activation need an internet connection?

No. Download your signed license certificate from your account and import it in Logify under Administration › License. Logify checks the certificate on your server and never contacts us to keep working. If the license is missing or invalid, Logify switches to read-only mode: your data stays available and nothing is deleted.

Is Logify a cloud service?

No. Logify is self-hosted: you install it on your own web server (PHP with MySQL or MariaDB, on Apache) and your data stays in your own database. There is no hosted edition.

What do I need to run it?

PHP 8.1 or later with common extensions, MySQL 8.0+ or MariaDB 10.6+, Apache 2.4 with HTTPS, and a scheduled task for the background jobs. It was tested on Debian 13 with PHP 8.3, MySQL 8.0 and MariaDB 10.11. nginx and IIS are untested. No Docker, Node.js or Composer is needed.

How do several teams work on one ticket?

Each ticket has a primary team, a coordinator and the participating teams, each with a stated responsibility. People get individual work assignments with due dates, estimates and dependencies. Completing an assignment never closes the ticket; your closure rule decides when it can be resolved.

How is labor calculated?

Labor is the sum of every person's time entries, in person-hours: three people working the same hour record three person-hours. Labor is never calculated from how long the ticket was open or from production downtime; those are measured separately.

Who can see labor cost?

Only roles with the cost permission. Each time entry stores the person's labor rate when it was recorded, so changing a rate never rewrites past cost. When some entries have no rate, the cost is shown as partial.

Is Logify a maintenance management system (CMMS)?

No. Logify records incidents, the equipment and location involved, labor, production downtime, root cause and corrective actions. It has no preventive-maintenance schedules, meter readings or spare-parts inventory.

Does it work with email?

Yes. Incoming mail becomes tickets through POP3 polling or an MTA pipe, and replies are matched by a signed message reference and an authorized sender. Outgoing mail is queued and sent through your SMTP server with retries. It was tested against SMTP and POP3 servers in our test lab; Microsoft 365 and Gmail have not been tested, and OAuth2 is not supported.

Does Logify support single sign-on or multi-factor authentication?

Not in this release: there is no single sign-on (SSO, SAML or OIDC) and no multi-factor authentication. Users sign in with a password of at least 12 characters, and accounts lock after repeated failed sign-ins.

Is there a mobile app?

No. Logify is a web application. Its layouts adapt to tablets and phones in current browsers.

How many tickets or users can it handle?

We have not load-tested Logify, so we do not state a capacity. Its queries are indexed and paginated, and a small virtual server (2 vCPU, 4 GB RAM) is a reasonable starting point for a single plant.

Has Logify been independently tested or certified?

Not yet. Security testing so far is internal: automated HTTP security tests and integration tests on Linux with Apache, MySQL 8 and MariaDB. There has been no external penetration test or independent audit, and Logify holds no certifications.

Which systems does Logify 2.1 integrate with?

Built-in connectors: Microsoft Dynamics 365 Business Central, Dynamics 365 Finance and Supply Chain Management, Microsoft Teams, RingCentral, Zoom Phone, Twilio Voice and Slack. Generic options: signed inbound and outbound webhooks, and a read-only REST connector. Email-to-ticket remains built in.

Do the integrations cost extra?

No. The integrations are included in the Logify license at no additional charge, and there are no connector subscriptions. Each provider may require its own subscription, API access or licensing, for example Microsoft 365 and Azure for the Teams bot, a Dynamics 365 license, or a RingCentral plan with API access. Those are between you and the provider.

Have the integrations been tested with real provider accounts?

Each connector is tested against the provider's documented API: authentication, signatures, events and responses, in automated tests and end to end on Linux with Apache. They have not yet been validated against live Microsoft, RingCentral, Zoom, Twilio or Slack accounts. We validate each connection with your account during setup, and the configuration page tests every connection before it can be enabled.

Does Logify integrate with SAP, Oracle, Epicor or Infor?

Not natively. Systems without a built-in connector can send events to Logify through the signed webhook, or Logify can read a JSON API with the REST connector. Neither is a native integration, and we do not claim support for those products.

Can Logify change data in my ERP?

Only if you allow it. Write-back is off by default. When enabled, Logify updates only the fields you list, such as status or a ticket reference, on records linked to a ticket. Financial postings, journals, inventory and production data are never written, and Logify never creates or deletes ERP records.

Does Logify need to be reachable from the internet?

For real-time events from Teams, RingCentral, Zoom, Twilio, Slack and Business Central, yes: those providers call Logify over HTTPS. Business Central and Finance and Operations synchronization, the RingCentral call log and the REST connector work from a private network, with a delay of a few minutes.

Information and support

Questions about Logify, its release or how it would fit your teams? Send us a message and we will reply by e-mail.

Installer download available After payment is confirmed, the installer and your license key appear under Licenses & downloads in your account.

Bring every team on an incident into one ticket.

Buy Logify online and install it on your own server, or tell us about your plant and your teams and we will help you plan the installation.