Everowl Technologies: a software studio in Malaysia building web and mobile applications, enterprise platforms, and agentic AI automation since 2018.
Selected Work
Most of what we build runs where you can't see it. A few cases, declassified.
- Case 01: ENERGY AUDIT PLATFORM. Sector: ENERGY. ERA 03 // EVOLUTION. Problem: Compliance reports fall due on a fixed schedule, rebuilt by hand each cycle from meters and spreadsheets. Nothing showed where the power went. System: They scoped a reporting tool. Metering went in first: every switchboard feeds one record, and the optimisation module acts on the readings the audit cites. Open case file.
- Case 03: LOCAL MEETING SCRIBE. Sector: IN-HOUSE. ERA 03 // EVOLUTION. Problem: Someone in every meeting stops listening in order to write. What gets written is thin, and a week later nobody can say who agreed to what. System: Sending the room to a transcription service was the easy build. What went in runs on the machine it listens from, separates the voices, and answers a mid-call question before the pause ends. Open case file.
- Case 04: PEAK DEMAND CONTROL. Sector: ENERGY. ERA 04 // BEYOND. Problem: Large sites draw from the grid and their own solar. One unwatched spike past the contracted ceiling puts a penalty on the bill, and nobody sees it coming. System: A rule engine only catches the peaks somebody predicted. What went in holds demand under the ceiling around the clock, and wakes someone only for what it cannot decide. Open case file.
- Case 12: MERCHANT LOYALTY CORE. Sector: RETAIL. ERA 01 // TRADITION. Problem: Merchants ran on one-off discounts with no way to reward the customers who came back. Nothing recorded who returned, so a regular looked like a stranger. System: Three flows and no more: enrol, earn at the till, redeem at checkout. Merchants read who comes back and how often, and set the reward rules against it. Open case file.
The Whole Stack
Everowl has been building for ten years, and the same senior unit is still doing it. Every position a complete system needs sits in-house: designed, built, shipped, and kept running by the same people.
- SOFTWARE
- 01ARCHITECT
Decides how the whole system holds together.
- 02FULL-STACK
Carries a feature from screen to database.
- 03BACKEND
Everything behind the interface: services, APIs, logic.
- 04DATA
Moves and stores what the system knows.
- 05DEVOPS
Cloud, deployment, scale on demand.
- 06AI / AGENTIC
Automation with judgment that acts, and hands you the insight.
- HARDWARE
- 07EMBEDDED
Firmware, on the board itself.
- 08HARDWARE
Boards and devices, the physical layer.
- 09NETWORK
What connects it to the rest of the world.
- PRACTICE
- 10SECURITY
Hardens it from the first commit, not the last.
- 11RELIABILITY
Watches it in production and keeps it up.
- 12DELIVERY
Scope held, questions answered, the client line open.