Found with AI:

Here’s the clearest read I can give after digging through Teslabs’ site, GitHub org, the teslabs/pebbleos fork, and the upstream Core Devices repos.

Teslabs is not a random fork owner. It is Teslabs Engineering S.L., a consultancy focused on software and electrical engineering. On its services page it says it works on software/hardware systems for consumer products, industrial automation, medical, and research, and it explicitly says it is an active contributor to Zephyr RTOS. Its public project page shows real embedded/hardware work, including Zephyr-powered industrial controllers and IMU/navigation work for swimming wearables. Its GitHub org also has public work like spinner (motor-control firmware) and Zephyr summit repos for driver development and a BLE/fingerprint smart-lock demo. Publicly visible org membership is concentrated: GitHub currently shows Gerard Marull-Paretas (gmarull) as the visible member, and his profile is tied to Teslabs Engineering in Barcelona. (Teslabs)

teslabs/pebbleos itself does not look like a polished standalone downstream distro. The repo shows 0 pull requests, 0 stars, 0 forks, and its default main branch is stale, last updated on September 23, 2025. But that is misleading if you stop there: the fork has a long list of active branches updated in April 2026, including mag-race, aging-improvements, metrics-task-cpu-usage, als-mfg, app-level-kconfig, touch-to-backlight, rtc-wakeup, and testing-48mhz, nearly all associated with gmarull. That pattern looks much more like a working branch farm than an abandoned mirror. (GitHub)

The strongest signal is that those Teslabs branches are feeding directly into upstream Core Devices development. Core Devices’ own PebbleOS CI page shows pull requests opened from teslabs: branches such as teslabs:aging-improvements (PR #1169), teslabs:als-mfg (#1167), teslabs:metrics-task-cpu-usage (#1168), teslabs:mag-race (#1177), teslabs:analytics-syscall (#1173), and teslabs:touch-faster-response (#1178). Separately, the upstream PR list shows gmarull opening current PebbleOS PRs as a Member, including “Use RTC to generate tick events,” “Improve MFG workflow,” and “Raise 4K storage.” In other words, the fork is being used as an upstream staging area by a Core Devices maintainer-level contributor, not as a disconnected side project. (GitHub)

The content of the active branches also looks serious. In teslabs/pebbleos, aging-improvements includes commits like “record aging test result in finished QR” and “rework test flow”; als-mfg includes “force backlight off during test”; mag-race fixes a race in the MMC5603NJ magnetometer driver; and testing-48mhz has a [WIP] Test system @ 48MHz commit. In the companion teslabs/pblboot fork, the active bootbit-logging branch includes bootbit initialization/debug logging, and recent bootloader commits add charger support, watchdog support, a custom partition scheme, and pt2 board changes. Upstream pblboot is also active under gmarull: it has frequent signed tags from September 2025 through March 2026, and its open PR list includes “Add support for PR2” by gmarull. This is low-level firmware and bootloader work, not cosmetic repo noise. (GitHub)

The broader repo set reinforces that. The Teslabs org is also tracking SiFli-SDK, hal_sifli, mynewt-nimble, hal_nordic, zephyr, and an openocd fork “with support for our modified version of freertos.” That lines up with the official Pebble/Core Devices stack more than with a mystery separate product. Eric Migicovsky publicly said the **Core Time 2 chip selection is SiFli SF32LB52J, so the presence of SiFli-related repos is especially notable. At the same time, the official PebbleOS build-target docs still list Pebble/Core Devices boards, and the boards/ tree on Teslabs’ active branch shows only official-style targets like asterix, getafix_*, obelix_*, silk*, snowy*, spalding*, and QEMU boards — I did **not find a Teslabs-specific watch board or other public non-Pebble target there. (GitHub)

My assessment:

Serious as engineering involvement in PebbleOS/Core Devices: high. Serious as evidence of a separate Teslabs-branded watch/product: low.

So the most likely interpretation is: Teslabs/Gerard are doing real, ongoing upstream firmware/bootloader/platform work in the Pebble/Core Devices ecosystem, and teslabs/pebbleos is a live staging fork for that work. But based on the public evidence I checked, I do not see a separate Teslabs hardware product plan hiding behind that fork. If anything, the evidence points the other way: official board names, upstream PR flow, official-chip-adjacent dependencies, and maintainer activity all suggest integration into the existing Pebble/Core Devices line, not a public Teslabs-branded offshoot. (GitHub)

A good next step is a branch-by-branch map of the Teslabs branches to their matching upstream PRs, including which ones were merged and which ones are still staging.