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

AI & ML Systems.

From model development to production deployment.

We build ML systems that serve predictions in real time, retrain on schedule, and degrade gracefully when the model is wrong. Recommendation engines, demand forecasting, anomaly detection, and classification, deployed as services with monitoring, versioning, and rollback. The hard part isn't the model, it's everything around it.

  • End-to-end ML pipelines from training to serving
  • Model versioning, A/B testing, and rollback
  • Feature stores and training data management
  • Model monitoring with drift detection and alerting
demand-forecast · v3Auto
WhenInventory level drops below reorder thresholdSKU-4721 · KL-West
Then
  1. 1Predict demand7-day window
  2. 2Check supplierlead time · 3d
  3. 3Draft PO120 units · MYR 3,840
  4. 4Notify buyerSlack · #ops
92% precision · 0 false alarms this week
serving · ab-gate · v3 vs v2Shadow → 10% → 50% → hold
Running
Shadow5d · no impactScore+2.1% precisionGateCI > 95%Promoteawaits 5d hold
Rollback in seconds · not a meeting
demand-forecast · train v3Data → features → fit → register
Running
Datav82 snapshotFeaturesstore · 142Fitlgbm · trial 18Registermodel.v3
Reproducible · 82 trials logged
feature-store · demandMaterialized
sku_velocity_7dOnlinep99 · 12ms rows
promo_pressureOnlinep99 · 18ms rows
season_indexOfflinebatch rows
stockout_riskDerivedlambda rows
One definition · train + serve

Models that serve.

Building a model is a weekend project. Building a system that trains, validates, serves, monitors, and retrains that model reliably is the actual work.

Training pipelines reproducible to the commit.

Dataset versioned, hyperparameters tracked, experiments logged. Every model serving traffic can be rebuilt from the exact code and data that produced it, months later if the auditor asks.

demand-forecast · train v3Data → features → fit → register
Running
Datav82 snapshotFeaturesstore · 142Fitlgbm · trial 18Registermodel.v3
Reproducible · 82 trials logged

One feature store for train and serve.

The features a model sees in serving are the same ones it learned on. No training-serving skew, no transformation forked between notebook and service, no features that work in dev and fail at the counter.

feature-store · demandMaterialized
sku_velocity_7dOnlinep99 · 12ms rows
promo_pressureOnlinep99 · 18ms rows
season_indexOfflinebatch rows
stockout_riskDerivedlambda rows
One definition · train + serve

Drift watched, damage avoided.

Input distribution, prediction distribution, and precision against ground truth all tracked. The moment the model stops earning its output, alerts route to the team that can retrain or roll back.

Model health · demand-forecast v3
Input drift · velocitySLO <0.150.08
Prediction distributionSLO baselinenominal
Precision · 7d rollingSLO >0.880.86
Coverage · live scoringSLO >99%99.7%
Retrain triggers watched · not hoped for

New models earn traffic, they don't claim it.

Candidate versions shadow, then take 10 percent, then 50 percent, against a statistical gate. If a version regresses, traffic flips back in seconds, not after a postmortem.

Rollout · v3 vs v2
Shadow · 100% trafficno business impact
5 days
Live · v3 at 10%+2.1% precision
3 days
Live · v3 at 50%gate · CI > 95%
ongoing
Live · v3 at 100%awaits 5d hold
queued
Rollback in seconds · not a meeting

An ML system in production.

  • Training pipeline

    Automated, versioned training pipeline with experiment tracking, dataset versioning, and reproducible builds.

  • Serving infrastructure

    Production model serving with auto-scaling, health checks, and graceful fallback, deployed on your cloud.

  • Monitoring dashboard

    Model performance tracking with drift detection, prediction distribution monitoring, and alerting on degradation.

  • Operations guide

    Retraining procedures, rollback steps, and incident response for the team that operates the ML system after handover.

Ready to talk about ai & ml systems?

Book a discovery call. We will walk through how this fits your business, scope, timeline, and what you will get at the end.