LiveBPM® workflow platform
The deterministic backbone. It carries forward more than twenty years of engine experience from LiveFlow. Rewritten on .NET + Vue, with SaaS multi-tenancy and on-premise deployment side by side, and a REST API as the execution and compliance backbone.
- LiveBPM is our enterprise workflow / BPM platform
- BPMN 2.0 engine, low-code forms, permissions, routing, notifications and dashboards
- .NET + Vue, containerised, on-premise / SaaS multi-tenant / hybrid
- REST API across authentication, instances, to-do items, forms and routing; eight languages
- Integrates with AI office assistants (WorkBuddy, 豆包 Work and 千问办公) so work happens in chat
Everything a process platform should have
More than 90% of processes, forms and reports are built without code. The remaining 10% is covered by open interfaces and source-level extension.
Process engine
BPMN 2.0 modelling by drag and drop. Countersign, add-signer, withdraw, transfer, delegate, notify, hold and resume, overdue reminders and automatic handling, out-of-office delegation.
Form engine
A low-code designer with sub-tables, formulas and totals, validation, attachments and signature blocks. Each step of a process can show a different form, responsive across devices.
Organisation and permissions
Multiple organisations, positions, dual roles and delegation. Role and data-scope based permissions, with users imported and synchronised from the domain or Active Directory.
Rules and routing
Route by form data, position, department and amount band in combination. Dynamic handler resolution, substitute handlers, shared tasks and handler exclusion.
Notification centre
In-app, email, SMS and WeCom / DingTalk / Feishu messages. Templates can embed form data and are sent in each recipient's own language.
Reporting
Process efficiency analysis by process, step and handler. Monthly, quarterly and annual statistics with drill-down, Excel export, and visibility scoped automatically by organisation.
Open platform
A REST API covering authentication, process instances, to-do items, form read/write and approver routing, plus webhook events and integration with development platforms.
Languages and devices
Eight interface languages set per user. Responsive web, with the mobile view embedded into the WeCom, DingTalk and Feishu workplaces.
Complexity belongs in the engine, simplicity in the interface
Branching, joins, parallel handling, exclusive conditions, "the first manager who exists", "many people can see it but only one handles it" — these are built-in semantics, not exceptions that need coding on site.
- Transactional handling, so process integrity is guaranteed
- Every action recorded; the full history can be replayed
- Standard handling times and overdue policies reduce human delay
- Per-user language and out-of-office settings for distributed teams
Built-in process operations
Three directions into your systems
Down: infrastructure
Single sign-on against LDAP / Active Directory and mainstream OAuth2 / OIDC providers, plus relational databases, mail and messaging platforms.
Across: existing systems
ERP, HR, CRM and finance data synchronised through a unified tool gateway and adapters, with XML, web, database and file exchange all supported.
Up: applications and agents
A REST API built around process instances, work items, forms and approver routing, for your own applications, portals and LiveAI agents.
Run your processes inside AI office assistants
The employee entry point is shifting from system menus to AI assistants. We package process capability as skills those assistants can call, so people can check progress, pick up tasks, file requests and approve from a conversation in WorkBuddy, 豆包 Work and 千问办公 — while execution and the audit trail stay in the engine.
One entry point
File a request, check progress and handle to-do items inside the assistant, without switching systems.
Capability as skills
Starting processes, querying work items, reading and writing forms and resolving approvers are wrapped as standard tools, registered through each assistant's plugin or skill interface.
Permissions unchanged
Single sign-on and data scoping still apply: what the assistant can see and do matches exactly what that person can do in the system.
Execution stays in the engine
The assistant handles the conversation. State changes, approval records and audit logs are all written by LiveBPM, replayable and auditable.
| Interface area | Capabilities | Typical use |
|---|---|---|
| Authentication | Token issue and renewal, single sign-on | Portal integration, mobile embedding |
| Process instances | Start, query, chase, terminate; read current step and history | Triggering from business systems, progress dashboards |
| Work items | Query, handle, transfer; create items for human confirmation | Unified to-do centre, human-machine collaboration |
| Form data | Structured read and write, including sub-tables and attachments | Write-back, reporting extraction |
| Approver routing | Resolve handlers dynamically by organisation, position and rule | Complex approval chains, per-organisation variation |
Built to run for a long time
Stack
- .NET on the back end, Vue on the front end, decoupled
- SaaS multi-tenancy with tenant-level data isolation
- Containerised delivery, horizontally scalable
- End-to-end audit logging
Deployment
- On-premise: your data centre or private cloud; data stays inside
- SaaS: provisioned per tenant, live quickly
- Hybrid: process in the cloud, sensitive data and models local
Security
- Single sign-on, fine-grained permissions and data scoping
- Encryption in transit and at rest, sensitive fields masked
- Business data is append-only; reversals are recorded, never deleted
- Logging, auditing and credential custody for compliance regimes
The process engine is the AI's seat belt
An agent may read process context, write a recommendation, create a work item for human confirmation and, within its authorisation, trigger helper flows. It may not write business master data, complete a work item on someone's behalf, change routing rules, or start a process that moves money or state.
| Action | An agent may | An agent may not |
|---|---|---|
| Read context | Query the instance, current step, form data and history | Read data outside its authorised scope |
| Write recommendations | Write conclusion, evidence, confidence and suggested action into an AI field | Write amounts, codes or status into business master data |
| Create work items | Create a confirmation item with a role and a deadline | Complete a work item, or change approver routing rules |
| Trigger processes | Start reminder-type helper flows under L0 authorisation | Start business processes that change amounts or state |
LiveBPM questions
What is LiveBPM?
LiveBPM is our enterprise workflow / BPM platform. It provides a BPMN 2.0 process engine, a low-code form designer, organisation and permission management, rule-based routing, a notification centre, reporting dashboards and a REST API. It is responsible for reliable execution and a complete audit trail.
Which process operations does LiveBPM support?
Start, assign, withdraw, direct-send, hold, pause, stop, resume, countersign, add-signer, notify, transfer, delegate, archive, out-of-office delegation, substitute handlers, shared tasks, overdue reminders and automatic overdue handling, scheduled start. All of these are built into the engine, not scripted per project.
What can LiveBPM integrate with?
Single sign-on against LDAP / Active Directory and mainstream OAuth2 / OIDC identity providers; ERP, HR, CRM and finance systems through a unified tool gateway and adapters; a REST API covering authentication, process instances, to-do items, form data and approver routing; webhook events; and messaging through WeCom, DingTalk and Feishu.
Can LiveBPM work with AI office assistants?
Yes. Starting a process, querying work items, reading and writing form data and resolving approvers are wrapped as standard tools and registered through each assistant's plugin or skill interface, so people can check progress, pick up tasks, file requests and approve from a conversation in WorkBuddy, 豆包 Work and 千问办公. The assistant is only the entry point: permissions follow single sign-on, and state changes and approval records are still written by the process engine.
Does LiveBPM support multiple languages and mobile?
Eight interface languages, selectable per user. The web interface is responsive, and the mobile view embeds into the WeCom, DingTalk and Feishu workplaces.
What is the technology stack and how is it deployed?
.NET on the back end, Vue on the front end, decoupled, delivered as containers. Available on-premise (your data centre or private cloud), as SaaS multi-tenant, or hybrid with the process in the cloud and sensitive data and models kept local.
How much can be built without writing code?
Process modelling, form design and report generation are all graphical. More than 90% of processes, forms and reports are built without code; the remainder is handled through open APIs and source-level extension.
Want to see it running on your own process?
Book a 45-minute online demo. We build a working sample from one of your real processes and show how deterministic execution and AI recommendations work together.