Canonical: https://kleidos.dev/overview/cores3-se/ Updated: 2026-11-04 1. [Overview](https://kleidos.dev/overview/) 2. M5Stack CoreS3 SE Overview # Kleidos on the M5Stack CoreS3 SE Kleidos turns the M5Stack CoreS3 SE into a password manager: it keeps your passwords encrypted on the board and types them into your computer over Bluetooth, after you unlock it on the board itself. The firmware costs nothing and asks for no account. There is nothing to install yet: version 0.1.0 is not released. The same firmware runs on [nine boards](https://kleidos.dev/overview/#devices), and I recommend none of them over the others: this page is what the CoreS3 SE does with it. Updated 4 November 2026 1. [On screen](https://kleidos.dev/overview/cores3-se/#on-screen) 2. [Controls](https://kleidos.dev/overview/cores3-se/#board-controls) 3. [Capacity](https://kleidos.dev/overview/cores3-se/#holds) 4. [Consumption](https://kleidos.dev/overview/cores3-se/#draws) 5. [Price](https://kleidos.dev/overview/cores3-se/#cost) 6. [Status](https://kleidos.dev/overview/cores3-se/#release) ## Kleidos on its own screen Every recording here is of the CoreS3 SE's own screen, with a demonstration vault on a development build. The same recordings are on the [recordings page](https://kleidos.dev/recordings/#fleet-clips), beside those of the other boards I have filmed.  [Live from the device](https://kleidos.dev/recordings/#provenance) **Scrolling and opening by touch** On the touch model a finger drags the vault list down to the last of the six demonstration services, and two taps open it: the account is shown, the password still masked.  [Live from the device](https://kleidos.dev/recordings/#provenance) **Typing with no keys** The on-screen keyboard on a touch board that has no keys: the device-name field opened from the settings tree, five characters erased one key at a time, the same five typed back, and the name saved.  [Live from the device](https://kleidos.dev/recordings/#provenance) **A one-time code** The vault steps from its passwords to its 2FA page with one hold, and two demonstration codes stand there, each with the ring that shows how long it has left. They are real codes, computed on the device for the moment the clip was recorded.  [Live from the device](https://kleidos.dev/recordings/#provenance) **Codes renewing themselves** Two one-time codes reaching the end of their window: the rings close over the last five seconds, both codes change at once, and the rings open again on the next window. Nothing is pressed in this clip. The codes are real, computed on the device for the moment the clip was recorded.  [Live from the device · code covered](https://kleidos.dev/recordings/#provenance) **The code that opens the panel** The device's own screen while it serves the admin panel from its own access point: the vault, then the card with the join code and the name to open in a browser, then the vault again with the radio down. Nothing moves in between: the card is a screen the device holds for as long as it serves. I covered the join code itself, because it holds the access point's name, which includes part of this board's hardware address, and that session's password. Each picture's badge says how I made it, and [the legend of the badges](https://kleidos.dev/recordings/#provenance) explains every kind. - Live from the device - Live from the device · code covered ## What each control does Each row quotes what the CoreS3 SE itself shows for that control: on the pages it shows the first time it starts, or in the bar at the foot of its vault list. **A tap** What the board says it does: “select” **A swipe up or down** What the board says it does: “scroll” **A swipe sideways** What the board says it does: “change tab” **The A mark below the screen** What the board says it does: “PREV” **The B mark below the screen** What the board says it does: “SELECT” **The C mark below the screen** What the board says it does: “NEXT” **A tap on a row, then another** What the board says it does: “Tap a row, tap it again to open” **The power button** What the board says it does: “Press power to lock” I will write a guide to every screen, board by board, once the interface stops changing. ## What it holds, and how it keeps time The vault is the same on every board. What changes with the board is how much it holds, how it keeps time for the one-time codes and where its backups go. **Chip** ESP32-S3 **Input** Touch screen **Screen** 320×240 **Case** 54×54 mm **Capacity** 500 credentials, 50 two-factor codes **Clock** Battery-backed chip **Card slot** Yes: it writes its own backups ## What it draws from its battery What the CoreS3 SE draws in each state, as the [measurements page](https://kleidos.dev/measurements/#boards) prints it, with what each state is and how each figure was taken. ### M5Stack CoreS3 SE I give no battery estimate for it: its power controller has no current reading, and its cell comes in an optional base module, so without that base there is no battery to estimate. I publish no unlock time for it yet. **Asleep** not yet **Light sleep** not on this board **Normal use** not yet **Wi-Fi** not yet **Bluetooth** not yet Switches off at its power controller, which stays awake to switch it back on, and draws while it waits. ## What it costs Kleidos costs nothing: there is nothing to buy from the project and no account to make, and the firmware is free software under [GPL-3.0-or-later](https://www.gnu.org/licenses/gpl-3.0.html). What you pay for is the board. **Price** US$38.90 **Listed by** [M5Stack's own store](https://shop.m5stack.com/products/m5stack-cores3-se-iot-controller-w-o-battery-bottom) **Product code** K128-SE **Read on** 1 November 2026 That is what the maker's own store asked on the day I read it, before shipping and taxes. Resellers ask their own, and the price moves. ## Where the firmware stands Kleidos is pre-release, at version 0.1.0: there is nothing to install yet, and [the roadmap](https://kleidos.dev/roadmap/#status) says what is left before the first release. **Version** 0.1.0 **To install** Nothing yet: no release is published **Hardened build** In development I have not had the firmware or the cryptography reviewed by anybody outside the project; [the security page](https://kleidos.dev/security/#verify) says what you can and cannot check. - [Previous board M5Stack CoreInk](https://kleidos.dev/overview/coreink/) - [Next board M5Stack Core2 v1.3](https://kleidos.dev/overview/m5stack-core2-v13/) - [All nine boards](https://kleidos.dev/overview/#devices)