OQTERANAutomation engine
Versioned rules with an auditable run history
A transactional-outbox worker with retries, backoff, dead-lettering and idempotency. Every run records what fired, what it touched and what it did next.
One tenant. One audit trail.
Every request, story and release in one system of record.
Oqteran runs the path from a raw business request through discovery, PRDs, backlog and sprints, into QA, UAT and release, and out to measured outcomes. Nothing gets planned without a sponsor. Nothing ships without a gate.
SSO and role-based access on every plan. No credit card to see it.
Committed
86 pts
101% of capacity
Done
41 pts
48% burned
Blocked
3
2 on one dependency
Release gate
4 / 6
UAT sign-off pending
8
domains, intake to admin
24
modules, one data model
9 × 5
roles by personas, server-side
100%
of writes in the activity log
Lifecycle
Five stages. Five rules.
The rule is the product. The screens follow from it.
01IntakeA request needs a sponsor and a decision record before it can enter the backlog.
02PlanReadiness gates the backlog. RICE sets the order. Capacity is checked at commit, not at review.
03BuildItem, story and ticket share one identity, so the parent rolls up without a second view.
04AssureA release gate names what is still open: sign-offs, blocker defects, rollback plan.
05MeasureEvery roll-up states what it counted, so a number can be traced back to its rows.
Platform
Set it up once. Run it the way you work.
Multi-tenancy, permissions, automation and integrations are part of the model rather than added around it.
Access and audit
Nine roles, five personas, one enforcement point
A role by capability matrix enforced server-side. Personas change navigation, never privilege. Every write lands in the activity log with its actor and reason.
Multi-tenancy
Org- and workspace-scoped, down to the row
Provision, rename and suspend organisations from the platform console. Support entry requires a reason and issues a short-lived impersonation that expires on its own.
Notifications
In-app, email and push, on the user's terms
Per-user channel, category and quiet-hour preferences, with realtime updates across nodes. Escalations and digests come from the same rule engine as everything else.
Pricing
Clear plans that scale with you
Team
One workspace
For a single product and engineering team running the full lifecycle.
All 24 modulesUp to 40 users10 active automation rules90-day log retention
Business · most common
Many workspaces
For an organisation that needs portfolio roll-up across teams.
Everything in TeamUnlimited workspaces and usersPortfolio and initiative roll-upUnlimited automation rulesJira, Slack and webhook delivery
Enterprise
Custom
For regulated organisations with their own governance requirements.
Everything in BusinessCustom roles and readiness rulesUnlimited retention and exportSLA and dedicated onboardingSingle-tenant deployment option
FAQ
Questions we get on every first call
It can. Keep Jira for engineering execution and use the two-way delivery integration, or move the board across and run everything in one place.
One workspace is usable the same day. Multi-workspace rollouts take two to three weeks, most of it agreeing the taxonomy rather than configuring software.
Your role decides what you can write and is enforced on the server. Your persona decides what you see and is yours to switch. Switching never grants a permission.
In an org- and workspace-scoped Postgres tenant you can export at any time. Enterprise can run single-tenant in a region you choose.
See it on your own backlog.
Sign in to your workspace, or let us walk you through a live one. If your organisation uses SSO, you will be sent to your provider.