BDH Corporation

The starting point of Secure Edge AI.

We build the path an AI model takes to reach a device. Each model is checked in training, delivered securely and run on the chip that collects the data. Our first venture is BENTO.

Why we exist

What if intelligence installed like a song?

Today a finished model still needs an engineer to export it, integrate it into the firmware, rebuild and reflash, and the work repeats for every device.

Where it is made

Create and train

Applications are designed in the BENTO IDE. Models are trained on data the board recorded itself, then checked by gates that nobody can silently waive.

How it travels

Deliver

Found in the Edge AI Store and sent from the browser to the board its owner chose, without reflashing the firmware.

Where it runs

Run

One PSOC™ Edge E84 chip with its own NPU and three sensors on the board. It can go inside any product a designer builds.

The BENTO architecture

The five parts of BENTO, connected in a loop.

Each part of BENTO, from the firmware on the chip to the device on the wall, was built to pass a model safely to the next. Scroll to follow one model around the loop.

01 · Foundation

BENTO Secure Firmware

The foundation on the chip. BENTO firmware runs as three parts on the two Arm® cores of Infineon PSOC™ Edge E84: the Cortex®-M33's TrustZone secure world, its application world that acts as the brain, and an AI core, the Cortex®-M55 on FreeRTOS, that runs several Edge AI models at once on the Arm® Ethos™-U55 NPU. Application developers build on top of it in the BENTO IDE. A few lines of Python choose the models and read their results, with no C code.

  • TodayEach sound or motion model carries its own signal settings, so adding a model never means new firmware
  • TodayThe board checks each model against what its sensors really deliver, and refuses a mismatch with the reason
  • TodaySeveral models share the one NPU as a saved scene, which starts again by itself after a power cut
  • TodayStart, confirm and end levels for each class turn raw scores into events, each reported once with its duration
  • TodayOn the BENTO HMI Kit, a delivered model opens only on its own board, and the board proves its identity over mutual TLS, provisioned at delivery
  • TodaySecure boot and signed-model verification, switched on in every BENTO device we deliver
Firmware details

02 · Learn

BENTO Edge AI Trainer / DEEPCRAFT™ Studio

Models are trained and judged here. Each step of the workflow runs by itself; where a choice has to be made, AI agents choose among options the engine has already checked, and a person signs off where it matters. Install it on a local AI server, on your own premises or in the cloud.

  • TodayLive recording from the board over USB, with labels added as you record
  • TodayAI agents choose among options the engine has already checked, and every choice is logged and can be undone
  • TodayFourteen quality gates that are never waived, and a check against the rules the board's firmware uses to load a model
  • TodayExtensions for labelling, augmentation and data checks install from one page, run offline and start switched off
  • TodayOne command starts a trainer, with or without a GPU, on a local AI server, on premises or in the cloud. Each trainer signs the models it makes with its own key
About the Trainer

03 · Deliver

BENTO Secure Edge AI Store

Models are found here and delivered. They install like songs, scenes play like playlists, and each one goes from the browser to the board its owner chose, without new firmware.

  • TodayOn the BENTO HMI Kit, each model is sealed to the one board it is sent to, with a one-time ticket the board itself creates, over USB or the network
  • TodayGroup models into a scene, like songs in a playlist, and run them together on one board
  • TodayConnect your board and each card says whether that model will run on it, and why not
  • TodayThe Store learns a board's key only from the board itself, never from the browser
  • TodayEvery model shows the trainer that made it, and a published version never changes
  • TodayOn the BENTO HMI Kit, tick Auto Start when you send a model or a scene, and the board runs it by itself every time it is switched on
About the Store

04 · Create

BENTO IDE

Applications are made here, in the browser. Write one as a Flow, as Blocks or in Python, try it on the BENTO Emulator, ask the AI Buddy, then run it on the real board over USB.

  • TodayThree ways to write one app: wire Flow nodes, snap Blocks or type Python, with live values on the wires
  • TodayThe BENTO Emulator runs real MicroPython in the browser and draws the board's own screen, built from the firmware's own sources
  • TodayA Virtual Hardware Console of buttons, knobs, LEDs, tilt and an RGB matrix, so an app can be tested before a board arrives
  • TodayThe AI Buddy reads your connected board and explains errors in Thai or English. A reset, a file write or running code waits for your click
  • TodayRemote Flash puts BENTO firmware on a board from the IDE through a small helper app, with no toolchain to install
About the IDE

05 · Run

PSOC Edge BENTO Device

Built on Infineon PSOC™ Edge E84, a microcontroller made for devices that listen, sense and show at the same time. The BENTO HMI Kit puts a screen, radar, a motion sensor and microphones in one device, and BENTO feeds it intelligence.

  • TodayA Cortex®-M55 with an Arm® Ethos™-U55 NPU for AI, beside a Cortex®-M33 with TrustZone for the brain and the keys
  • TodayA built-in 2.5D graphics engine drives screens up to 1024 by 768 at 60 frames a second
  • TodayUp to six microphones connect directly to the chip, and several models listen and sense at once
  • TodayRuns on the BENTO HMI Kit, the TESAIoT Dev Kit and the PSOC™ Edge E84 Evaluation Kit, offline on the chip's own NPU
  • TodayHighlights: a timeline of what the board recognised and when (results only, no recordings)
  • TodayAlways sensing: once loaded, the AI keeps watching the microphones, the motion sensor (IMU) and the radar in the background on the board itself, day and night
See the device
The BENTO orbit: BENTO Secure Firmware, BENTO Edge AI Trainer / DEEPCRAFT™ Studio, BENTO Secure Edge AI Store, BENTO IDE and PSOC Edge BENTO Device, connected in a loop. 01 BENTO Secure Firmware 02 BENTO Edge AI Trainer DEEPCRAFT™ Studio BENTO Edge AI Trainer DEEPCRAFT™ Studio 03 BENTO Secure Edge AI Store 04 BENTO IDE 05 PSOC Edge BENTO Device

Then the loop starts again. The device records new data, and the next model is trained on it.

BENTO Device

Looks like a smart clock. Thinks like edge AI.

Behind the screen is an Infineon PSOC™ Edge processor, and BENTO feeds it intelligence. The board carries three sensors.

RadarPresence and motion, without a camera

IMUVibration and movement

MicrophoneThe sounds around it

A BENTO device on the PSOC™ Edge E84 HMI kit showing a clock and weather face
The same device showing its Edge AI screen with models running

From the products

A look inside the products.

Screens from the Edge AI Store and the Edge AI Trainer as they are used today. Select one to enlarge.

Not found anywhere else

Three things we could not find elsewhere.

Checked against the public documentation and code of comparable products.

Edge AI Store

A store that knows your board

Reads your board, says whether each model will run and why not, and installs it into the running MicroPython firmware from the browser, without a reflash.

BENTO IDE

Three views of one program, in one browser tab

Flow, Blocks and Python views of one program, plus an emulator of the board and the real board, in one browser tab and in Thai and English.

Edge AI Trainer

Training with its evidence attached

Release gates in every run and a check against the rules the firmware uses to load models, on your own server, in English and Thai.

How we checked

Secure by design

Every copy sealed to one owner's board.

A package made for one board will not open on any other. This is the basis for licensing a model per board rather than per file. It runs today on the BENTO HMI Kit.

In transit

Signed and sealed to one board

Encrypted to the receiving board's own key, signed by the store and carrying a one-time ticket; a package made for another board is refused.

At rest

Ciphertext on the board

Stored on the board in encrypted form, under a key that belongs to that chip alone. There is no key file to copy.

In use

Decrypted only inside the chip

Decrypted only into on-chip memory for the Ethos™-U55 NPU; a changed byte stops the model loading.

TodayRunning today on the BENTO HMI Kit. Secure boot and a closed debug port are set on every BENTO device we deliver. Until the console lock ships, code run through a board's own console can still reach a running model.

How BENTO approaches security

Scenes

One board, with a different scene for each room or line.

A scene is a set of models chosen for a place. To give the same hardware a new task on site, you change the scene and leave the firmware as it is.

Manufacturing

Vibration anomalies, drill material and whether an operator is present.

Robotics

Surface type, collision shock, human proximity.

Care at home

Fall detection, a call for help and room presence. In normal operation, only results leave the board.

Smart building

Occupancy, the sound of breaking glass, door vibration.

Energy

Transformer hum, pump vibration, site intrusion.

Smart living

Home sounds, presence and activity, room by room.

These scenes are illustrations. Some of the models are in the Edge AI Store today; others are examples. Results are for information only. They are not a diagnosis and not a safety guarantee.

A family of companies

A parent company with room for more ventures.

BDH Corporation is a parent company. Each venture runs on its own, but all of them follow the same rules: security from the chip up, only claims we can prove, and engineering that respects the people who use it.

Venture 01

BENTO

Secure Edge AI for Infineon PSOC™ Edge. Firmware, IDE, trainer, store and device form one path from an idea to a running model.

Explore BENTO

BDH Group

Bangsaen Design House

BDH Corporation is a company of BDH Group (Bangsaen Design House Group).

Principles

How we work.

Security from the chip up

Trust starts in the silicon and is carried up through every layer. We count a security feature only once it runs on a named board.

Claims we can prove

We label each feature as working today, demonstrated on the bench or still on the roadmap, and we keep those labels separate.

Data stays where it belongs

Models run on the device, and training can run on your own server. Only results need to travel.

Built on open platforms

BENTO builds on Infineon PSOC™ Edge and Arm® Ethos™, and works with open platforms such as the TESAIoT Foundation, so what you build is never locked to us.

Built on and works with

Infineon PSOC™ Edge E84 Arm® Cortex®-M55 · Ethos™-U55 Infineon ModusToolbox™ Models from Infineon DEEPCRAFT™ Studio TESAIoT Foundation by TESA

Work with us

Four ways to work with BENTO.

BENTO is made to be used, built on and backed by people everywhere. Choose the way in that fits you, and your message comes straight to us.

Developers, schools and universities

Learn and build

Write an app in Flow, Blocks or Python, try it on the emulator and run it on a real board. Labs can train their own models on their own server.

Product companies

Put AI in your product

Train on your own server, seal each model to one device, and add new abilities after the product is in your customers' hands.

Chip makers and distributors

Bring BENTO to more silicon

BENTO runs today on Infineon PSOC™ Edge. Its IDE, trainer and store give a microcontroller family a complete path from an idea to a running model.

Investors

Back the sovereign edge

We are building BENTO for the long term and welcome investors who believe AI should belong to the people and places that use it.

Images: NASA, ESA, CSA, STScI, NOIRLab/NSF/AURA and the EHT Collaboration. Star map: NASA/Goddard Space Flight Center Scientific Visualization Studio, Gaia DR2 (ESA/Gaia/DPAC). Cropped, resized and recoloured for this page. Used under CC BY 4.0 or as US public domain; no endorsement is implied.

Image credits
  • Deep Star Maps 2020 (sky): NASA/Goddard Space Flight Center Scientific Visualization Studio; Gaia DR2: ESA/Gaia/DPAC (public domain, source)
  • M31 · Andromeda Galaxy: Bill Schoening, Vanessa Harvey/REU program/NOIRLab/NSF/AURA (CC BY 4.0, source)
  • M33 · Triangulum Galaxy: T.A.Rector (NRAO/AUI/NSF and NOIRLab/NSF/AURA) and M.Hanna (NOIRLab/NSF/AURA) (CC BY 4.0, source)
  • M51 · Whirlpool Galaxy: NASA, ESA, S. Beckwith (STScI), and The Hubble Heritage Team (STScI/AURA) (CC BY 4.0, source)
  • M104 · Sombrero Galaxy: NASA/ESA and The Hubble Heritage Team (STScI/AURA) (CC BY 4.0, source)
  • NGC 1300 · Barred Spiral Galaxy: NASA, ESA, and The Hubble Heritage Team (STScI/AURA) (CC BY 4.0, source)
  • ESO 350-40 · Cartwheel Galaxy: NASA, ESA, CSA, STScI (CC BY 4.0, source)
  • HCG 92 · Stephan’s Quintet: NASA, ESA, CSA, and STScI (CC BY 4.0, source)
  • M42 · Orion Nebula: NASA, ESA, M. Robberto (Space Telescope Science Institute/ESA) and the Hubble Space Telescope Orion Treasury Project Team (CC BY 4.0, source)
  • NGC 3324 · Cosmic Cliffs, Carina Nebula: NASA, ESA, CSA, and STScI (CC BY 4.0, source)
  • M16 · Pillars of Creation: NASA, ESA, CSA, STScI; J. DePasquale, A. Koekemoer, A. Pagan (STScI) (CC BY 4.0, source)
  • M57 · Ring Nebula: NASA, ESA, and C. Robert O’Dell (Vanderbilt University) (CC BY 4.0, source)
  • NGC 7293 · Helix Nebula: NASA, NOAO, ESA, the Hubble Helix Nebula Team, M. Meixner (STScI), and T.A. Rector (University of Alaska Anchorage/NSF NOIRLab) (CC BY 4.0, source)
  • M1 · Crab Nebula: NASA, ESA and Allison Loll/Jeff Hester (Arizona State University); acknowledgement: Davide De Martin (ESA/Hubble) (CC BY 4.0, source)
  • 3C 461 · Cassiopeia A: NASA, ESA, CSA, STScI, D. Milisavljevic (Purdue University), T. Temim (Princeton University), I. De Looze (University of Gent) (CC BY 4.0, source)
  • M45 · Pleiades: NOIRLab/NSF/AURA/T.A. Rector (University of Alaska Anchorage), R. Cool (University of Arizona) and WIYN (CC BY 4.0, source)
  • M13 · Great Globular Cluster in Hercules: T.A. Rector (University of Alaska Anchorage) and H. Schweiker (WIYN and NOIRLab/NSF/AURA) (CC BY 4.0, source)
  • Sgr A* · Milky Way black hole: EHT Collaboration (CC BY 4.0, source)
  • M87* · Black hole in M87: EHT Collaboration (CC BY 4.0, source)
  • AS08-14-2383 · Earthrise, Apollo 8 (24 Dec 1968): NASA (Public domain, source)