OPEARIA
SRRequest a demo

PRODUCT STATUS

06 / OPEARIA

Available, contracted and in development are not the same.

Status labels separate production Web capability, contracted packages, Android scope and integrations that are not yet connected.

Final availability is confirmed for the specific version, work surface, package, company and user role.

DECISION STRUCTURE

From a question to a documented decision.

01How to read status
02Available by contract
03Access control
04Integrations in development
05Android status

AVAILABILITY MATRIX

One platform does not mean an identical role for every application.

Status is informational. Final scope and availability are confirmed for the specific version, company and contract.

Capability status by application
CapabilityWebAndroidPackage
Identity, tenant, roles and data scopeShared foundationShared foundationCore
Core ticketing, SLA, comments and auditAvailableSupported mobile scopeCore
Equipment 360 and advanced service historyAvailableMobile alignmentCasino Tech
Casino Service Extended and Command CenterAvailableMobile alignmentCasino Tech
Warehouse, custody, repair and QAAvailable by contractMobile alignmentWarehouse & Inventory
Procurement, purchase orders and partial receiptsAvailable by contractWeb-onlyProcurement & Supply
Advanced analytics and administrative reportsAvailable by contractMobile views in preparationContracted package
Google, Teams, Slack, Jira, WhatsApp and ViberIn developmentNot connected in productionIntegrations
SuperAdmin, demo reset, contracts and large importsWeb-onlyNot plannedAdministration

How to read status

AVAILABLE BY CONTRACT

Production package with confirmed scope

The package is activated for a specific company according to its contract, seats, permissions and validity period.

WEB / MOBILE PARITY

Web available, Android scope limited

The Web capability is available in contracted scope while corresponding mobile alignment continues.

WEB-ONLY

Administrative or management capability

The capability belongs to configuration, analytics, import, contracts or platform administration and remains on the Web.

IN DEVELOPMENT

Not a production capability

A technical or permission foundation exists, but connection, acceptance or production availability is not complete.

Available by contract

  1. 01Opearia Core
  2. 02Service Operations
  3. 03Warehouse & Inventory
  4. 04Procurement & Supply
  5. 05Casino Tech and Casino Command
  6. 06Finance Support, operations projects, automation, dynamic fields and workflow extensions within confirmed scope

Access control

  1. 01The active package determines company capabilities
  2. 02Role and granular permissions determine allowed actions
  3. 03Scope may cover own data, team, site, partner or the whole company
  4. 04Server and database controls apply package, membership, permission and scope

Integrations in development

  1. 01Google Workspace
  2. 02Microsoft Teams
  3. 03Slack
  4. 04Jira
  5. 05WhatsApp Business
  6. 06Viber Business
  7. 07Email-to-Ticket, Enterprise SSO/SCIM and advanced ERP or accounting connectors

Android status

  1. 01The Android app exists for supported field flows
  2. 02It is not presented as a full replacement for the Web platform
  3. 03Functional parity is confirmed by package and version
  4. 04Administration, large imports and advanced management views remain Web capabilities

RELATED CONTENT

Continue the assessment without losing context.

01

PRODUCT DIRECTION

We separate available packages from integrations and mobile capabilities still undergoing development or alignment.

02

PROCUREMENT / RFP

A structured framework for business, technical, security and implementation assessment of Opearia.

03

FAQ

Clear answers about scope, implementation, security, integrations and how the product works.

Turn the content into a concrete scope conversation.

Configure a demo requestTalk to sales