Teach IoT hands-on. Real technology. Build skills that transfer.

HARDWARIO Academy helps educators take learners from a physical event to a working dashboard through the TOWER stack—using technologies they can meet again in advanced study, internships and engineering careers.

Plan learning pilot Visit Store

SCHOOL

Secondary and high-school learning

UNI

University labs and project pathways

ADAPT

Adapted upper-primary activities

DIY

Independent maker learning

WHY HARDWARIO ACADEMY

A real device-to-dashboard path, shaped for learning.

Career-reusable technology

Learners work with technologies and concepts that remain useful in further study, technical projects and engineering work—not an education-only dead end.

A complete system

Connect embedded hardware, firmware, radio, messaging, automation, time-series data and visualization so learners can explain how the whole system works.

Educator-ready progression

Start with a guided activity, state the prerequisites, and expose deeper layers progressively. The educator remains in control of the learning goal, timing and supervision.

Pilot to repeat use

Define one useful lesson or lab, review the evidence, then expand across classes, subjects, semesters or educator teams when the pilot works.

WHO ACADEMY SERVES

Structured education for institutions. Independent learning for makers.

The audience changes the depth, delivery model and next step. It does not change the underlying commitment to authentic IoT learning.

Secondary and high schools

Hands-on lessons, laboratories and projects for informatics, physics, electronics, automation and interdisciplinary STEM.

Universities and higher education

Practical labs and project foundations for embedded systems, IoT, automation, mechatronics, data engineering and teacher education.

Upper-primary and basic schools

Age-appropriate introductory activities with explicitly adapted depth, duration, tooling, supervision and assessment.

Structured learning programs

STEM labs, clubs, after-school programs and training providers with a named facilitator, cohort and learning objective.

Education partners

Schools, universities, regions and funders building a defined program with clear roles, evidence and a route beyond a one-off event.

DIY and makers — self-service

A project-led, self-service route through the TOWER stack overview and the Store rather than a school sales journey.

Compare learning paths

THE TOWER STACK

Real technology from the device to the dashboard.

The TOWER learning path connects eight layers into one coherent system learners can inspect, explain and extend. HARDWARIO Academy grew out of BigClown, the original name of today's HARDWARIO TOWER kit.

Embedded hardware

STM32 low-power microcontrollers

Learn with a real MCU family and encounter power-constrained embedded design concepts.

Embedded software

Rust + Embassy

Explore modern memory-safe embedded development and asynchronous firmware architecture.

Host tooling

Rust CLI host ecosystem

Use inspectable, scriptable developer tooling instead of a closed education-only application.

Device communication

Secure sub-GHz radio

Understand constrained wireless communication and include security in the system model.

Messaging

MQTT

Move device events through a broadly applicable publish-and-subscribe model.

Flow and integration

Node-RED

Connect messages, logic and services while making system behavior visible.

Time-series storage

InfluxDB

Store and query measurements and events as they change over time.

Visualization

Grafana

Build dashboards and interpret operational data in a professional visualization environment.

Each activity states the layers it covers; we confirm released hardware, curriculum coverage, prerequisites, accounts, local services and support with you before your school or university commits.

INSTITUTIONAL JOURNEY

Start with a defined learning outcome, not a box of hardware.

A useful pilot makes the learner, educator, environment and evidence explicit before delivery.

01
FRAME THE LEARNING GOAL
Name the cohort, subject, outcome, timetable, educator and the TOWER stack layers learners should understand or use.
02
VALIDATE READINESS
Confirm the released configuration, computers, installation rights, network access, local services, supervision, preparation and support boundary.
03
PILOT, REVIEW, EXPAND
Run a scoped lesson or lab, review learner work and educator experience, then decide whether to repeat or expand it.

LEARNING PATHS

Choose the path by learner level and outcome.

SCHOOL PATH

Secondary or high school

A pilot lesson, practical lab or project path for a named class and subject.

Named educator and learner cohort
Age-appropriate device-to-dashboard depth
Prerequisites and assessment agreed before delivery
A review and repeat-use decision

Plan school pilot

UNIVERSITY PATH

University or higher education

A lab, coursework or project foundation with deeper access to the TOWER stack.

Course or laboratory outcome
Rust/Embassy and host-tooling depth as scoped
Messaging, storage and visualization path
Evidence suitable for repeat course delivery

Discuss university lab

ADAPTED PATH

Upper-primary or structured program

An explicitly adapted introduction for younger cohorts or facilitated non-formal learning.

Depth and duration adapted
Supervision and safeguarding made explicit
Exact tools and educator preparation
No assumption that secondary material fits unchanged

Scope adapted pilot

PLAN WITH CONFIDENCE

Teach on the released path — we make sure of it with you.

Academy connects learning goals with current technical truth. Before your class commits, we go through release status, exact prerequisites and curriculum coverage together — nothing rests on assumption.

TOWER STACK

Eight-layer overview

Review the canonical device-to-dashboard path used for every new Academy learning activity and program brief.

Explore the stack

RELEASE READINESS

Activity prerequisites

Every readiness check covers release, configuration, prerequisites and TOWER stack coverage — ask us about any guide and we confirm what it covers.

Discuss readiness

PROGRAM DESIGN

Pilot or curriculum conversation

Bring a cohort, learning objective and date. We will frame the smallest useful pilot and identify what must be validated.

Plan a pilot

CURRENT AVAILABILITY

Store

Check the currently listed TOWER components and configurations before planning a self-service build or equipment purchase.

Visit Store

INDEPENDENT LEARNING

Building for yourself? Take the maker path.

Build at your own pace — the maker path is self-service. Pick a project with a stated release, exact configuration, prerequisites and TOWER stack coverage, and you know before you buy exactly what you will build and what it needs. If a guide does not state these, ask before you start.

Explore TOWER stack Visit Store

Start with a reproducible outcomeChoose a project that states its exact components, software, release status and expected first result.
Understand the complete pathTrace the build through the relevant STM32, Rust/Embassy, radio, MQTT, Node-RED, InfluxDB and Grafana layers.
Keep the support boundary honestUse docs and community resources first; request guided help only when a defined training or support offer exists.

FREQUENTLY ASKED QUESTIONS

Questions to resolve before a pilot.

A trustworthy scope is more useful than a universal promise.

Which institutions are the best fit?

Academy starts with secondary and high schools through practical lessons, labs and projects. University departments can use deeper laboratory and project pathways. Upper-primary and basic schools are welcome when depth, duration, tooling, supervision and assessment are adapted.

What technology does the TOWER path use?

STM32 low-power microcontrollers, Rust with Embassy, a Rust CLI host ecosystem, secure sub-GHz radio, MQTT, Node-RED, InfluxDB and Grafana. A specific activity may cover only a subset — its scope says exactly which layers.

Must every educator or learner start by writing Rust firmware?

No. A prepared entry activity can hide some complexity, while advanced work progressively exposes Rust/Embassy firmware and Rust CLI tooling. The required depth and prerequisites are agreed for the cohort.

What computers and software are required?

It depends on the activity. The readiness check may include the Rust toolchain and CLI, Node-RED, InfluxDB, Grafana, local services, accounts, network access and installation rights. These requirements are stated before delivery.

Is TOWER safe for classroom use?

Standard classroom activities use low-voltage, solder-free assembly. Normal supervision, age guidance and the requirements of the exact activity still apply; this is not a claim of zero risk.

Are all hardware, curriculum and support options available now?

We confirm availability, curriculum coverage and support for the exact offer you discuss with us — and we announce features, dates, certifications and support horizons only once they are verified.

Where should DIY builders begin?

Review the TOWER stack and current Store listings first. Use a self-service project only when it explicitly states its current-stack compatibility, bill of materials, prerequisites, release status and support boundary.

Which languages are supported?

Academy marketing is available in English, Czech, German, Slovak and Polish. Learner material, educator material, live delivery and support languages must be checked separately for each offer.

Ask about your program

EDUCATION COMMUNITY

Schools and universities in the Academy community

FOR SCHOOLS, UNIVERSITIES AND PROGRAMS

Plan the smallest useful IoT pilot.

Tell us who will learn, what they should understand or build, who will facilitate, and when you want to run it. We will use that brief to identify the learning path, readiness checks and an honest next step.

Plan pilot

Or call us directly

+420 775 159 734