Automation inside your own product, on your own terms.
Ship a workflow builder to your customers without building one. OCNORA runs as a multi-tenant control plane behind your product: your brand, your tenants, your limits.
Three workflows teams build here first.
- 01
A workflow tab in your product where each tenant builds and runs their own automations against their own data.
- 02
Product events that fan out to your customers’ tools: CRM updates, invoices, notifications, webhooks to their systems.
- 03
Vertical automations you ship as templates, so every tenant starts from a working workflow instead of a blank canvas.
Webhook transform and forward
Receive any JSON, normalise a few fields, reshape it and forward to another endpoint — the smallest useful glue workflow.
Built for this, not adapted to it.
Embed with an iframe and a token handoff
The builder mounts in an iframe; your host page passes a short-lived tenant token over postMessage. No shared cookies, no second login.
JIT SSO for your users
Users are created on first arrival from the token your product signs. No user sync job, no double invitation flow.
Per-tenant plugins and images
Ship private nodes to one tenant without touching another. Each tenant can run its own plugin image on the same control plane.
Per-tenant AI budgets
Monthly token and dollar caps per tenant and per provider, with a circuit breaker when a tenant hits the line. You never pay for a customer’s runaway agent.
White-label
Your logo, your colours, your domain. The dashboard already ships in 21 languages, so your tenants see the builder in theirs.
Licensed per tenant
Embedded partners hold one licence per tenant, signed offline with Ed25519 and checked without a phone-home. Add a tenant, add a licence.
Apps this kind of workflow usually touches.
Each one has its own page with operations, triggers and auth.
See a workflow run in your first ten minutes.
Create a workspace, import an n8n file or start from a template, and watch Workflow Health check it before it ever runs.