Bring the work that's scattered across Excel, LINE, email and paper leave forms into one place.
The employee registry is in one file, time & attendance in another, leave forms on paper. Nobody knows which file is the latest version.
A leave request goes in and then goes silent. You have to walk around asking one person at a time, and management can't see where the bottleneck is.
Laptops, phones, company cars. An employee resigns and the item disappears — there's no check-out / return history.
One HR system, another for service tickets, another for room booking — then you sit down and connect them afterwards.
Not a marketing claim — this is the list of modules that actually exist in the system.
| Work area | Core capabilities |
|---|---|
| Employee and org data | Employee registry, departments, positions, org chart, multiple manager types, auto-generated employee IDs |
| Time & attendance | Check in / check out with GPS coordinates, work shifts, rotating schedules, holiday calendar, time correction requests |
| Leave | Leave types, leave entitlements, automatic leave balance calculation, carry-over, leave requests, leave cancellation requests |
| Overtime (OT) | OT policies, multipliers by day type and time window, hour caps, OT requests |
| Approval workflows | Multi-step workflow templates, conditional approval rules, approval dashboard, my pending approvals |
| Self-service | Employees clock in, request leave, request OT, submit resignations, check leave balances and view their own documents |
| Employee documents | Employee document storage, multi-file upload, document expiry dates |
| Company assets | Asset registry, check-out / return, asset history, asset dashboard |
| Facilities | Meeting room registry, online room booking, double-booking prevention, housekeeping notifications |
| Service work / ITSM | Internal service tickets (IT Service Desk), field engineer tickets, Lab Room, work checklists, sign-off signatures |
| Customers & credit | Customer registry, service contracts, top-up and per-period credit, credit ledger, contract expiry alerts |
| Internal service requests | Engineer → procurement routing, procurement line items, SLA tracking |
| Dashboards and reports | Company overview, leave summary, attendance/absence summary, OT summary, activity calendar, Excel export |
| Notifications | Automatic email (Thai/English) and in-app notifications |
| Security | JWT login, per-menu and per-action permissions (RBAC), audit log |
What Excel simply cannot do — rules are enforced at submission, not caught at period close.
The system checks the balance after deducting items already pending approval. If it isn't enough, it says so and shows the entitlement, carry-over and days already used.
It adds approved hours to pending hours, then blocks any submission that would exceed the daily, weekly or monthly cap.
1 credit is deducted per ticket automatically. A customer who runs out of credit can't open a ticket until they top up.
It checks for overlap with confirmed bookings, blocks backdated bookings, and enforces a 30-minute minimum.
Every approval workflow in the system pulls approvers straight from this structure — you never have to set up approvers again in each module.
The system measures the distance from the allowed point. Outside the radius the check-in fails, and it reports the actual distance against the allowed distance.
Define leave types with any conditions you need — half-day or hourly leave, paid or unpaid, maximum per year, days of advance notice, how many days carry over — plus entitlement conditions by gender, employment type and minimum length of service.
The formula the system actually uses
The balance never drops below 0, and items still pending approval are already set aside — so employees can't submit beyond their entitlement in the first place.
Build templates from the screen and add, remove or reorder steps yourself. The approver at each step can be one of 3 kinds: direct manager, department head, or a specific named person.
Tickets in 3 modes: Internal (IT Service Desk), External (field engineers at customer sites) and Lab Room, with 5 job types and 5 urgency levels.
Asymmetric keys with refresh tokens · a password change is forced on first sign-in · password reset by email with token verification.
Permissions are defined as {subject, action} pairs · one user can hold several roles · enforced on both the web front end and the API — hiding a menu is not enough.
An audit log with a screen for reviewing history, and every request tracked across services with a Correlation ID.
Every core data table is tied to a company, preventing data from crossing between organizations — a good fit for groups with several legal entities.
Cloudflare R2 / S3-compatible, scales without limit and doesn't consume app server disk space.
Containers run as a non-root user, and security headers are set on the web server.
What the system does not support in the current version — written down here so it doesn't create the wrong expectations in real use.
No re-keying needed. The system imports employees, departments and positions from files, with a column matcher that saves a format for reuse (Import Mapping). It also imports time data from your existing scanner, and customer data as an upsert keyed on customer code with a per-row error report.
The system is designed as multi-tenant, with every core data table tied to a company at the database level, not just filtered in the application. One user can hold several roles, and system-level roles are separate from company-specific roles.
You can change it yourself from the screen, with no code. Add, remove and reorder steps, and set conditional rules for which case uses which workflow, based on department, named employees, leave type and amount ranges.
Not yet. Today the payroll module is at the level of salary component setup — earnings/deduction structures, tax rates and basic configuration. Full payroll calculation and payslip generation is not supported yet. We suggest talking to our team about the roadmap.
Check in and check out from a phone with GPS verification. You can set several check-in points (office, branch, customer site), each with its own radius. Outside the radius the check-in fails and the system reports the actual distance against the allowed distance, and a check-in at a customer site uses that customer's grace time instead of the shift default.
Pricing is based on the size of your organization and the modules you switch on. The main variables are headcount, which modules you use (HCM only, or HCM + ITSM), the number of group companies, migration of your existing data, and training. Please contact sales for a quote.
Book a walkthrough with our Thai team — no cost and no commitment.
Real people, Mon–Fri 9:00–18:00