If you've ever stood up a service desk, you know the shape it needs: typed records (incidents, requests, assets), fields that mean something, queues, real permissions, and rules that push work forward. ServiceNow is very good at that shape — and it also deploys and prices like the enterprise platform it is. For a team of 5–50 people, renting a second platform just to run support is a heavy tax.
Here's the part that's easy to miss: that team already runs a permissioned, backed-up, CRUD platform every day. It's WordPress. What it lacks is the ITSM shape — and a low-code layer is exactly how you add it.
Give WordPress the shape
WP-PFManagement turns WordPress into a ServiceNow-style low-code platform. Without writing code you model typed entities (incident, request, asset), fields with real types, forms, lists and queues, row- and field-level permissions, and business rules that fire on change. Wire those together and you have a working service desk — incidents with an SLA field, a triage queue, an escalation rule — living in the wp-admin your team already opens every morning.
It's the ServiceNow idea (model your processes as data, ship apps on top) without the ServiceNow deployment: no second platform, no separate identity provider, no per-seat enterprise contract.
Why "on WordPress" is the feature
Because every ticket is a record in the same platform as the rest of your data, it composes with your stack instead of integrating with it:
- A WooCommerce order can open an incident directly — the order is a native event, not a connector poll.
- A visual workflow (the engine that ships beside the low-code platform) can watch incidents and act: escalate, notify, or hand a host-side job to an open-source Rust worker on your own machine.
- Permissions are real and enforced at the row and field level — agents see their queue, contractors see only their tickets, nobody sees a field they shouldn't.
And it's not only a service desk: the same platform now ships Agile project management (a Kanban board and a Gantt where each task's width is its duration) on the same records, so the work and the plan live in one place.
Where it runs, plainly
Everything is plugins on your own server: no external SaaS, no telemetry, your data never leaves your database. The low-code platform and the workflow engine are commercial — licensed per domain, not per seat, and refundable — and on sale now: register, buy and self-host today, and the purchase is the trial. The AI agent that can design the whole schema from a sentence, and the Rust worker that runs host-side jobs, are open source and free.
There's a worked end-to-end example — a WooCommerce order becoming a ticket, a workflow, an AI triage and a generated RMA file — at project-flash.com/use-case. Docs at /docs.
If your team already lives in WordPress, your service desk can live there too — typed, permissioned and automated, without renting a second platform to hold it.
Happy to answer anything about the permission model, how incidents compose with WooCommerce and workflows, or the per-domain licensing.
Top comments (0)