Workflow design, everyday task management, native e-signature, AI, hardware-sandboxed custom code, deep integrations, embeddable forms, a resale marketplace, admin security, and dedicated deployment — this page is the full reference. Jump to any section, or start from your role instead.
These are the things a team leader or member of staff interacts with constantly — and they're configured by an administrator in the UI, not modelled by a developer.
Each step can carry an SLA target set by any administrator — no process model required. Tasks show green, amber or red on the row itself.
Team leaders see every task across the processes they oversee, reassign work when someone's out, and rebalance load — without full admin rights.
When the default order isn't right — a key client, a regulatory deadline — team leaders set a work order number and move it to the top of the queue.
Normal, High or Urgent — set by the people doing the work, and reflected instantly in how every task list is sorted.
Tasks waiting on an inbound email, a WhatsApp reply, or a signature show exactly what they're waiting for — not just "in progress".
A deadline is a hard timeout. When it's reached, Opzaro can auto-approve, auto-escalate, or move the task on — no one has to notice it first.
Export step-by-step performance data — time in each step, who did what, SLA breaches — as CSV, whenever you need it.
Every step transition, data change and automated action is logged against the task, for every process, automatically.
Opening a task shows the actual, zoomable process diagram with the current step highlighted — not just an admin-only view.
Any authorised user starts a new instance of any process — an expense claim, an onboarding case — straight from their dashboard.
Users can save progress without moving a task forward, or submit and advance it — no lost work from partial data entry.
A task can be rewound to an earlier point in its history for correction — real-world approval bounce-backs, built in.
Effort spent on each step can be logged, feeding performance and utilisation reporting.
Processes are drawn as visual diagrams — start events, user tasks, gateways and end events — using an embedded BPMN.io diagram editor. Click any step to configure it across a small set of tabs that map to real operational decisions: how it's assigned, who can see it, what its SLA and deadline are, and what happens on entry and exit.
The form builder behind each step is designed visually, independent of the diagram itself, so different stages of a process can ask for exactly the right information without touching the flow around them.
Step configuration, in one place
Each tab is a business decision, not a technical one: who can act on this step, how long it should take, what happens if it runs over, and who it goes to next.
Processes, step code and permissions can be synchronised with a git repository — full, auditable source control, and the ability to support dev, staging and production instances properly.
Admins upload a shared library of helper functions available to every step's code across every process — automation building blocks, reused everywhere.
Whole processes (diagram, forms and code) export and import as a single package — for backup, version control, or promotion to production.
Opzaro includes a complete e-signature module — branded OpSign — built on the open-source OpenSign engine, giving it a credible, auditable pedigree rather than a black-box signing tool. The same signing engine that runs an automated "get this contract signed" step inside a process is also available for one-off, ad hoc signature requests from anywhere in the app. A task natively pauses when it needs a signature and resumes the moment signing completes — no middleware gluing a workflow tool to a separate DocuSign or Adobe Sign account. Configurable reminder cadence, document expiry windows and post-signing redirect URLs keep every request moving without manual chasing.
Every document's lifecycle, tracked automatically:
Sign-yourself (single-signer, immediate) and request-signatures (one or more people, sequentially or all at once).
Fields can be automatically positioned by scanning the document for existing content, instead of placing every field by hand.
Optional one-time-passcode verification, and optional full KYC identity verification (via Didit) before a signer can sign.
Every view/sign/decline event is logged with the signer's IP address and timestamp, for legal defensibility.
Individual signing steps can be sent to an external party as a single-use link needing no account.
Frequently sent documents are saved once with placeholder signer roles; a different real person is assigned each time.
Every document sent or received is automatically filed into a searchable folder tree — a document repository, no separate purchase.
A token-authenticated API (x-api-token) covers documents, templates, contacts, folders and webhooks.
PDF, PNG, JPG, JPEG and DOCX can all be sent for signature, with signature, initials, stamp, drawing and auto-filled fields placed precisely on the page.
Real-time webhooks on created/viewed/signed/completed/declined events — the same pipeline that resumes a paused workflow task the instant signing completes.
Each user sets up their signature, initials and stamp once — drawn, typed or uploaded — offered automatically whenever it's their turn to sign.
A saved address book of frequent signers, so senders pick recipients instead of retyping addresses every time.
A business user can describe what a step should do in plain English; Opzaro reads the whole process and generates ready-to-use step logic, constrained to real field names and functions. Structured AI calls (callAI) return strictly-typed, schema-validated JSON — not free text — reliable enough to drive further workflow logic. AI calls can reason over documents and images, and a per-process, fully intelligent document library answers plain-English questions grounded in your own material.
Plain-English instructions become working step logic, grounded in your actual data model.
A RAG-style assistant scoped to one process's own documents, searchable by keyword and meaning.
Text is automatically extracted from uploaded PDFs, Word documents and images.
Token cost from AI calls is tracked against each task, for reporting AI spend by process or case.
When a step needs real custom logic beyond the visual tools, that code runs inside its own AWS Firecracker microVM — genuine hardware-level virtualization per execution, not a scripting sandbox. A pre-baked base image lets each job start in tens of milliseconds via warm image snapshots. Both PHP and Python are supported, with Python getting full access to platform helper functions through a secure bridge. On simpler hosting without Firecracker set up, code still runs in-process.
See the full architectureOpzaro is designed to sit inside your existing technology landscape — not to replace it — so you can orchestrate the systems and APIs you already run from a single workflow engine.
Staff sign in with credentials they already use; permissions and team-leader status can be driven from Azure AD groups.
Files, folders and SharePoint Lists are available to step logic at runtime — your existing document store stays the source of truth.
A task can pause and resume on an inbound email reply or a WhatsApp reply from a specific number — no portal login required.
Every action available in the UI is available via API, including generic outbound calls to any third-party REST endpoint.
A step can kick off and wait on a full KYC identity-verification session, with secure webhook confirmation.
A step can hand data to an external automation endpoint and read updated values back — for existing Microsoft automation investments.
Any step can pause until a matching external system posts data back — for payment processors, CRMs, or internal tools.
Region-aware transactional email sending (EU/US) for notifications, reminders and approvals.
A single script tag and a <div> renders a live, fully-styled, multi-step form for a published process on any third-party website — a customer intake form, a job application, a service request — with no iframe workaround, and styling that matches the host page. Turning a process into a public-facing form is a single toggle in the process designer, alongside a configurable "thank you" completion message.
An anonymous visitor can progress through an entire multi-step process — including "Back" navigation and resuming later — without ever creating an account, secured by signed tokens rather than a login session. A slow step running in the background can show live status polling (e.g. "processing your request…") while it completes.
<div id="opzaro-form"></div>
<script src="https://embed.opzaro.com/widget.js"
data-process="client-intake">
</script>
Whole processes can be packaged, encrypted, and sold as products: one-time, expiring, domain-locked download tokens are issued per customer, so a purchased process only runs on the licensed buyer's domain. A sold process's business logic ships encrypted and cryptographically signed — buyers get a fully working automation without ever seeing, or being able to tamper with, the underlying step code.
Configuring a Shopify webhook lets a customer's purchase automatically issue and email them their licensed download link, with no manual fulfilment step — turning Opzaro into a genuine storefront for agencies and consultants who want to package and resell automations as products.
A process is packaged, encrypted and cryptographically signed for distribution.
A Shopify checkout completes and fires a webhook back to Opzaro.
A domain-locked, expiring download token is issued and emailed — no manual fulfilment.
Passwordless magic-link sign-in by default, falling back automatically to full Entra ID SSO when configured. Access can be granted at the whole-process level or narrowed to one specific step, to individual users or groups. Team leads see and manage their team's tasks without full administrator rights, and a specific step can be sent to someone outside the organisation as a one-time, expiring link — no account needed.
Application name, tagline, logo and full theme colour palette are configurable for white-label use, and sign-in provider, integrations and infrastructure settings are all managed from a single settings screen, with secrets masked in the UI.
A scripted installer provisions a complete production stack — web server, PHP, database, HTTPS certificates and optional sandboxing — as its own isolated deployment. Each customer gets a dedicated instance and database, with its own independent scheduler, config and database, not a shared multi-tenant backend. Processes can be started automatically on a recurring (cron) or one-time schedule, with full timezone awareness.
Most workflow tools are built around one of these — usually "someone fills in a form." Opzaro treats all of them as first-class triggers into the same engine.
We'll walk through a real process from your operation — onboarding, approvals, claims, change control — and show how it would look, step by step.