Jump to content

Recommended Posts

Posted

Hi everyone,

I’m happy to share the first public release of Kontor, an open-source modular ERP, CRM and business operations platform built natively for ProcessWire.

Kontor

Kontor is not intended to turn ProcessWire into one rigid business application. The goal is to provide reusable business components that can be combined according to the needs of a particular website or organization.

Business software should become part of the ProcessWire site, rather than forcing the site to become part of a separate business platform.

Kontor 1.0.0 contains 35 components. They share one audited core, one organization model and one permission-aware admin workspace, while remaining separately installable.

Customers and revenue

  • Contacts — contacts, companies, addresses, company memberships, tags, duplicate detection and import/export foundations.
  • CRM Intake — configurable qualification forms for contacts, leads and deals, including required fields, validation rules and field bindings.
  • CRM — leads, pipelines, stages, deals, lead-to-deal conversion, Kanban data and pipeline reporting.
  • Catalog — products and services, categories, price lists, price entries, units of measure and tax-code references.
  • Sales — quotations, orders, shared document lines, status workflows and quotation-to-order conversion.
  • Invoices — invoices, numbering, issue workflow, overdue state, credit-note foundations and order-to-invoice conversion.
  • Payments — payments, invoice allocations, partial payments, reversals and idempotent provider-integration boundaries.

Finance and localization

  • Ledger — double-entry accounting foundations, chart of accounts, journal entries, ledger lines and balances.
  • Germany — German localization contracts, chart-of-accounts support and country-specific business-document formatting.

Operations and project work

  • Inventory — warehouses, balances, stock movements, reservations, transfers and barcode support.
  • Purchasing — suppliers, purchase orders, receipts, receipt lines and inventory integration for received goods.
  • Expenses — expense categories, expenses, receipt associations and approval workflows.
  • Projects — projects, milestones, time tracking, billable items and invoice integration.
  • Tasks — tasks, reminders, recurrence, calendar-oriented data and links to business entities.

Collaboration, content and customer access

  • Collaboration — notes, threaded comments, mentions, followers, notifications and unread state.
  • Dashboard — widget registry, personal dashboards, role dashboards and configurable layouts.
  • Reports — report-provider registry, report builder, charts, exports, scheduled reports and queued delivery.
  • Documents — versioned document templates, HTML/PDF rendering, multilingual output and immutable issued-document snapshots.
  • Files — private local storage, file metadata, signed temporary URLs, versions and a provider contract for external storage adapters.
  • Mail — outbound history, inbound adapter contracts, shared mailboxes and links between messages and business entities.
  • Portal — customer authentication, quotations, invoices, payments, files, signed downloads and profile access for self-service workflows.

Platform, extensibility and integrations

  • SDK — shared contracts, DTOs, event envelopes and value objects, plus conventions and scaffolding tools for new components.
  • Workflow — a reusable state-machine engine with definitions, transitions, permissions, approvals and immutable history.
  • Automation — event-driven rules with triggers, conditions, actions, dry runs, execution logs and recursion protection.
  • Queue — asynchronous and delayed jobs, priorities, retries, progress, a dead-letter queue, handler registry and CLI worker.
  • Cache — namespaced cache access, tag-based invalidation, an in-memory implementation, a ProcessWire adapter and an optional Redis adapter.
  • Search — federated global search, provider and indexer registries, SQL full-text support and asynchronous indexing.
  • Settings — versioned, secret-free workspace settings export, validation, preview and controlled import.
  • Custom Entities — an entity builder with configurable fields, relations, views, permissions and optional API exposure.
  • Marketplace — official and custom component registries, package metadata, publisher trust, security advisories and installability checks.
  • API — bearer-token authentication, organization-scoped CRUD resources, filtering, field projection, OpenAPI, webhooks and idempotency at /api/kontor/v1/.
  • GraphQL — a component-aware schema registry, query execution, permission enforcement and complexity limits at /graphql.
  • MCP — 13 scoped tools for status, discovery, search, record operations, settings migration and API description, with permission and idempotency boundaries.
  • AI — a provider-neutral layer for summaries, drafting and structured extraction, with previews and approval boundaries before sensitive actions.
  • Demo — a connected order-to-cash reference scenario spanning Contacts, CRM, Catalog, Workflow, Sales, Projects, Files, Mail, Invoices, Ledger and Payments.

Core and admin workspace

The root Kontor module provides the shared service container, organization model, component and capability registries, migrations, audit log, backup and recovery, health checks, import/export and dependency management.

ProcessKontor provides the unified ProcessWire admin workspace. Navigation is assembled from the components that are actually installed and the permissions available to the current user.

Kontor uses ProcessWire modules, permissions, hooks and the admin interface. It does not replace ProcessWire’s frontend model. The site profile remains responsible for public templates, presentation, routing choices and project-specific composition.

A project can install only the components required by its Blueprint. Supported public PHP methods and integration boundaries are documented in API.md; internal ProcessKontor admin handlers are not treated as a public site API.

Current status

This is version 1.0.0 and the first public release. I still recommend treating it as a testing release until it has received feedback from more ProcessWire installations, database configurations and hosting environments.

The release-candidate programme currently includes:

  • all 35 components installed and enabled together on a real ProcessWire site;
  • 1,279 automated tests and 4,939 assertions in the documented release-candidate run;
  • package-level unit, integration, migration and contract coverage;
  • installation, historical upgrade, uninstall and reinstall testing;
  • verification that ordinary uninstall preserves business data;
  • permission, role and organization-boundary testing;
  • browser journeys for CRM qualification and order-to-cash workflows;
  • desktop and mobile responsive checks;
  • accessibility, keyboard, browser-console and failed-network checks;
  • REST, GraphQL, Settings and MCP contract coverage;
  • deterministic local substitutes for mail, payment, webhook, AI and object-storage providers.

Kontor is not presented as a certified accounting, tax or regulatory-compliance product. Country-specific rules, production-scale performance and real external providers must still be verified for each project.

Please install it first on a development or staging copy. Make a backup before installing it into an existing site, assigning new permissions or enabling integrations.

Requirements

  • ProcessWire 3.0.240 or newer
  • PHP 8.2 or newer
  • DOM, JSON and ZIP PHP extensions
  • A ProcessWire-supported database

Installation

  1. Download or clone the repository into site/modules/Kontor/.
  2. Run composer install --no-dev inside that directory.
  3. In ProcessWire Admin, open Modules and run Refresh.
  4. Install Kontor first.
  5. Install only the business components required by the project.
  6. Assign the smallest required kontor-* permissions to each role.

Repository and documentation

Feedback

I would especially appreciate feedback about:

  • installation on different ProcessWire, PHP and database environments;
  • admin UX, naming and navigation;
  • permissions and organization boundaries;
  • missing hooks, services or extension points;
  • real-world CRM, sales, finance and operations workflows;
  • REST, GraphQL, webhook and MCP integration;
  • component boundaries or unnecessary coupling;
  • documentation gaps;
  • scenarios that deserve an additional deterministic regression test.

This is a large project and a significant personal milestone. My goal is to give ProcessWire developers a flexible foundation for building business applications while preserving the freedom to compose each website in the ProcessWire way.

Testing, issues, architectural feedback and ideas are very welcome.

  • Like 11
  • Thanks 4
  • 2 weeks later...
Posted

Hi
Tried to install Kontor, but after installing the main module Kontor all the other modules are uninstallable because they say:

Module class must implement the "Processwire\Module" interface

image.png.b955b1ad6e6a8aba0faf29881147280e.png

image.png.8d57f7e4df4b62e1a75f45c455ac64b7.png

image.png.785cb9bac4731155f7e4c7eacf86abec.png

I have PW 3.0.274 and PHP 8.4

Posted

@lpa Thanks for reporting this. I confirmed the issue: the component discovery wrappers were missing the ProcessWire namespace, so ProcessWire loaded the implementation but looked for the module class in the wrong namespace.

This is fixed in Kontor 1.1.1. Please download the latest version, replace the existing Kontor files, run composer install --no-dev, and then use Modules → Refresh. The optional components should then become installable.

I also added a regression test covering all 34 component wrappers. Thanks again for catching this.

  • Like 2
  • 3 weeks later...
Posted

I think my head just exploded LOL. Crazy work. I could see someone creating a business/agency to help small businesses for this very thing: a turn-key solution based on Kontor.

CRM Intake + Intake could be just the start of a consultant agency. I have been helping get businesses to market for nearly 30 years. In the end, they have 5–6 tools they end up adopting. But the thought of starting—and building upon their needs—using Processwire means everything would be integrated.

Non-profits could be a good fit as most aren’t enterprise-level and they require a little hand-holding and boutique-ish, tailored solutions.

Thanks @maximus.

  • Like 3
  • 3 weeks later...
Posted

@maximus, this module looks so wonderful I couldn't believe it is a true thing and not an AI slop) An interesting thing - so many cool things appearing lead to an exhaustion so one can't even find time and energy to try if they are really cool))) Today I found those and finally installing Kontor...

I have to say, the installation is definitely a barrier to anyone wanting to try this out. I'll leave aside running composer from the folder. But clicking like 30 install buttons one by one in a particular order is a pain. And I am now only in the middle of it writing this post! There should be an umbrella module to install everything for testing purposes. Or something like that)) 

Or am I missing some obvious way to solve this? Just following the installation instruction.

Posted

I have installed it and toured for half an hour. I have to say that I kind of get scared of this brave new AI software world there you see something grandiose and complicated, but you cannot tell if it is working or not) Kontor is something like that. In pre AI era we couldn't imagine someone building such a thing. It is a monster. 35 submodules!

The first thing I have checked is db. All records have their own hard-coded tables. So PW extensibility doesn't apply if I got it correctly. Though еverything seems to be accessible via API (didn't try). Could be used as a backend for a store (Mercato?)

The interface looks ok in Konkat theme and much worse in regular Uikit. Though Konkat still has bugs like the black buttons not fixed.
image.thumb.png.0cc33c782f8c6970aa8bff47a19fdce3.png

Some glitches appear when you start adding things. An added personal dashboard widget appear off-grid.

image.thumb.png.5d14f2526253c73f029a4bff69a405bc.png

A task accidentally closed has no way to be brought back.

I think human testing and feedback can make this module useful for a case like a PW-based store. Not so sure if it can compete as a standalone solution for SMB.

Some better demo data is needed for humans getting into this. I have installed the demo package but it added only a couple of records. I could mess things up though.

@maximus, do you have someone working with this module day to day and giving feedback?

Anyway, good luck and thanks for creating such a thing! I remember in Joomla! times there were modules for everything there. Now we can have this in PW too.

Posted

Ivan, thanks for taking the time to install Kontor and try it. The notes about the installer, the dashboard and the closed task gave me concrete things to fix.

There’s now a demo setup command on main. On a test copy, run php bin/kontor demo:install /path/to/processwire to preview the order, then run the same command with --apply to install the 21 modules the demo needs. After that, go to Kontor → Demo → New scenario. I ran it on a clean ProcessWire installation: the first step creates six linked records, and the full order-to-cash run creates 21. The demo guide now explains where those records come from.

I fixed the personal dashboard grid and the widget ordering controls. Completed or cancelled tasks can now be reopened from Tasks → Closed, and completing a reopened recurring task won’t create a duplicate occurrence. I also fixed the button text contrast and some missing styles in Core Original. Konkat’s dark fill for primary buttons in light mode is part of the theme.

On the data model: yes, the business records live in Kontor’s own tables. ProcessWire handles the admin, permissions, module hooks and forms. A storefront can use the published PHP APIs for the business data and keep its own pages and templates.

I’ve deployed these changes on our own CRM and started testing them against the working installation. Jonathan Holden also sent five PRs based on feedback from a council CRM user, including clearer list links and configurable company fields. Those are merged and deployed too. That’s the kind of real-world feedback I want to keep building on.

Demo setup: https://github.com/mxmsmnv/Kontor#installation
Fixes: https://github.com/mxmsmnv/Kontor/commit/3e4d526457d15b0bdd6c6e3c8e815ad47b73c5b9

  • Like 6

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...