AEGIS INFORMATION TECHNOLOGY LIMITED · HONG KONG

Software that leaves evidence.

We build AI systems for construction, finance and operations. Every number traces back to its source, every approval leaves a trail, and nothing is called done until it is proven.

RECORD · rec_8f2c41 VERIFIED
kindsite diary · day 47 scope2F east · slab pour proofphoto ×3 · voice 0:42 · sheet qtyconfirmed by site manager flows tovaluation #3 · line 12
Illustrative record

OUR PRINCIPLE

Make critical work traceable: with process, evidence and outcome.

Process

Every step has an owner and a state. Drafts, reviews and approvals tiered by contract value, so no work disappears into a chat thread.

Evidence

Every claim links to its source: the photo, the clause, the original file, the exact words of the person who decided.

Outcome

Numbers are computed by code, explained by AI and checked twice before anyone signs.

ONE RECORD, THREE STATES

A site photo becomes a payment line, and you can walk it back.

AI drafts the record from whatever the site sends. A person confirms it. From then on, every downstream number points back to it.

01 · RAW INPUTfrom site
0:42

“Poured the east slab on 2F today, about forty cubes, pump truck left at four.”

02 · SITE DIARYconfirmed
itemqtyunit Concrete, slab 2F-E40m³ Pump truck1shift Rebar inspectionpass—
source · voice 0:42 source · photo ×3 by · site manager
03 · VALUATION LINEtraceable
this period qty40 m³ × unit price[UNIT PRICE] retention5% price adjustmentper contract
Every figure links to diary #47

Sample data for illustration.

PRODUCTS

Five products. One standard.

01Live · Taiwan

AEGIS Construction

Site diaries to settlement, for contractors.

  • Daily diaries drafted by AI from photos, voice notes and spreadsheets, then confirmed by the site manager.
  • Confirmed quantities flow into monthly valuation, with retention and deductions applied in order.
  • Approvals follow contract value and organisational rules, with every confirmation recorded.
02Live

AEGIS Intelligence

Ask the books. Get a number you can trust.

  • Plain-language questions over your finance and operating data.
  • Code computes, AI explains. Never the other way round.
  • A second, independent path checks each answer before it is shown.
03Taiwan edition

AEGIS Bid

Tender formats you can verify.

  • Freezes the tender's required format into a contract that can be checked.
  • Verifies every clause and form word for word before submission.
  • Finds material in past bids instead of rewriting it, and flags what is still missing.
04Private deployment

AIGW

One gate for every AI call in the company.

  • Identity and tenant isolation for every department and app.
  • Content safety, usage attribution and audit on every request.
  • Routes across upstream models without changing your applications.
05Boats & off-grid

AOV

A night watch for Victron energy systems.

  • Reads your boat or off-grid system through the Victron cloud.
  • Speaks up in plain language only when something needs you.
  • Watches itself too: if monitoring stops, you hear about it.

LAB · HOW WE BUILD

We hold AI to the same rule as people.

Show the evidence, or it didn't happen. These are the tools we built to make that true inside our own engineering.

L1 · WORKLEDGERappend-only memory

Memory you can audit.

Our AI agents share one ledger. Records are only ever appended. Originals are stored with their hash. A value that changes is superseded, never overwritten, so the old one stays on record. A decision is kept with the exact words of the person who made it, and standing rules are put back in front of the agent on every turn.

srcoriginal · site-diary-2F.jpg · sha256 9c1e…stored
recdecision · “Retention is 5%, rounded to the dollar.”user-confirmed
factretention.rate · 10% → 5%superseded
rule“Follow approval rules and record every confirmation.”every turn
L2 · EVIDENCE GATESrelease discipline

No “shipped” without proof.

An agent cannot report a release as live without a recorded check against the real system. Before any deploy, we ask what production is actually running. Once, production was 34 commits ahead of the main branch. The gate caught it, so we merged first instead of overwriting work that already worked.

$ deploy
› production runs a1b2c3d
› ancestor of HEAD? no · 34 commits only in production
blocked: merge first, then deploy
L3 · MULTI-MODEL BUILD CREWparallel, adversarial

Contract first. Tests blind. Review hostile.

One lead model writes the contract. Writer models from different vendors build in parallel. Test writers work from the spec alone and never see the code. Reviewers look for one kind of failure each, refuters must reproduce a finding before it counts, and mutation tests check that the tests actually bite. Every run is logged.

Spec Contract Writers ×8 Blind tests Lens review Refuters Mutants Ledger
L4 · PHOTO TO 3Dgenerative mesh + Blender

From phone photos to a moving 3D model.

Sixteen photos of a real subject become a generated mesh. Agents rig and animate it in Blender, render frame checks and confirm the result opens cleanly, then export glTF for the web. Each version is kept with its own acceptance notes.

Photos
Generated mesh
Rig & animate
glTF on the web

SELECTED WORK

Systems our team has delivered.

Clients are not named. Each project is described by sector and scope.

AEROSPACE RESEARCH

Altitude simulation for aero-propulsion testing

Research institute

LOGISTICS

Control platform for a multimodal inland port hub

Logistics hub operator

URBAN OPERATIONS

City-scale operations and data platform

Development zone operator

TELECOM

Cloud-native infrastructure for a regional carrier

Telecom operator

TRANSPORT

Security-hardened operations for a transport network

Transport network operator

WATER

AIoT operations brain for a city water utility

Water utility group

AUTOMOTIVE · JAPAN

Unit-test checklists generated from change tickets

Systems-integration team

EDUCATION · NETHERLANDS

Course booking pilot with data kept in the EU

Language school · pilot

HOW WE DELIVER

Four steps, each one checkable.

  1. 01

    Map the work

    We sit with the people who do it and find where evidence gets lost.

  2. 02

    Prototype on your forms

    Your real templates and document formats, so the output is something you would actually sign.

  3. 03

    Deploy where data must live

    On your premises, in your cloud, or hosted in your region.

  4. 04

    Operate with proof

    Every release is checked against what production actually runs, with a backup and a rollback point first.

Bring us the work that keeps going wrong.

EMAIL

[CONTACT EMAIL]

OFFICE

Hong Kong

[REGISTERED ADDRESS]

WE WORK IN

English · 繁體中文 · 日本語 · العربية

[BOOK A CALL LINK]