One technology base
All twenty products run the same stack: .NET 10, PostgreSQL 18, Vue 3. One response envelope, one error-code scheme, one auth model, one way to operate them. Your IT team learns it once.
In-house20 products · 4 business lines · one technology base
From the shop floor to the front counter — business systems that can grow
We do not build one giant system that does everything. We let focused systems grow on one platform: one account model, one set of integration contracts, one data-authority matrix. Start with a single system, or grow all the way into the full suite.
- 20
- in-house products
- 4
- business lines
- 6
- manufacturing systems, one platform
- 100%
- can run on-premise
Product matrix
Manufacturing SuiteSix systems, one platform
ERPResource planning
PLMProduct lifecycle
APSPlanning & scheduling
MESShop-floor execution
WMSWarehouse
SRMSupplier collaboration
Restaurant SuiteFrom the till to the pickup screen
POSTill & store ops
KIOSKSelf-service kiosk
EMENUTV menu boards
PICKUPPickup calls
SHOPStore back office
OPSChain operations
AI & AutomationAI inside real processes
NOVAFLOWAI workflow
FOKEICantonese AI service
DANFAIDocument intelligence
CAD-FAIDrawings & inspection
Vertical PlatformsIndustry rules, turned into an online service
BOOKINGOnline booking
TODOTask management
LAEDrone rental
LOTTERYProbability & backtesting
Product matrix
Four business lines, twenty products
Every line stands on its own. When you do want them connected, the interfaces, accounts and data ownership were agreed long before you asked.
6 products
Manufacturing Suite
Sign in once, use all six. Every kind of data has exactly one ledger.
ERPPLMAPSMESWMSSRM
Learn more
6 products
Restaurant Suite
One shop or a whole chain — front of house and back office together
POSKIOSKEMENUPICKUPSHOPOPS
Learn more
4 products
AI & Automation
Not a thin wrapper — the moat is the eval set, the domain data and the workflow fit
NOVAFLOWFOKEIDANFAICAD-FAI
Learn more
4 products
Vertical Platforms
Scheduling, approvals, dispatch — write the rules down first, then write the code
BOOKINGTODOLAELOTTERY
Learn more
Why RUYI
Fixing the real reason digitisation projects fall back to Excel
It is rarely "no system". It is several systems with no single source of truth and no reliable integration between them.
One ledger per kind of data
A data-authority matrix registers exactly one system of record for each data type. Execution happens in many systems; posting happens in exactly one — adding a system never adds a second set of books.
On-premise first
Every product can be deployed to your own machines and run fully offline. Where the data lives and who can touch it is your decision, not a condition of using us.
Buy as many as you need
Enable systems one at a time and add more later. Anything not enabled falls back to the base system, so a process never breaks halfway through because "we have not bought that module yet".
Technology base
Twenty products, one stack, one way to operate them
One response envelope, one error-code scheme, one auth model, one migration convention. SQL migration scripts are the single source of truth for the schema — never ORM auto-generation. Each system runs as its own service, on its own database and port.
.NET 10One backend stack
PostgreSQL 18SQL migrations are the source of truth
Vue 3 + ViteOne frontend stack
DB-per-tenantPhysically isolated tenant databases
Linux + systemdRuns on your own servers
Android / iOSStation terminals and handhelds
Solutions
Pick a combination that already works in your industry
The same base grows into different shapes. Here are six combinations we have already delivered.
Discrete manufacturing
Delivery dates are guesswork. Nobody can say where an order stands. The drawing changed but the floor is still building the old revision. Every new system adds another set of books.
Start with ERP so the ledger is under control, then add in order of pain: APS for dates you can actually hit, MES for traceable execution, PLM so nobody builds a stale revision, then WMS and SRM. Each addition registers one more data type in the authority matrix — never two places posting the same thing.
Discrete manufacturing · Products
ERP — Enterprise Resource PlanningPLM — Product Lifecycle ManagementAPS — Advanced Planning & SchedulingMES — Manufacturing ExecutionWMS — Warehouse ManagementSRM — Supplier Relationship Management
- Quote a date computed from real capacity and real material availability
- Trace every issue, pass and report back to person, machine and batch
- Inventory and payroll stay on exactly one ledger, in ERP
Restaurant chains & canteens
Queues at peak. A menu change means visiting every store. One network outage stops the whole shop. Opening a store takes a full day of manual setup.
In store: POS, self-service kiosks, TV menu boards and pickup screens to keep the front of house moving, with the store back office for menu and settings. Across the chain: the operations console for cross-store access and one-action store provisioning. Offline capability is a requirement, not a bonus.
Restaurant chains & canteens · Products
POS — Till & Store OperationsSelf-Service KioskeMenu — TV Menu BoardsPickup Call SystemShopManager — Store Back OfficeOps Console — Chain Operations
- Keep taking money through an outage; nothing is lost on recovery
- Change a price centrally and the boards follow within fifty seconds
- Open a store: database, service, domain and certificate in one run
Trade & logistics
Invoices, packing lists and bills of lading piling up to be keyed in by hand. Finding a document means searching email. Customers ask for status on WhatsApp and nobody is watching.
Document extraction turns paper and PDFs into structured data, with low-confidence fields routed to a human. The workflow platform chains review, approval and write-back into one traceable process. Cantonese AI handles day-to-day enquiries and hands off when it should not guess.
Trade & logistics · Products
DanFai — Document IntelligenceNovaFlow — Enterprise AI WorkflowFokei — Cantonese AI Customer Service
- Data entry becomes a glance and a confirmation
- Every change is attributed and timestamped
- Nobody has to sit on the phone to answer "where is my shipment"
Appointment-based services
The therapist, the room and the prepaid package all have to line up. Reschedule and cancellation rules are intricate. Someone is answering the phone all day.
The booking platform encodes dual-resource scheduling, package redemption and login-free self-service into database constraints and state machines. AI customer service absorbs enquiries and reminders; internal follow-up runs on task management.
Appointment-based services · Products
- Database exclusion constraints make double-booking impossible
- Customers manage their own bookings by phone number, no account needed
- Reschedule, cancellation and bad-weather rules are configuration, not code
Quality inspection & engineering
First-article reports are numbered by hand on the drawing, dimensions copied into Excel. A complex drawing eats most of a day, and transcription errors slip through.
Parse dimensions and tolerances directly from the vector drawing, balloon and number automatically, correct from the keyboard, export the report. Everything runs in the browser — the drawing never leaves the machine, and your IT will not see it on the wire.
Quality inspection & engineering · Products
- Most of a day becomes minutes
- Unstated tolerances filled from the standard tables
- Zero upload — drawings stay local
Low-altitude economy
Heavy drones, licensed pilots and job demand never quite line up. Flight compliance and geofencing need a system behind them. Settlement is a monthly argument.
Aircraft, pilot credentials and job orders live on one platform with dispatch and settlement per job type. Geofencing and limit-breach alerting run as a dedicated subsystem, with PostGIS behind the spatial work and replayable tracks.
Low-altitude economy · Products
- Demand and pilots matched and settled online
- Immediate alerts on breach or over-limit operation
- Every job leaves a track on file
How we deliver
Start where it hurts most — never a big-bang cutover
Solve one problem that can actually be signed off, then grow outward. Every stage has a deliverable you can accept or reject.
Site survey
We come to your floor, store or office and watch how it actually runs, then rank the pain and pick one thing that can be signed off.
Requirements blueprint
Written requirements and design: business rules, interface contracts, permissions, failure cases and the data model, spelled out and reviewed by you.
Build
Implemented against that document. SQL migrations are the source of truth for the schema. Critical logic ships with automated tests.
Pilot & acceptance
One line, one store or one department goes first, checked off against the acceptance list so problems surface small.
Rollout
Old and new entry points run side by side with a gradual switchover — never a big-bang cutover, and migrations have a rollback path.
Operations
Monitoring, backups, certificate renewal and the upgrade procedure are part of the handover, with a rollback path instead of a reinstall.
Wondering whether this fits the way you already work?
Tell us your situation, what you run today, and which part you want fixed first. You will get a concrete recommendation based on your case — not a product brochure.