Telegram mini apps · n8n · industrial control

Automation that keeps runningafter we hand it over

We build the systems that carry a business day to day: a till that lives inside Telegram, a publishing queue with a human in it, a cold room that wakes someone at 3am. 108 workflows in production right now — and we run most of them ourselves before we sell them to anyone.

Phnom Penh, Cambodia · remote worldwide for software, on site for hardware

automation workflows in production
108automation workflows in production
Telegram mini apps shipped
6Telegram mini apps shipped
social platforms published to
8social platforms published to
unattended monitoring
24/7unattended monitoring
Products

Software your staff already know how to open

Both of these run as Telegram mini apps. No app store, no install, no separate password, no tablet to replace when it dies behind the bar.

Services

Automation for work, premises and home

Three divisions, three very different environments, one requirement: it has to keep working when nobody is looking at it.

Custom sensor module on a workbench
Bespoke

When off-the-shelf will not do it

When nothing off the shelf fits, we design the board, write the firmware and integrate it with everything else you run.

  • Custom sensor module design and fabrication
  • PLC programming and industrial control panels
  • API bridges between systems that were never meant to talk
  • Telegram bots and mini apps as the front end to anything
  • n8n workflow design, review and rescue
All services
How we build

Four rules we do not bend

Most automation horror stories come from breaking one of these.

A human approves anything public

Automation that posts in your name without review will eventually embarrass you. Every publishing path we build has a person in it.

Authorisation server-side

Hiding a button is not a permission model. Admin actions are refused at the API by role, so a poked-at request fails the same as a poked-at UI.

Alerts find the person

A dashboard nobody opens is not monitoring. Alarms escalate to Telegram until a human acknowledges them.

It runs on your infrastructure

Your server, your database, your credentials, your documentation. Our involvement should be a choice you keep making, not one you cannot unmake.

Process

Four steps, and you can stop after any of them

  1. 01

    Conversation

    A call or a Telegram thread about what actually goes wrong in your week. No discovery invoice.

  2. 02

    Fixed scope

    A written scope with a price against it. If the honest answer is that automation is not worth it here, you get that instead.

  3. 03

    Build

    Built in the open with something to look at early. You see it working before it is finished.

  4. 04

    Handover

    Documentation, credentials in your name, and a walkthrough. You own it whether or not we keep working together.

Work

We run this stack ourselves

Both case studies below are our own venues. Nothing here is a pilot we talked someone else into.

All case studies
Writing

From the workshop

All posts

Tell us what keeps going wrong

A conversation costs nothing and often ends with us saying automation is not worth it for a given job. That is a useful answer too.