Simplico is a Bangkok-based engineering studio, and over the past decade that’s meant shipping a lot of different systems for a lot of different operators — an EV charging network, a durian depot, a security operations center, a factory floor. Each product started the same way: a business had an operational problem that generic software didn’t fit, so we built something that did.
This post is a tour of that portfolio — what each product actually does, and more importantly, what changes for the business once it’s running. We’ll cover the six platforms with the deepest engineering behind them, then round out the rest of the catalog.
The one-line summary
| Product | What it is | The core benefit |
|---|---|---|
| EV CSMS | White-label OCPP 1.6 charging station management | Launch a branded charging network with Thai payment rails already built in |
| simpliSOC | Open-source SOC stack (Wazuh + IRIS + Shuffle) | Real detection and incident response without per-alert vendor pricing |
| simpliSSO | Centralized identity on Authentik + Azure AD | One login, one off-boarding switch, across every internal app |
| simpliDepot | Commodity depot management (intake → invoice) | A payout price record that never gets re-argued |
| simpliRecycle | Scrap yard operations platform | Weigh-in to VAT invoice in one connected pipeline |
| MES Development / simpliFactory | Custom Python manufacturing execution systems | Real-time OEE and traceability, with source code you own |
| ERP Service | Odoo / ERPNext implementation and customization | One system of record instead of five disconnected spreadsheets |
Now the detail.
1. EV CSMS — a charging network under your own brand
Most EV charging software is built for Europe or the US, and it shows the moment a Thai operator tries to use it: no PromptPay or QR30, a support ticket queue in a different timezone, and the platform vendor’s logo on the screen your customers see instead of yours.
Simplico’s EV CSMS is a production-grade OCPP 1.6J charge station management system, white-labeled to your brand, with QR30, PromptPay, and 2C2P built into the payment layer from day one — not bolted on. A live reference deployment is running right now at ocpp-dashboard.simplico.net, so an operator can see real session data before signing anything.
What the customer gets: a charging network their own drivers can actually pay for, running under their own brand, hosted and monitored by someone who answers the phone in Bangkok when a charger goes down at 8 PM — not a ticket that sits in Amsterdam overnight.
2. simpliSOC — a real SOC without the per-seat security tax
Most SOC platforms price by alert volume or endpoint count, which means the bill grows exactly when an attack is happening. simpliSOC is a production-ready stack built entirely on open-source components — Wazuh for detection, IRIS for case management, Shuffle for automated response — tied together by a custom FastAPI integrator that handles deduplication, severity mapping, and live IOC feed refresh.
It also puts a local LLM in the loop: every qualifying alert gets a plain-language "what happened, why it fired, what to do" write-up and a true/false-positive call, generated on-premise so alert content never leaves the network — and an analyst always makes the final decision.
What the customer gets: detection and incident response coverage across firewalls, VMware, Windows AD, and endpoints, with no per-alert bill, no vendor lock-in, and the underlying rules and integrator code as something the business actually owns rather than rents.
3. simpliSSO — one login, twenty-four fewer attack surfaces
Every extra login system a company runs is an extra place a departing employee’s access can quietly survive. simpliSSO centralizes identity on Authentik, federated with the company’s existing Microsoft 365 / Azure AD tenant, so staff sign in once with credentials they already have and reach everything else — modern web apps over OIDC, legacy ERPs like Infor M3 over SAML2, even printers and hardware over an LDAP outpost.
What the customer gets: a single point of control for access. When someone joins, one Azure AD account provisions every tool they need through SCIM. When someone leaves, one deactivation revokes every session, everywhere, instantly — instead of an IT team manually checking two dozen systems and hoping they didn’t miss one.
4. simpliDepot — a payout price that never gets re-argued
A commodity depot’s hardest operational problem usually isn’t the weighing — it’s the argument three weeks later about what price a farmer was actually quoted. simpliDepot locks the per-kilo price to each lot at the moment of intake, permanently, so it becomes the record rather than a starting point for a dispute. Stock then allocates FIFO automatically when a sale is made, and buyer invoices and farmer payouts run through the same ledger with gap-free sequential numbering even when several cashiers are billing at once.
Built first for durian depots in Thailand, the underlying variety/grade/price model isn’t hardcoded — it applies just as well to mango, rubber, or any other weighed, graded commodity.
What the customer gets: traceability from a specific farmer’s lot to a specific buyer’s invoice, a pricing record that closes disputes instead of starting them, and a depot that can keep growing past the point where a paper logbook or a shared spreadsheet quietly breaks.
5. simpliRecycle — weigh-in to VAT invoice, one pipeline
Scrap yards run on the same core loop as commodity depots — buy by weight and grade, hold in inventory, sell, invoice correctly — with the same failure mode when it’s run on paper and spreadsheets: misquoted prices at the gate, stock nobody notices aging in the yard, and an accountant losing two days at month-end reconciling invoices against what actually crossed the scale.
simpliRecycle runs the whole loop as six connected applications sharing one source of truth: weigh-in with a live QR mirror the supplier can watch on their own phone, A/B/C grading with price snapshotting, FIFO inventory with alerts on stock sitting 22+ days, collision-free lot and invoice numbering even with multiple weighers working at once, and VAT-aware invoicing built for how Thai tax requirements actually work.
What the customer gets: a yard where a transaction is entered once and flows downstream automatically — no month-end reconciliation fire drill, no aging stock nobody caught, and a full audit log that turns "who changed this price" from a guessing game into a lookup.
6. MES Development / simpliFactory — real-time floor visibility you own outright
Packaged MES platforms are proven, but they come with a vendor’s roadmap, a connector catalog that may not speak your PLC’s protocol, and a migration cost if you ever want to leave. Simplico’s MES development service builds a custom Python system around the factory as it actually runs — event-driven, ERP-agnostic (SAP, Odoo, ERPNext, or custom), reading whatever the shop floor speaks (Modbus, OPC UA, Siemens S7) — with a 12-week pilot from kickoff to first real OEE numbers, and the full source code, schemas, and runbooks handed over at the end, not held back as leverage.
What the customer gets: real-time visibility into machine state and OEE within three months, a system that can extend as far as the business needs because it’s not boxed in by a vendor’s feature list, and no migration bill waiting at the far end if the relationship with Simplico ever ends.
The rest of the catalog
Alongside the six flagship platforms above, Simplico builds and maintains:
- ERP Service — Odoo and ERPNext implementation, customization, and migration, plus custom ERP builds from scratch on Django and Docker where an off-the-shelf system doesn’t fit.
- simpliShop — a made-to-order, multilingual e-commerce platform built for the Thai market, with a real-time inventory and AI-assisted product discovery.
- simpliGym — gym and fitness studio management, from membership billing to class scheduling.
- IMCS / simpliFactory — captures readings straight off Mitutoyo/U-Wave and other shop-floor instruments, routes and validates them against tolerance, and feeds real-time SPC and ERP — replacing the caliper-to-Gemba-sheet-to-spreadsheet chain that fails every audit.
- TAK Integration — bridges drones, CCTV, and sensors into the TAK (ATAK/WinTAK) ecosystem, and — built by the same team behind simpliSOC — converges cyber detections and physical incidents onto one operational picture for defense, public safety, and critical-infrastructure operators.
- simpliEdge — edge and distributed computing development for latency-sensitive or offline-tolerant workloads.
- React Native mobile development — cross-platform apps with real-time updates and push notifications, usually built as the driver- or staff-facing layer on top of one of the platforms above.
What integration looks like for one organization
Most organizations that come to Simplico don’t end up running just one product. A manufacturer adopting simpliFactory usually also wants simpliSSO so shop-floor logins aren’t a separate headache; a depot or EV operator with staff and drivers usually wants a mobile app; and once more than one system is running, someone eventually asks simpliSOC to watch all of it. The diagram below shows the reference shape that integration typically takes.
flowchart TD
SSO[simpliSSO identity layer] --> ERP[ERP Odoo or ERPNext]
SSO --> MES[simpliFactory MES]
SSO --> DEPOT[simpliDepot or simpliRecycle]
SSO --> SHOP[simpliShop storefront]
SSO --> EVCSMS[EV CSMS]
ERP --> MES
ERP --> DEPOT
ERP --> SHOP
ERP --> EVCSMS
MES --> SOC[simpliSOC detection]
DEPOT --> SOC
SHOP --> SOC
EVCSMS --> SOC
ERP --> SOC
SSO --> SOC
MOBILE[React Native apps] --> DEPOT
MOBILE --> EVCSMS
MOBILE --> SHOP
- simpliSSO sits at the identity layer. Every other product authenticates through it instead of maintaining its own separate user table.
- The ERP acts as the system of record. Order, inventory, and customer data flow out to whichever domain platform needs it — simpliFactory on the shop floor, simpliDepot or simpliRecycle at the intake point, simpliShop at the storefront, EV CSMS at the charging network.
- simpliSOC sits above all of it, watching logs and access patterns across every layer rather than being bolted onto just one system.
- React Native mobile apps form the client layer wherever a driver, weigher, or customer needs a phone screen instead of a desktop one.
This isn’t the only way to combine them — running a single product on its own is just as common — but it’s the shape that tends to emerge once a business is running more than one.
The pattern underneath all of it
Look across the list and the same shape repeats: a real-world operational flow — weigh in, grade, sell, invoice; log in, verify, grant access; detect, triage, respond — gets modeled as a single connected pipeline instead of a set of disconnected tools stitched together with spreadsheets and hope. That’s true whether the domain is EV charging, security operations, or a scrap yard. The engineering underneath differs; the design principle doesn’t.
If one of these looks like it fits a problem the business is currently running around rather than through, describe the workflow, the volume, and the timeline, and Simplico will turn that into a scoped proposal — typically within 48 hours.
Get in touch: hello@simplico.net · Phone: (+66) 97 496 6397 · WhatsApp: +66 83 001 0222 · LINE: iiitum1984
Latest Posts
- Inside simpliRecycle: How a Six-App Pipeline Runs a Scrap Yard from Weigh-In to VAT Invoice August 29, 2026
- Using Small Language Models to Detect Cyber Attacks from Wazuh Logs and Firewall Syslog August 26, 2026
- How to Make Odoo or ERPNext Faster Again: A Practical Performance Troubleshooting Guide August 24, 2026
- Passkey Enrollment Is Your New Attack Surface: What Pass-the-Passkey Means for Your IdP August 22, 2026
- Your Attacker Might Already Be an AI Agent: What the OpenAI–Hugging Face Incident Means for Your SOC August 17, 2026
- Implementing ERPNext: A Practical Guide to the System, Its Document Model, and Core Workflows August 15, 2026