What we build with, and what that means for your IT team
This page is for IT teams, procurement, and whoever will inherit the system. If you are evaluating what the system does for your work, the other pages answer that better.
The main pieces
Each of these was chosen for the same reason: somebody has to be able to maintain this after we hand it over.
The language and runtime everything runs on
Microsoft publishes its support timeline in advance, and developers who write it are not hard to find in Thailand. If you ever want a different team maintaining this, you are not locked to us.
Every screen in the system
The logic and the data stay on the server, so your documents are not shipped to a user's machine to be processed, and modest hardware runs it fine.
Where all the data lives
If your organization already runs SQL Server, your IT team backs this up and restores it with the procedures they already have, rather than learning a new tool for one system.
Reading Thai documents into the system
Handles printed and handwritten documents, and sets aside the ones it is not confident about for a person to check before anything is committed — rather than guessing and posting quietly.
Inspection from camera images
Runs primarily on the CCTV you already have. No camera replacement, and nothing on the production line itself has to be touched.
The connection to your existing systems
Your accounting system, ERP or WMS receives the data over an API, so nobody has to re-key it from our screen into yours.
What IT teams ask
Where is the data stored?
Either your own servers or the cloud. If documents or biometric data have to stay in the country under your internal policy, we can deploy on-premise.
How do we get our data out if we stop?
It sits in a standard database your IT team can export from without going through us, and we hand over the schema on installation day rather than on the day you want to leave.
How much can our team change themselves?
Thresholds, configuration and new document layouts are adjustable from the admin screens without touching code. If every change has to go through the vendor, the system dies within the first year.
Will it connect to our accounting system?
Over an API or an import file, depending on what your current system exposes. We ask this in the first conversation, because it changes the entire scope.
Can we test before deciding?
Send sample documents so the team can confirm the assessment method, queue, timing, fees, and data handling before work begins.
What about PDPA?
Biometric data is sensitive personal data under section 26. We design for separate consent, an alternative for those who decline, and automatic deletion. We are not legal advisors, but we build systems your advisor can sign off.
What we do not do
- We do not resell someone else's software licence and call it development work.
- We do not take on work that cannot be measured. If we cannot agree on what to measure before starting, we will say it is not ready to start.
- We do not use one customer's documents to train a model used for another customer.
- We do not let the system decide things that are hard to undo without a human review point first.
