CTRLbot

two applications // one company control simplified. intelligence amplified.
io.ctrlbot.iot
ctrlbot llc / founded 2024 two applications shipping

We build software that translates human intent into system action. One application works out what is wrong by asking the right questions. One turns an Android phone or tablet into a complete professional AV control system. Each works entirely on its own.

signal.test() // live
cb — 001

ONE FIGURES IT OUT. ONE RUNS THE ROOM.

two halves of one problem

The world is full of connected devices. The technology is not the problem — the problem is that none of it talks to each other, and when something breaks you are on your own with a 47-page forum thread from 2014. CTRLbot covers both halves: the intelligence to work out the fault, and the hands to operate the equipment.

dv—01PROJECTORSpower / source / audio
dv—02DISPLAYS & TVSd-pad / inputs / volume
dv—03SWITCHERSvideo / audio input routing
dv—04MATRIX ROUTERSmany-to-many routing
dv—05NETWORK ENDPOINTSrs-232 + ir bridging
dv—06AUDIO-CAPABLE GEARvolume / speaker + mic mute
cb — 002

THE APP

CTRLbot IoT turns an Android phone or tablet into a standalone professional AV control system. The driver catalog ships inside the app, so it can be searched without downloading anything. Counts are from the snapshot generated 21 July 2026 and change as the catalog is revised — confirm the real equipment during live testing.

73 manufacturers / 124 drivers / 7,561 commands

The traditional path puts a processor in the rack before the room can say a word.

CTRLbot IoT configures and runs the room from a phone or tablet, installed from Google Play.

Tablet End User Interface with Input 1 routed to Display 1
Many-to-OneSeveral sources feeding one display, with the room-friendly labels set during configuration.
Tablet End User Interface routing one input to all four matrix outputs
Many-to-ManyMatrix routing across multiple inputs and outputs, including an all-outputs route.
Phone End User Interface showing source selection and volume
Same room, in a pocketThe generated interface reflows for phones. Volume and mute appear only where the gear supports them.
cb — 003

THE AI

it asks before it answers

Every mainstream assistant infers the rest of your sentence and returns six paragraphs. When the inference is wrong you have to notice it is wrong — exactly the thing you cannot do while troubleshooting something you do not understand. CTRLbot.AI interrogates first. Free, no login, and it forgets you when you close it.

question.next()

Answers you can click.

Questions arrive with their answers attached — YES, NO, and on the final question a PASS, each one explaining what that choice would mean for the diagnosis. You supply judgment, not prose.

Try it. The buttons are live.

ctrl — q.ai● asking
assumptionWindows blue-screening after an update usually means a display driver, not dying hardware. Let's find out which.
question
st—01The assumption

Within about a second it states what it thinks is going on, so a wrong turn is visible immediately.

st—02The questions

Fast YES/NO questions stream in, personalized with the brand, device, symptom and error code from your prompt.

st—03The confirmation

One sharper question whose answer buttons each explain what that choice would mean, then a playback of everything collected.

st—04The answer

Three real, non-sponsored sources and one direct answer — in the voice of an IT admin who got called in on a weekend.

cb — 004

THE LIBRARY

behind sign in

The resource side of CTRLbot. Device drivers and manuals from the DataBots catalog, the utilities we build for our own commissioning work — some of them open source — and a small shelf of gadgets. It sits behind a sign in so driver revisions can be versioned against the people using them. It is being built now.

lb—01DEVICE DRIVERS

The DataBots catalog that ships inside CTRLbot IoT, published as versioned snapshots with the command sets, transport defaults and supported-model lists visible before you download.

catalog live in-app · web access in build
lb—02MANUALS

Device documentation gathered during driver work, plus the CTRLbot IoT user manual — the same source the in-app assistant answers from.

in build
lb—03UTILITIES

The small tools we wrote because commissioning needed them. Some will be open source, published where anyone can read what they do before running them.

in build

Accounts are not open yet. Sign in exists so the shelf can be stocked before the doors come off.

cb — 005

THE COMPANY

ctrlbot llc / founded 2024

CTRLbot is a software company. It does not manufacture hardware, it does not sell a subscription, and it does not run a cloud that your room depends on. Two products ship today and each one is complete on its own — they share a company, a design philosophy, and exactly one integration point.

dst—01ctrlbot.io

The company portal. The product stories, the boundaries, the manifesto, the privacy policy.

dst—02ctrlbot.ai

The assistant itself. Not a marketing page — one text box, no login.

dst—03Google Play

Where CTRLbot IoT is downloaded and updated.

prv—01No accounts

Nothing to sign up for on the assistant. No per-seat licence on the app.

prv—02No analytics

No tracking and no advertising in either product.

prv—03Direct traffic

Device control goes straight to the addresses you configure, never relayed through CTRLbot.

cb — 006

BUILT DIFFERENT. BY DESIGN.

SIMPLICITY OVER FEATURE CREEP

PRIVACY OVER DATA HARVESTING

SOLUTIONS OVER ENGAGEMENT METRICS

we build software that translates human intent into system action.

cb — 007  // interested in what we're building? hello@CTRLbot.io