Engagements are configured, not priced off a list.
Every engagement is a different combination of three components. The right number for one operation is the wrong number for another. We would rather explain how the model works than publish numbers that do not apply to your case. This page explains the three components. When you talk to us, we scope each one to what your operation needs.
The right to run Kwerio as your operational substrate.
Platform licensing scales with the shape of your deployment, not with the number of seats. A single-tenant deployment with one project is priced differently from a hierarchical multi-tenant deployment with delegated administration. A hardware appliance in your DMZ is a different commercial structure from a shared-hosted environment.
Three things shape platform licensing.
Tenancy model
Single-tenant single-project, single-tenant multi-project, shared multi-tenant, hierarchical multi-tenant, or fully isolated. Each model carries different infrastructure assumptions and different commercial implications.
Deployment surface
Imageplus-operated cloud, your own AWS or GCP or Azure, sovereign cloud, on-premises, hardware appliance. The platform runs in any of these. The licensing reflects which one you choose.
Scale and modules in scope
How many modules are active. How much data the platform is holding. The shape of your operation, not the number of named users.
What platform licensing is not. A per-seat tax that grows with your headcount or with the number of AI agents you deploy. We do not charge per agent, per workflow, or per audit log entry. The substrate is licensed for the operation, not the activity inside it.
The contract for keeping the platform running.
Operational software is only as good as the day it stops working. The operations and SLA component covers the work of keeping the platform up. Monitoring, backups, disaster recovery testing, incident response, and the uptime commitments that match your operation's tolerance for downtime.
Three dimensions shape it.
Uptime targets
A consumer-facing operation has a different uptime requirement from an internal back-office system. RTO and RPO are scoped to the operation. The SLA reflects the cost of meeting them.
Coverage hours
Standard business hours coverage is one commitment. 24/7 active monitoring with on-call response is another. Engagements vary.
Disaster recovery posture
Annual DR testing is the baseline. Some engagements require quarterly testing, geographically distributed failover, or specific recovery scenarios documented and rehearsed.
Operations and SLA is a recurring component. It scales with the operational discipline your engagement requires, not with platform usage.
The work of building what is specific to your operation.
Kwerio comes with a substrate and a foundation. The modules that fit your specific operation. The CRM that matches your customer model. The invoicing flow that handles your specific approval logic. The orchestration shell that ties your existing systems together. Built per engagement, on the Kwerio substrate, by Imageplus as the implementation team in the ecosystem.
This component is project-shaped, not subscription-shaped. It is scoped against three dimensions.
Specification
Imageplus uses BPMN-driven specification methodology to scope what gets built before quoting. The output is a clear specification with traceability from what the operation needs to what gets deployed.
Build complexity
Generic pages. CRUD, list views, forms. Scaffolded from the schema in under an hour. Custom logic, complex workflows, and integration with external systems take longer. AI-assisted development has accelerated custom build by roughly 10x compared to pre-AI cycles. A complex orchestration is still a complex orchestration.
Integration scope
Connecting to SAP, Salesforce, KYC platforms, customs systems, accounting software, or legacy bespoke tools is per-integration work. Webhooks, REST and SOAP APIs, n8n, Make.com, MCP. The toolkit is broad. The integration is scoped per case.
Some engagements are weeks. Some are months. The specification work surfaces what it actually is before the commercial commitment.
How to think about the total.
A typical engagement combines all three. Platform licensing for the deployment shape you choose. Operations and SLA for the uptime and discipline your operation requires. Custom module development scoped against your specification.
A small engagement on shared hosting with standard SLA and a focused module scope is a different commercial conversation from an enterprise engagement on a hardware appliance with 24/7 active monitoring and a multi-system orchestration scope. We do not try to compress both into the same price list.
If your operation is closer to the small end, the conversation is short and the engagement is fast. If it is closer to the enterprise end, the specification work is more substantial and the conversation takes longer. Either way, we would rather scope it properly than mis-price it.
What is not on this page.
We do not publish numbers. Every range we could publish would be wrong for some real engagement, and right for none. The conversation does the calibration that a price list cannot.
We do not compete on price against off-the-shelf SaaS. Kwerio is bought when off-the-shelf does not fit. That is a different decision from which SaaS is cheapest. If price-per-seat is the dominant criterion, we are probably not the right answer.
We do not take on engagements where the fit is wrong. We say no when an operation would be better served by a packaged product or by a different platform. The first conversation is partly a fit assessment in both directions.
Talk to us about your engagement