We take on systems
that must not fail
Residents' internet, statutory log retention, payment collection — when these go wrong, real people are affected. So we hold every project to the same engineering rules, without exception.
WHO WE ARE
A Thai technology company
that started on site
Dewell Intelligent designs and builds network infrastructure systems, artificial intelligence platforms and management software for internet service providers, commercial residential property and enterprises.
Almost every system we make began as a problem we hit ourselves — a building owner enabling and disabling internet by hand for every move-in and move-out; an accounting team keying in hundreds of tax invoices at every month end. We don't build things that demo well; we build things that survive a full load of real users.
We work documentation-first: architecture, decision records and specifications must be settled before the first line of code. Clients end up with documentation another team can pick up or audit — not a system only its authors understand.
And we fix root causes only — no shortcuts that merely get through today, because what we ship has to keep working for years.
ENGINEERING PRINCIPLES
Six rules we
don't compromise on
These constraints apply to every project from the first day of design — they are not something bolted on after a failure.
Core service is never commercial leverage
If a licence expires or a payment fails, the management console can be restricted — but users' internet and statutory logging must not stop.
Safely repeatable, and always read back
Every command sent to a device can be re-issued without duplicate side effects, and the result must be read back and checked — never fire-and-forget.
Fail safe, not fail closed
When a subsystem breaks it must degrade into a reduced mode and alert — not take the main process down with it.
Zero silent errors
No swallowing errors quietly. Every failure is logged and propagated — a problem you cannot see is a problem you cannot fix.
Edge-first, aligned with PDPA
Personal data and traffic logs stay on the client's premises, never in a vendor cloud, with a fully separate database per building.
Security by design
Device credentials encrypted with AES-256 · licences cryptographically signed · remote support only through an encrypted tunnel.
PROCESS
What working with us looks like
01
Survey & assess
Our engineers visit the site and assess the existing network, user count and real constraints — free of charge, and we will say plainly if we think you shouldn't invest yet.
02
Design & document first
Architecture, decision records and specifications are settled before code — you see the whole picture before committing serious budget.
03
Deploy in parallel
The new system runs alongside the old one until we are confident, then we cut over — barely a visible seam, and reversible if needed.
04
Operate continuously
24/7 NOC monitoring, alerts to the on-call team within seconds, and management reporting written to be read by non-engineers.
TECHNOLOGY
The tools we choose
We pick technology proven in production that local engineers can maintain — we don't chase the new simply because it is new.
Primary language
Go
Database
PostgreSQL
High-volume data
ClickHouse
Messaging
NATS JetStream
Object storage
MinIO
Front end
React + Vite
Network devices
MikroTik RouterOS
AI compute
NVIDIA DGX Spark
Observability
Grafana + Vector
Remote access
Encrypted mesh VPN
Talk to an engineer, not a salesperson
The person you speak to is the person who will design the system — ask anything technical, and we'll be straight with you about the limits.