Add-on dossier

418-unit MNCERT/CC custom-order delivery record

A linkable lifecycle record for hardware expansions, app ecosystems, firmware upgrades, cases, radio parts, and post-event badge experiments.

Back to add-ons index

MNSEC 2025 Electronic Badge Collection manufacturer-reported completed custom order

completed delivery context

Beelog's official project page says it designed, manufactured, and developed 418 electronic badges for MNCERT CC as a custom order. The companion archive identifies MNSEC 2025 and says the work was completed, but neither source publishes ticket eligibility, recipient identities, handoff records, or evidence that all conference attendees received a badge.

Badge
MNSEC 2025 Electronic Badge Collection
Type
completed delivery context
Status
manufacturer-reported completed custom order
Compatibility
MNSEC 2025 MNCERT/CC-associated badge collection only; not a universal MNSEC admission or attendance entitlement
Source
https://beelog.tech/

Badge context

Related Resources

manufacturer project record

Beelog MNCERT CC Electronic Badge Project

Beelog's official project page states that it designed, manufactured, and developed 418 electronic badges for MNCERT CC as a custom order, including hardware, firmware, and deployment-ready work. The page does not identify individual recipients, per-unit configuration, ticket entitlement, or image-reuse permission.

Badge: MNSEC 2025 Electronic Badge Collection

public badge source archive

MNSEC2025BADGE public source archive

The public repository identifies the MNSEC 2025 electronic-badge commission, says three badge types and 418 completed units, names MNCERT/CC and Beelog Tech, and links hardware, firmware, and supporting material. It is a project archive, not a recipient ledger or blanket licence for all media.

Badge: MNSEC 2025 Electronic Badge Collection

public firmware and example-code archive

MNSEC2025BADGE firmware directory

The public directory contains a firmware binary, a named sketch, and example source folders. It does not establish a reconciled final release, source-to-unit mapping, support lifecycle, or safe operating/reconfiguration instructions.

Badge: MNSEC 2025 Electronic Badge Collection

Source trail

Evidence Sources

Beelog Technologies · retrieved 2026-05-15

MNCERT CC Electronic Badge Project

Primary manufacturer project record stating that Beelog designed, manufactured, and developed 418 electronic badges for MNCERT CC as a custom order. It does not map those units to named event recipients or selected source-media rights.

Badge: MNSEC 2025 Electronic Badge Collection

DavgaBeelog / MNSEC2025BADGE · retrieved 2026-05-15

BSD 2-Clause License

Primary repository license text. It is scoped as the archive's BSD 2-Clause source/binary statement and is not treated as automatic permission for photographs, renders, badges, branding, or a locally published image.

Badge: MNSEC 2025 Electronic Badge Collection

helicopteresdc / Beelog Tech · retrieved 2026-05-15

MNSEC2025BADGE

Primary public badge archive identifying the MNSEC 2025 commission, MNCERT/CC customer context, Beelog Tech role, three badge types, and 418 completed units. Its design archive is not treated as proof of every final delivered configuration.

Badge: MNSEC 2025 Electronic Badge Collection

helicopteresdc / Beelog Tech · retrieved 2026-05-15

MNSEC2025BADGE Firmware

Primary public source for the preserved firmware binary, named sketch, and examples. It does not establish a complete released software inventory, operational configuration, or support policy.

Badge: MNSEC 2025 Electronic Badge Collection