Local Linux hub
PrometheOS runs on the local network and provides system state, controls, project configuration, records, and administration.
PrometheOS for education
A shared platform for physical-computing education.
An education lab combines a local PrometheOS hub, browser-based team stations, curriculum, and shared sensors, cameras, controls, and machines.
Education lab inquiry
Lab components
A local hub, team stations, and shared equipment.
The hub manages the system, stations provide hands-on access, and shared equipment supports cameras, identity, audio, robotics, and environmental projects.
Team workstations
Small groups connect low-voltage inputs and outputs, define the behavior, test the result, and document revisions.
Shared equipment
Cameras, RFID readers, robots, audio systems, and environmental sensors support modules that require larger or shared hardware.
Browser interface
Browser-based access to a local hub.
Students can use classroom computers, Chromebooks, or tablets to open PrometheOS over the local network. The interface exposes assigned hardware, configuration, live state, controls, and project records.
Team A
Touch → logic → light
Team B
Test → observe → revise
Local network
PrometheOS
Typical learning cycle
Build, observe, document, and revise.
The same cycle is used for guided introductory work and increasingly independent projects.
-
01
Open
Sign in and see the team's tools in one place.
-
02
Build
Choose a real need, connect the parts, and decide what should happen.
-
03
Try it
Work safely, press the button, and watch the real result.
-
04
Document
Show what the team chose, saw, learned, and wants to change.
-
05
Revise
Use what happened to make the next version even better.
Educator role and support
Educators define context, safety, and learning goals.
Educators select the project context, establish safe working limits, structure teams, and assess the technical process. PrometheOS provides the shared environment, reference projects, and system records.
- Plan Define the lab layout, network, equipment, and supervision model
- Teach Use the curriculum sequence and reference implementations
- Maintain Keep replacement components and recovery procedures available
- Expand Add stations and shared equipment as requirements change
- Support Use optional updates, learning resources, and training
Deployment sizes
Pilot, classroom, and applied-invention configurations.
Programs can begin with a focused set of stations and add equipment, curriculum, and training as requirements change.
Start
Pilot Lab
Smaller groups, demonstrations, libraries, and initial school trials.
Build out
Classroom Innovation Lab
Multiple team stations, shared equipment, curriculum, and training.
Extend
Applied Invention Lab
Advanced programs, capstones, technical academies, and makerspaces.
Lab configurations
Three baseline configurations.
Each configuration includes PrometheOS and is adjusted for learner age, group size, available space, equipment, and program goals.
Small configuration
PrometheOS Pilot Lab
For smaller groups, demonstrations, libraries, and initial school trials.
- One configured PrometheOS control center
- A focused set of physical-computing stations
- Introductory curriculum and reference projects
- Educator orientation and deployment support
Recommended
PrometheOS Classroom Innovation Lab
A complete classroom setup with one shared control center, multiple student stations, shared equipment, curriculum, and training.
- A dedicated local PrometheOS control center
- Multiple team-based physical-computing stations
- Shared cameras, access, robotics, sound, and sensing tools
- Curriculum, guided projects, educator training, updates, support, and community access
Advanced programs
PrometheOS Applied Invention Lab
For advanced high-school programs, career education, colleges, makerspaces, and technical academies.
- Expanded hardware fleet and advanced shared equipment
- Applied capstone and prototyping pathways
- More training, launch planning, and support options
- Replacement, replenishment, and expansion planning
Local ownership and operation
Installed equipment and core software remain at the school.
The school owns its installed equipment, software, and purchased learning resources. The core classroom system does not need a cloud subscription to keep working.
Optional services can add updates, new learning resources, priority support, and more training whenever the program wants them.
Project information
Questions about an education lab?
Provide the learner age range, program setting, available space, equipment needs, and intended learning outcomes.