English in. Hardware in motion.

Describe the result. Let AI handle the build.

Tell PrometheOS what your device should do, in plain English. Connect a compatible ESP32, let the AI handle the code and configuration, then follow the wiring instructions to bring your idea to life.

PrometheOS Linux host connecting distributed ESP32 nodes, sensors, motors, cameras, and browser controls
One local host. Small nodes. All your hardware.

How it works

One computer runs it. Small nodes reach the hardware.

A Linux host runs the system. ESP32 nodes connect hardware wherever you need it. A browser gives you one place to build, watch, and control it.

  1. 01BrainLinux control center

    Runs the whole system locally.

  2. 02ReachESP32 nodes

    Connect hardware where it lives.

  3. 03HardwareInputs and outputs

    Sensors, controls, motors, and more.

  4. 04ControlBrowser interface

    Describe your idea, follow the setup, and watch it work.

What is built in

Your idea. A complete foundation.

PrometheOS brings hardware control, rules, automation, interfaces, monitoring, and maintenance into one local platform.

01

Connect hardware

Connect a workbench prototype, a room full of devices, or a machine with moving parts.

  • GPIO, I²C, relays, sensors, and connected actuators
  • Motors and servos with safety interlocks and watchdogs
  • Touch, analog, motion, and environmental sensor workflows
  • Gamepad and controller mappings for devices and sequences
02

Automate behavior

Turn live device events into rules, schedules, sequences, and safe repeatable actions.

  • Manual timers and recurring schedules
  • Timeline sequences with loops and conditions
  • Event-driven rules across devices, timers, and sequences
  • Locks, pause controls, snapshots, and safety history
03

Add identity and vision

Let people, cards, cameras, and visual markers start the right response.

  • Users, roles, permissions, access levels, and schedules
  • RFID credentials, readers, and event logging
  • QR, ArUco, and barcode-triggered workflows
  • Local object, package, pose, face, and subject triggers
04

Make it seen and heard

Use sound, speech, screens, and signs to tell people what the system is doing.

  • Audio libraries, queues, repeat, outputs, and volume
  • USB media, text-to-speech, and voice announcements
  • Voice commands that trigger devices and actions
  • Smart signage, display channels, reels, and event interruptions
05

Control rooms and equipment

Watch the conditions around a project and control the equipment that responds.

  • Thermostat and HVAC profiles, schedules, holds, and safety controls
  • Network-presence triggers for online and offline devices
  • Alarm actions using audio, speech, and notifications
  • I²C OLED and LED display setup, testing, reset, and bus recovery
06

Keep it running

Find problems, restore backups, update devices, and keep the system useful over time.

  • Searchable records, timelines, and CSV or JSON exports
  • Backup, restore, configuration import, export, and migration
  • Runtime, hardware, camera, scan, and worker diagnostics
  • Node discovery, pairing, claims, provisioning, and firmware updates

The basic loop

Sense. Decide. Act. Keep a record.

Take in a signal, check your rules, run the right action, and save what happened. The same loop works across every kind of hardware.

01

Take in signals

Connect sensors, buttons, cameras, cards, voice, and network devices. PrometheOS sees every change as it happens.

  • Sensors, buttons, touch, cameras, cards, and voice
  • Live signals, status, and event history
02

Make things happen

Turn on a light. Open a lock. Move a motor. Play a sound. Control every output from the same system.

  • Lights, locks, climate, motors, sound, and screens
  • Single actions, full sequences, and safety interlocks
03

Set the rules

Choose what should happen, when it should happen, and what must be true first. PrometheOS handles the rest.

  • Rules, conditions, and sequences
  • Schedules, timers, permissions, and safeguards
04

Give people control

Use a browser, screen, sound, speech, or alert to make the system easy to control and understand.

  • Messages, sounds, voice, alerts, and live controls
  • Roles, permissions, and interfaces for different people
05

Keep it yours

Run the core system locally. See what it is doing. Repair it, back it up, and keep changing it as your project grows.

  • Local control with no required cloud subscription
  • Clear history, health checks, backups, and recovery

When something changes

Every signal follows a clear path.

A signal arrives. PrometheOS checks the conditions you set, runs the right action, and keeps a record you can inspect later.

  1. 01SeeA sensor, switch, card, camera, voice command, or network event changes
  2. 02CheckLook at conditions, permissions, timing, safety rules, and system state
  3. 03ChooseUse the behavior you set for that event
  4. 04ActDrive a relay, motor, display, light, audio output, or notification
  5. 05RememberSave the event, response, and system state for later

Cameras

See something. Start something.

A code, object, person, package, or pose can start an action, save an event, or tell someone what happened. Vision runs as another input to the same local system.

  • Use a visual marker to trigger an exhibit, machine, or workflow.
  • Recognize a package or object and notify the right person.
  • Keep camera events and system responses in one history.
Camera recognizing a code and triggering a physical-system response
Vision becomes an input to the system.

Smart access

Know who can use what.

Connect cards, readers, people, permissions, and schedules to doors, cabinets, tools, machines, or other shared equipment.

  • Use RFID credentials as a dependable physical input.
  • Define who can use equipment, when, and under what conditions.
  • Keep a clear history of every request and result.
Access card opening an approved cabinet and saving the event
Credential input, permission check, output, and event record.

Sound and voice

Make every action clear.

Use sound, speech, screens, and voice commands to tell people what is happening—or let them control the system without touching a screen.

  • Play clips, prompts, alarms, announcements, and generated speech.
  • Use voice commands as a hands-free input where they make sense.
  • Coordinate sound with motion, screens, lights, and alerts.
Voice input and audio feedback connected to a physical system
Inputs and outputs people can understand.

Environmental systems

Monitor conditions. Control equipment.

Connect temperature, humidity, air-quality, water, motion, and other environmental sensors to the equipment that responds. Build a greenhouse, heating system, safety monitor, HVAC controller, or something original.

  • Monitor changing conditions in a live, inspectable system.
  • Drive fans, pumps, heaters, lights, or other equipment automatically.
  • Detect leaks, faults, and unusual changes early.
Temperature, humidity, water, and air sensors reporting to PrometheOS
Environmental inputs and equipment outputs in one system.

Robotics and motion control

Build machines that sense, decide, and move.

Connect gamepads, sensors, cameras, motors, and servos. Add movement limits, safety interlocks, and watchdogs. Use PrometheOS for a prototype or as the local control layer inside your own robot.

  • Combine perception, decisions, motion, and human control.
  • See what the machine noticed and why it responded.
  • Change, repair, and extend the system as the idea evolves.
Robot connecting cameras, distance sensors, motors, and human controls through PrometheOS
Perception, control logic, motion, safeguards, and history.

Yours by design

Run it. Understand it. Keep it working.

PrometheOS gives you control of the data, hardware, behavior, maintenance, and future of the system you build.

Keep data and control local

Run the core intelligence locally and choose what, if anything, leaves your network.

Use parts you can replace

Understand the system, replace failed hardware, and service it without a sealed dependency.

Connect what you build

Add original hardware, change the behavior, and keep improving the device after version one.

See the whole story

Inspect live status, decisions, failures, actions, and history.

Software licensing

Personal use is included. Commercial use needs a license.

Buy a PrometheOS product and use the software for personal projects. To sell, deploy, or operate it for a business, you need a paid software license for your product, team, or organization.

Local by design

Local control. No required cloud.

Run the PrometheOS control center on your own network. Open it from a browser, keep core behavior local, and avoid a required subscription or locked-down device you cannot understand.

Run
Keep the core system on your network
See
Know what is on, off, connected, or changing
Share
Give each person the right level of control
Recover
Keep history and backups close at hand
Continue
Save a project, move it, and pick up where you left off

Every project is different. We help shape the setup around its hardware, safety, privacy, and operational needs.

Start simple. Go deep.

Use the browser. Reach the whole stack.

Start with the visual interface, then go deeper when you need custom hardware, original behavior, diagnostics, updates, or recovery.

  1. SeeLive state and controls in the browser
  2. ConnectInputs, outputs, nodes, and network devices
  3. DefineYour own logic and automation
  4. ExtendCustom hardware, interfaces, and behavior
  5. MaintainDiagnostics, records, backups, and recovery

Start a project

Building something with real hardware?

Tell us what it should sense, what it should do, which hardware it uses, and where the project stands.