Intelligence Without Limits

We build the intelligence layer
your business runs on.

Ontilus designs and engineers bespoke AI operating systems for complex, multi-entity operators. We turn fragmented operational data into one live source of truth — and one engine that tells your leadership what to do next.

  • 12 weeksPilot to group-wide
  • Multi-entityHard data isolation
  • PDPA & GDPRAligned by design

Engineering AI systems for multi-entity operators worldwide

Telekom Malaysia Omnicom Media Group Sunway Medical Centre Mindvalley Eternity Healthcare Hara Fitness Top 30 Media Next Level Academy
Built on SupabaseAWSFirebaseGoogle CloudApple iOS

Capabilities

Four things every
Ontilus system does.

Real-time telemetry

Live operational streams — transactions, inventory, labour, finance — unified across every legal entity and reconciled against your own close reports.

  • Webhook & sync-agent ingestion
  • Legacy and on-premise systems included
  • Source-of-truth reconciliation

Predictive engines

Demand forecasting, pricing optimisation and variance detection that run before the day starts — not after it ends.

  • 7-day demand & revenue forecasting
  • Cost and price variance alerts
  • Automated resourcing & purchasing plans

The decision engine

It answers the daily why and recommends the next best action. A strategic partner in the business, not a static report.

  • Daily briefing, written for the reader
  • Root-cause on every variance
  • Ranked, costed recommendations

Enterprise architecture

Role-based access, entity-level isolation and audit-ready logging — designed from day one for regulated, multi-company groups. Built in Malaysia, for groups running several entities on separate systems.

  • Scoped by entity, brand and site
  • Full change history on every record
  • Isolated VPC, regular key rotation

The Ontilus platform

One intelligence layer.
Every system you run.

We don't hand over a dashboard and leave. We build the layer that sits between your operations and your decisions — on your data, in your entity structure, under your governance.

AI engine Automation Data intelligence Security first
Explore the systems
Your business

Applications

Command centers · Agents · Workflows · Executive views

Our platform

Ontilus AI engine

Reasoning · Memory · Forecasting · Recommendation

Data intelligence layer

Identity graph · Telemetry · Analytics · Reconciliation

Secure cloud

Infrastructure

Isolated VPC · Encrypted · Audit-logged · Regional

The systems we build

Two systems.
One operating system.

Every engagement is bespoke, but almost all of them resolve into these two — and they're designed to fuse into a single engine. The Command Center below is shown answering four different sectors' questions; the figures are illustrative, the modules are what stay constant.

System 01

The Command Center

Real-time operations, AI decisioning and executive intelligence on one live surface — from the front line to the board pack.

Live demo

Net revenue — today

RM 428,650

▲ 6.2% vs target

Orders

7,412

▲ 3.1% WoW

Average order value

RM 57.83

▲ 2.9% WoW

Stores above target

24 / 33

9 need attention

Gross margin by channel

Cost intelligence · target 42.0%

Own stores44.1%
Own e-commerce46.2%
Marketplaces38.6%
Wholesale35.4%

Margin & stock alerts

Detected in the last 7 days

  • +9.4% Landed cost, core range Supplier 04
  • 18 SKUs below reorder point 6 best-sellers
  • +1.5% Marketplace fee change two channels
  • 42 Lines under 60% sell-through season 3

Stock is uneven, not short — 6 of the 18 shortfalls exist in another store

Morning briefing

Decision engine · generated 06:00 · for the Retail Director

Revenue is 6.2% ahead of target, but the mix is moving toward your two lowest-margin channels. Two actions are worth taking today.

  1. 01

    Rebalance stock before reordering

    Six of the eighteen shortfalls are sitting in a store that is not selling them. Transferring costs freight; reordering costs freight and working capital.

    Est. impact +RM 38,000 working capital · confidence high

  2. 02

    Reprice the 42 slow-moving lines now

    Sell-through has been under 60% for six weeks. Marking down in-season recovers more than clearing at end of season, and the model puts the break-even at week nine.

    Est. impact +RM 61,400 margin · confidence medium

System 02

The Growth Agent

Unified customer intelligence and an engine that runs engagement on its own — so retention stops depending on who remembered to send the campaign.

Customer intelligence

A single 360° profile per customer, patient, student or client — one identity across every entity you operate.

  • Unified profiles across all brands
  • Engagement frequency & value patterns
  • Preference and service-note fields
  • VIP, corporate and household tagging

Engagement automation

Journeys that fire themselves, on time, every time — with consent tracked per customer, per channel.

  • Milestone & renewal campaigns
  • Onboarding, loyalty & referral journeys
  • Lapsed-customer win-back journeys
  • WhatsApp, email & SMS, fully automated

Market intelligence

External signal measured against internal return — so marketing spend is judged on contribution, not impressions.

  • Competitor pricing & trend tracking
  • Review & sentiment monitoring
  • Social, influencer & campaign performance
  • CAC, repeat rate and lifetime value

Fused with the Command Center, operational and customer data become one predictive engine.

Ask the system

Answers the daily why.

Your team already asks these questions. Today the answer takes three days and four spreadsheets.

ontilus · decision engine scope: group · all entities

How we deploy

Live in 12 weeks.
Proven before it scales.

Four phases, in the same order every time. Nothing goes group-wide until it reconciles against numbers your finance team already trusts.

  1. Weeks 1–3

    Discovery

    Where the pain actually is

    • Sit with the teams doing the manual work and map the real process
    • Audit every source system, including the legacy and on-premise ones
    • Agree the success measures and the data we'll validate against
  2. Weeks 4–6

    Build

    Implementation and iteration

    • Stand up the data layer and connect the first live feeds
    • Build the interfaces and automations agreed in discovery
    • Review working software with you weekly and adjust as we go
  3. Weeks 7–10

    Test & activate

    Fix, tune, then switch on

    • Reconcile every figure against your own reported numbers
    • Fix defects and tune the models on your real data, not sample data
    • Train the people who'll use it daily, then activate by team
  4. Weeks 11–12

    Hypercare

    We stay on it after go-live

    • Daily monitoring with a named engineer while adoption settles
    • Same-day turnaround on anything that blocks the work
    • Handover pack, run book and an agreed steady-state support model

What makes it land

Standardise the taxonomy. One naming convention across every system before we integrate.

Appoint one champion. A single internal owner for data validation, not a committee.

Three metrics first. Teams learn performance against target, cost on the day, and critical alerts. Everything else follows.

Security & governance

Built for companies
that get audited.

Multi-entity groups don't get to be casual about data. Separation, consent and audit trails are architecture decisions here, not settings we add later.

Transparent running costs

You'll know your monthly operating cost before you sign — inference, infrastructure and integration, itemised and sized to your actual transaction volume. Confirmed at technical scoping, not estimated after go-live.

AI / LLM inferencesized to usage
Cloud infrastructure & storagesized to scale
Integration & middlewaresized to estate

End-to-end encryption

TLS 1.3 in transit, AES-256 at rest, across every service.

Role-based access

Scoped by entity, brand and site. People see their scope, nothing else.

Entity-level isolation

Hard separation between legal entities — not a filter on a shared table.

Audit-ready logging

Full change history on every record and every access event.

PDPA & GDPR aligned

Consent tracked per person, per channel. PII minimised by default.

Isolated infrastructure

Private VPC, regular key rotation, regional data residency.

Questions

The ones we
get asked first.

If yours isn't here, ask us directly. We answer scoping questions before there's a contract in sight.

Talk to us
What exactly does Ontilus build?

Bespoke AI operating systems. In practice that means a live data layer over your existing systems, predictive engines on top of it, and an interface your team actually opens every morning — plus the automations that remove manual work underneath. We're not reselling a product; we architect and build for your entity structure.

How is this different from a BI dashboard?

A dashboard reports what happened. Our systems explain why it happened and recommend what to do about it, then execute the parts that can be automated. The difference shows up in the morning briefing: a ranked, costed list of actions instead of twelve charts and an interpretation problem.

Do you work with our existing systems?

Yes — including the awkward ones. Where a system has webhooks or an API we integrate directly. Where it's on-premise or legacy we deploy local sync agents and batch ETL. Most groups we work with run three or four different systems across their entities, and that's the normal starting point, not a blocker.

How long until we see something real?

Discovery runs three weeks, and you see working software from week four, reviewed with you weekly from then on. Twelve weeks to a live group-wide system, followed by hypercare. We deliberately validate against numbers your finance team already reports before anything scales — it's slower on paper and far faster in reality, because nobody has to unpick a bad rollout.

Who owns the data and the system?

You do. Your data stays in infrastructure scoped to you, with residency where you need it. Commercial terms on the codebase are agreed up front — we'll tell you exactly what you own before you commit, not after.

What does it cost to run?

Monthly operating cost breaks into three lines: AI inference, cloud infrastructure, and integration middleware. We size all three against your actual transaction volume during technical scoping and give you the number before you sign — including how it grows as you add sites.

Let's build
what's next.

Tell us what's slowing your operation down. We'll show you what the system would look like running on your data — before you commit to anything.

Book a demo

See it running on
your operation.

Tell us where the friction is. We'll come back within one business day with a walkthrough built around your data model — not a generic deck.

hello@ontilus.com

Your details go to the Ontilus team only. No list, no sequence.