Skip to content
  • New: asasii S2 handheld barcode scanner. 1D and 2D, IP52 rated.View S2
  • asasii POS is live and deploying to Malaysian retailers.See asasii POS
  • asasii BSC: supply chain software for multi-outlet operators.See asasii BSC
  • Browse the full asasii hardware line: terminals, printers, scanners, payment, drawers.View hardware
idataraya
idataraya

Engineered. Deployed. Operated.

We design, build, deploy, and operate enterprise software across data, cloud, AI, commerce, and connected hardware. One engineering team, accountable from first architecture workshop through live operations, for systems your business runs on every day.

Five disciplines. One team. Every layer.

Data and intelligence. Cloud and DevOps. Product engineering. Commerce systems. Connected hardware. idataraya delivers across all five under one accountable team, from first design workshop through live operations.

Seven phases. One accountable firm.

Hover any phase to see how we work that stage of an engagement.

Plan.

A signed plan sets the tone.

Scope, objectives, stakeholders, and timeline captured in a charter you can sign. No discovery theatre, no open-ended SOW. The plan you approve is the plan we ship to.

  • Scope charter
  • Stakeholder map
  • Phase timeline
Scope Charter
v1.0 · Signed
ScopeStakeholdersTimelineApproved
Project
Multi-outlet POS rollout · 14 stores
Objectives
  • Unified POS across all outlets
  • Live inventory sync to ERP
  • Daily sales dashboard by store
Out of scope
Loyalty, ecommerce sync
Success criteria
< 2s txn · 99.9% uptime
Ops lead · R. HassanIT · M. TanFinance · A. Kumar
SignedR. Hassan2026-04-12

Analyze.

Anchor every decision in evidence.

Field research at the counter, in the warehouse, with the operator. Time-and-motion on every step, a map of the systems they actually use, and the numerical proof of where time leaks out.

  • Field research
  • Current-state audit
  • Gap & time-loss model
Current-State Findings
Shift · 08:00–16:00
5 steps2 gaps1 broken linkEx. 12 shifts
StepSystemTime lost
Order · POSCounter
RekeyManual entry+12 min
Stock checkBack office
ERP syncNo link+36 min
Day-end bookFinance
Total lost
~48 min / day
≈ 200 hrs / year

Design.

Research first. Wireframes second. Code third.

Information architecture from the user's day, not the engineer's data model. Wireframes reviewed with the people who'll touch the screen. Visual design earns the right to exist after the flow works on paper.

  • IA & user flows
  • Wireframe review
  • Visual & interaction spec
Counter Flow · v3
3 comments · 2 resolved
SelectFrameTextField researchCashier · Manager
POS · Checkout
Cart list
Payment tray
Cash
Card
QR
Receipt
Cart · 3 items
RM 42.80
CASH
CARD
QR
Artboard · Checkout v3
N
Nadia · cashier
Cash tray should be default — 70% of txns.
M
Manager · resolved
Need manager override on voids.

Build.

One team writes all of it.

Hardware, firmware, backend, web, and mobile delivered by the same engineering organisation. Pull requests cross every layer of the stack; no handoffs, no vendor finger-pointing, no integration tax.

  • Full-stack engineering
  • Continuous integration
  • Daily merges to main
build · pull requests
Sprint 14 · 4 active
AllOpenReviewMergedmain ← sprint-14
#1842POS · cash tray default
web14/14
merged
#1847Inventory sync — ERP webhook
backend12/14
review
#1851Thermal printer · ESC/POS driver
hardware11/14
open
#1853Supervisor mobile · void flow
mobile6/14
draft

Test.

We don't ship until it survives real conditions.

Acceptance suites mirror the work the operator does on a normal day. Load tests simulate 50 concurrent counters. Hardware burns in for 8-hour shifts before sign-off. Customer signs the release, not the vendor.

  • Acceptance suites
  • Load & soak tests
  • Hardware burn-in
Test Run · Release 2026-04-18
87 / 88 passing
87 pass1 fail0 skippedTotal · 17m 03s
Acceptance · POS checkout
42 pass
2m 14s
Integration · ERP sync
28 pass
47s
Load · 50 concurrent counters
16 pass1 fail
6m 02s
Hardware · printer burn-in 8h
1 pass
8h
Printer burn-in · 8h
No faults · paper advance 100%
Customer sign-offPending · 1 retry on load

Deploy.

We ship deployments, not download links.

Engineers on site at every outlet. Devices provisioned, networks validated, ERP handshakes confirmed, staff trained, on-call rotation activated. We hand over a working installation, not a dashboard credential.

  • On-site rollout
  • Staff training
  • Go-live support
Rollout · Cohort 1
2 live · 1 installing · 1 queued
StoresDevicesTrainingGo-live window · 2026-04-18
KL-01Flagship · Pavilionlive
Live · 09:12
KL-02KLCC · L4live
Live · 10:38
KL-03Mid Valleyinstalling
Provisioning
PJ-011 Utamaqueued
Scheduled · 14:00
Go-live checklist
  • Devices provisioned · 22 of 22
  • Network validated at counter
  • ERP handshake confirmed
  • End-to-end txn validated
  • Staff training · handover

Operate.

The people who wrote the code debug it.

24/7 monitoring on the metrics that actually predict failures. P95 latency, error rate, transaction throughput. Incidents land with the engineer who built the system, not a tier-1 queue. Iterative improvement continues for the life of the engagement.

  • 24/7 monitoring
  • On-call incident response
  • Iterative improvement
Live Operations · Multi-outlet retail
14 sites · 22 devices
Uptime 99.98%1 incident · resolvedOn-call · S. Kumar
p95 latency
142ms
Txn / min
318
Error rate
0.02%
p95 · last 2h
Event stream · /api
09:14:22200/api/txn · KL-01
09:14:18200/api/txn · KL-02
09:13:41503/api/erp-sync · retry 1
09:13:42200/api/erp-sync · recovered
09:12:08200/health · all stores

Every system, mapped to every industry.

Each solution is one element. The strip at the bottom of every card shows which industries it serves. Hover an industry to trace it across the matrix.

Choose your industry. Six sectors we know deeply.

Each with engagements tailored to the operating model, workflows, and constraints of the segment.

One engineering team. Accountable from the first architecture workshop through live operations, for the systems your business runs on every day.

Built here. Shipped here. Supported here.

One engineering organisation owns the architecture, the build, the deployment, and the operation. The people who wrote the code answer the pager.

One firm. Every layer of the stack.

Hardware, firmware, backend, web, and mobile are designed and delivered by a single engineering team. Accountability stays with the people who built the system, not a chain of vendors and sub-contractors.

HardwareTerminals · printers · scanners
FirmwareECR · printers · QR
Backend & APIsPipelines · integrations
Web dashboardReporting · ops
Mobile appiOS · Android

Engineered for the market you operate in.

DuitNow, FPX, Touch 'n Go, GrabPay, and Pos Laju are integrated natively for Malaysian operations. The same engineering approach extends to regional payment rails, languages, and regulatory frameworks as your footprint grows.

RM 248.00Order #A-2619
Choose payment method
DuitNow QR
FPX Online banking
Touch 'n Go eWallet
Cards
ENBMAll rails native, not plugin

Delivered as a working system, not a deployment ticket.

Each engagement concludes with a production system installed on your premises, integrated with your existing operations, and operated by trained staff. We transfer a working installation, not a dashboard credential.

Deployment · Outlet KL-03Live
  • Devices provisioned4 terminals
  • Integrations configuredECR · Xero · WMS
  • Staff trained12 cashiers
  • On-call rotation active24/7

Accountable past go-live, for the full lifecycle.

Post-launch monitoring, incident response, and iterative improvements are handled by the same engineering team that delivered the system. Operational context is retained end-to-end, reducing mean time to resolution and preserving institutional knowledge.

Incident resolved18 min
POS-4112Receipt printer timeout after firmware push
PagerDutySentry · Outlet KL-03 · P2
00:00
AH
Ahmad · wrote the driverOn it. Reverting firmware.
00:04
AH
AhmadFix deployed. Printer back up.
00:18

Discovery consultation.

Describe the system under consideration and the operational context in which it runs. Submissions are reviewed directly by an engineer. Applicable scopes include custom platforms, data pipelines, integration services, hardware-adjacent systems, and enterprise-grade internal tooling.

What happens next

  1. 01Engineer replies within one Malaysian business day.
  2. 0230-minute discovery call. No deck, just scope.
  3. 03Written brief outlining scope, constraints, feasibility.