Ops PlatformAvailable

Ops Platform

The Straventa Ops plane runs your back office on a single configurable DocType engine: typed records with state machines, per-transition role permissions, custom fields, assignees, watchers, comments, attachments, and automations. Every vertical is a module of one console. Helpdesk is live today; more verticals are on the roadmap.

Book a Demo

At a glance

Helpdesk that ships today, on an engine that models any back-office workflow — typed records, state machines, role-gated transitions, and SLA timers.

What it does

Built for the work, end to end

DocType engine

Model any workflow as a typed record with a state machine, custom fields, assignees, watchers, comments, and attachments — configuration, not a new code tree per vertical.

Role-based transitions

Every state transition is gated by a role permission, resolved from the same Straventa Accounts token used across the estate.

Automations & SLAs

Trigger actions on events and on time, with SLA response and resolution timers and a breaching-soon worklist. Automatic escalation on breach is not implemented yet — a breach is recorded and surfaced, not routed.

Helpdesk

A live ticketing vertical: a triage inbox with saved-view filters, threaded records, and SLA tracking out of the box.

Inbound email

Email-in ingestion turns a mailbox into records and lets authenticated senders reply-append to an existing thread.

Multi-tenant & audited

Row-level tenant isolation, a hash-chained audit log, and an outbox-first event stream — self-hostable beside Payops.

How it works

From kick-off to day-to-day

Configure the doctype

Define the record, its states and transitions, its fields, and who may move it — as configuration, not code.

Route work in

Point a mailbox at it or create records directly; automations assign, escalate, and track SLAs.

Work the queue

Teams triage from saved-view inboxes and move records through their state machine — every change audit-logged.

How it compares

Ops Platform vs the seat-priced service desks

Indonesian buyers evaluating a back-office or service-desk plane almost always land on Freshservice, Zendesk, Jira Service Management, or Odoo. All four are mature and all four are priced by how many people you let into the queue, and three of the four cannot run inside your own data centre at all. Straventa Ops is one configurable DocType engine — typed records, state machines, role-gated transitions, automations, and SLAs — with Helpdesk live today, self-hostable beside Payops, and signed in through the same Straventa Accounts token as the rest of the estate.

Ops Platform vs the seat-priced service desks
Criterion	Straventa Ops Platform	Freshservice	Zendesk	Jira Service Management	Odoo
Deployment model	Self-hostable on your own Kubernetes or Docker, beside Payops — or run by Straventa. Same product either way.	SaaS only — the Freshworks cloud. There is no self-managed edition.	SaaS only.	Cloud is SaaS. Self-hosting means the Data Center edition under an annual licence — Atlassian ended Server sales.	Self-hostable: Community (LGPL) or Enterprise on your own servers, or Odoo Online / Odoo.sh.
Where the record data lives	Your infrastructure, in Indonesia, on a self-hosted deployment — record bodies, attachments, and the hash-chained audit log never leave your environment.	Freshworks regions (US, EU, India, Australia), chosen at signup. There is no Indonesian region.	Zendesk's own regions; a paid Data Center Location add-on pins hosting to the EU. No Indonesian region.	Cloud residency pins to Atlassian's published region list (US, EU, Australia, Germany, Singapore and others) — Indonesia is not on it. Data Center is your own servers.	Odoo Online regional data centres, or your own servers if you self-host.
Pricing model	Per deployment, on request. The published price catalogue covers the Payops modules; Ops is quoted for the deployment, not per agent.	Per agent, per month, tiered by plan, with paid add-ons.	Per agent, per month, tiered by suite plan.	Per agent, per month on Cloud (free up to 3 agents); Data Center is an annual licence sized by agent tier.	Per user, per month on Enterprise, across the whole app catalogue; Community is free to licence and yours to run.
Configuring a new workflow	A doctype: define the record, its states and transitions, its fields, assignees, watchers, and attachments — configuration, not a new code tree per vertical.	Custom objects and the workflow automator, within the ITSM/ESM model and on higher plans.	Custom objects, triggers, and automations built around the ticket object.	Request types, workflows, and custom fields per project; deeper models need marketplace apps or Forge.	Odoo Studio to add models, fields, and automations — Studio is an Enterprise feature.
Who may move a record	Every state transition is gated by a role permission, resolved from the same Straventa Accounts token used across the estate — one place to change a rule, one place to audit it.	Roles and groups inside Freshservice; identity comes from whatever IdP you already pay for.	Roles inside Zendesk; identity comes from your own IdP.	Permission schemes per project, with Atlassian Access / Guard for identity, licensed separately per user.	Access groups and record rules per model; sign-in via an external OAuth or SAML provider you supply.
One login across your estate	Straventa Accounts is the estate's self-hosted OpenID Connect provider, licensed per deployment rather than per employee — Ops, Payops, and your own registered applications share an issuer you run.	Connects to your identity provider — a separate product, usually billed per seat.	Connects to your identity provider — a separate product, usually billed per seat.	Atlassian Access / Guard is a separate per-user subscription on top of the agent licence.	Bring your own IdP; the integration and its licence are yours.
What else runs on the same plane	Helpdesk today with more verticals on the roadmap, plus the Payops payments, KYC, AML, fraud, and reconciliation modules deployed alongside it under one contract.	Freshworks' wider product family — separate products, separate subscriptions.	Zendesk's suite: support, messaging, and add-ons, each priced separately.	The Atlassian estate — Jira, Confluence, and marketplace apps, each licensed on its own.	A broad ERP catalogue, but the payments side is generic — not shaped around Indonesian rails or OJK expectations.
Who answers at 03:00	A named Jakarta-based engineering contact, on terms set in your contract, in your timezone.	The support tier you purchased, in an offshore timezone.	Your plan's support tier, offshore.	Atlassian support at your plan level, or a solution partner you retain separately.	Odoo Enterprise support, or your own team on Community.

Competitor rows describe each vendor’s publicly documented model at time of writing; confirm current terms with the vendor before making a decision.

How it is priced

Every incumbent here bills per agent or per user per month; Ops is quoted per deployment, so the price tracks the deployment rather than how many people you let into the queue.

Billing model

Per deployment — on request

No published list price. The Straventa price catalogue covers the Payops modules only — Ops Platform is quoted per deployment, on request.
Freshservice, Zendesk, and Jira Service Management Cloud all price per agent per month: every new agent and every new team is a line item, forever.
Odoo Enterprise is per user per month across its whole app catalogue; the free Community edition is yours to licence and yours to be on call for.
One deployment covers every doctype you configure — a second back-office workflow on the same engine is configuration, not a second product contract.
A self-hosted deployment carries your own infrastructure cost, and standing it up inside your environment (Kubernetes or Docker, HA, backup and restore rehearsal, handover runbook) is a Straventa on-premise engagement, scoped and priced separately.

See the full price list

Want Ops Platform for your team?

Bring your rails, controls, and deployment constraints. We will show where the platform fits and where it does not.

Book a Demo Talk to Sales