Loading Praxia Loading Praxia

From process
to execution.

Enterprise low-code, workflow automation and process orchestration

Model the data, draw the process, compose the screens, publish the service. Then watch it run, promote it between environments and prove what happened. One model underneath all of it, on your own infrastructure, in Arabic and English.

How a case moves

  1. 01 Receive form, event, webhook
  2. 02 Route decision table, delegation
  3. 03 Decide committee vote, quorum
  4. 04 Issue sealed, tracked, audited

A walkthrough, end to end

The same path the four stages describe, running in the product: model an entity, shape the process, publish the portal, and watch the work land.

Begin wherever the work already is

Most platforms make you choose a starting point and then live with it. Begin from a process, a dataset, or a system that will not be replaced, and the rest composes around it.

Orchestrate
anything

Process automation across people, applications, databases and events under one workflow engine, with delegation, escalation, acting on behalf and committee approval modelled as themselves.

Build
anything

Entities, forms, portals and mobile apps from one model. Start from ready templates (forms, documents and email) and reuse them across services.

Connect
anything

Records stay in the system that owns them. 58 connectors, any HTTP, SQL or queue endpoint, and named inbound events with their own webhook and secret.

Operate
anything

Changes travel as a signed release: planned, reviewed, applied, reversible. Two consoles at either end, and a CLI that reaches any environment by name.

Not a workflow tool with features bolted on

Author

Run

Observe

Connect

Operate

The diagram is the thing that runs

No export step and no generated stub to maintain. What an analyst draws is what the engine executes, so the picture on the wall and the behaviour in production cannot drift apart.

The rule lives in a table, not in the diagram

Policy changes more often than process. Put the thresholds in a decision table and a director can change who reviews what without anyone reopening the workflow.

Start from a template, not a blank page

Entities, relationships and enumerations define the data once. Forms, documents and email all read that model, so a field added in one place appears everywhere it belongs, in both languages.

Connect what you already run

Records stay in the system that owns them. Integration is declarative: a process reads and writes them where they live, through endpoints composed and named rather than buried in a step.

A front door that belongs to the institution, not to us

A catalogue to request from, an inbox to work in, and their own requests to follow. A ministry, an authority, or any government or public-sector body gets a front door carrying its own identity. The same portal below is shown four ways: the institution’s own colours, light and dark, English and Arabic. Nothing is rebuilt between them, the theme and the direction are settings.

Four appearances, one definition. The institution sets its colour and logo once, the reader chooses light or dark, and the direction follows the language. The widgets above are published from Insight Studio, so the numbers on a portal are the same numbers the metric produced, not a second copy kept in step by hand.

A citizen follows a case with no account at all

The petitioner who filed the request is usually not a user of your system and never will be. They enter the reference, confirm a one-time code, and see exactly where it stands. No registration, no password to forget.

The same services, as an app you publish

Compose an app from the services you already built, then build and sign it. On launch the runtime asks what this app may show and what has been switched off underneath it, so a plan change or a withdrawn service takes effect without a new release.

Measure it without exporting it

Define a metric, compute it on a schedule, compose it into a widget and publish that into a dashboard slot. The snapshots are append-only, so last quarter’s number is still last quarter’s number.

Who did what, to which case, and when

By case, by person, summarised across a period, and exportable, including the vote each committee member cast and the deputy who acted on whose behalf.

Your infrastructure, your data, your keys

The host that builds a release cannot be the host that approves it

Design host · driver, Builds and signs

Runtime host · agent, Verifies and approves

Installed, not rented

Self-hosted on-premises on your own SQL Server, as a Windows service or under systemd on Linux.

People sign in where they already are

Azure AD, OIDC or LDAP, per tenant, with role templates and permissions.

You can walk away

A complete .NET, Angular and Flutter solution from the same model.

Hijri, Arabic names, national identifiers

Built in the Middle East for government and public-sector work across the Gulf, by a team in the same time zone as the people who run it.

Arabic is the same build, not a second one

The whole composition mirrors, not just the words. One form definition, rendered twice.

Straight answers, before the call

What is Praxia?

Praxia is an enterprise low-code platform for workflow automation, process orchestration and case management. A process is drawn on a BPMN canvas and executed as drawn, and it can orchestrate work entirely through integration - reading and writing records in the systems that already own them, with nothing modelled in Praxia. Where you do want Praxia to own the data, a single model defines the data entities and generates the schema, the migrations, the forms and the code. It runs as a hosted subscription or on your own infrastructure, in Arabic and English.

Is Praxia low-code or a BPM engine?

Both, and the combination is the point. It is a low-code application platform built around a BPMN workflow engine, with case management as a first-class concern rather than a pattern you assemble. A workflow engine alone leaves you building the application around it; an application platform alone leaves the process as a component.

Is Praxia model-driven, and do we have to model our data?

It can be model-driven, and it does not have to be. A complete service can be built with no model at all, orchestrating systems that already own the records over HTTP, SQL or a queue, with Praxia holding only the process state - nothing migrated, no new database. Where you do want Praxia to own the data, a single model defines the data entities and generates the schema, the migrations, the forms and the code, diffing model against database to produce each migration. Modelling is one of three ways in, not a prerequisite.

Does Praxia do AI?

In two distinct ways. An AI Architect builds the solution: describe a service in plain language, or hand it a requirements document, and it composes the entities, the workflow, the forms and the approval chains - then gives you a draft to review, approve and deploy, never a change it made on its own. Separately, AI runs as ordinary workflow steps, 28 activity types across models, agents, tools, chains, memory and vector stores, so a model call, a retrieval over your own content, a human approval and an ERP write sit in one flow under one audit trail.

Is the AI allowed to change things by itself?

Only if you let it. A session runs in Plan, which proposes and does nothing, Ask, which stops for approval at every step, or Auto. Whatever it produces is a draft that is listed, reviewed, approved and then deployed, so nothing reaches a database or a running process because a model decided it should.

Can we start without replacing anything we already run?

That is the common case. Begin from a process and let it read and write records where they live, bind entities onto tables Praxia did not create, or model new data where none exists yet - and mix all three in one workspace. A single flow can read from SAP, write a decision to a modelled entity and raise an event to a queue.

Is Praxia cloud or on-premises?

Both, and the same product either way. Praxia is offered as a hosted subscription and as a self-hosted installation on your own servers or cloud tenancy; licensing follows the size of the installation and how it is hosted. Institutions with data residency obligations run it inside their own boundary, and releases move between environments as signed, reversible envelopes.

Is Praxia multi-tenant, and what is a workspace?

One installation serves many organisations, isolated from each other down to the database schema - two tenants modelling the same entity get separate physical tables, not a shared one. Within a tenant, work is divided into workspaces, typically one per service or department, each with its own model, workflows, connection and schema. How many workspaces you get is a licensing tier.

Can we reuse forms, documents and emails across services?

Yes, that is what templates are for. Form templates compose from over 40 controls with right-to-left layout and signature fields, document templates merge case data and attach the result, and email templates preview before they send. A form can also be generated directly from an entity, taking its fields, types and required flags from the model.

Does Praxia support Arabic?

Fully, including right-to-left layout, from the same model as English. Entities and forms carry bilingual labels rather than sitting behind a translation layer, so an Arabic service is the same composition under a different setting, not a separate build.

How does Praxia compare to Camunda, Appian or OutSystems?

Closest in shape to Appian and Pega, which also put process, data and case management in one platform. Camunda is a workflow engine you build an application around; OutSystems and Mendix are application platforms where process is a component. Against all of them Praxia differs on two axes: self-hosting as the default, and Arabic-first public-sector work.

What can Praxia connect to?

58 connector activities, including SAP, Microsoft Dynamics, Odoo, SharePoint and CRM systems, plus any HTTP, SQL or message-queue endpoint. Inbound events are named in a catalogue, each with its own webhook, signing secret and test fire. Records stay in the system that owns them.

Who is Praxia for?

Government bodies and enterprises, principally in the Gulf and the wider Middle East, that need services modelled, run, measured and audited on infrastructure they control. The features that distinguish it - committee voting with quorum, acting on behalf, public case tracking without an account, signed promotion - are the ones institutional work actually needs.

Find the shape that fits, then talk to us

Licensing follows the size of the installation and how it is hosted, so the right number comes out of a short conversation rather than a table. Pick the one that sounds like you.

Free

One workflow and one workspace, with the whole designer open, for fourteen days. No conversation, no card, nothing to sign. Open it and start building.

Starter

A single directorate putting its first services online, with the branded portal in front of them.

Professional

Several departments sharing one model, with connectors, the event catalogue and code generation.

Business

An entity serving several tenants, with Mobile Studio and the full integration surface.

Enterprise

A national programme, with the signed release path end to end and segregated environments.

Install it in your own network instead

Any plan above can run on-premises, on your own infrastructure rather than ours: your SQL Server, your backup and retention policy, your directory, as a Windows service or under systemd on Linux. Licensing then follows the installation, which is a conversation about environments and support rather than a per-seat figure.

Bring a process you already run

Bring a government, public sector or enterprise process. We will model it, draw it and show it running on a demo tenant with real data. Not slides.

[email protected]

Praxia on LinkedIn