📖Music Technology in K-12 Classrooms — The Complete Guide
How to bring music technology into K-12 classrooms — the only guide written by people who actually ship the hardware. Standards-aligned lesson design, equipment selection, classroom management, procurement, and what works (and what doesn't) for each grade band.
Audience: music teachers, STEAM coordinators, district curriculum directors, and principals deciding whether to invest in classroom music technology. Reading time: 28 minutes (or skim the table of contents, jump to what matters). Updated: May 2026.
What this guide covers
If you're a music teacher who's been told the school is buying iPads "for music," you already know the gap between hype and what works on Monday morning. This guide is written from inside that gap. It's by Playtronica — we make TouchMe, Playtron, Biotron, and Orbita — but it isn't a sales pitch. We sell hardware; we make our money when students play. The guide is here because the questions teachers actually ask aren't answered well anywhere else online.
The full table of contents:
- Why music technology now — the case music teachers can make to administrators in 2026
- What "music technology in the classroom" actually means — the four categories, and which one matters for which grade band
- The grade-band realities — what works in K-2, in 3-5, in 6-8, in 9-12, and in conservatory / advanced settings
- Standards alignment — NCAS, UK Model Music Curriculum, NGSS, ISTE — what they want and how music tech delivers
- The equipment decision — software, hardware, hybrid, and the budget envelopes for each
- Lesson design for music tech — the 4-phase template that works whether you have 1 device or 30
- Classroom management — the specific problems music-tech lessons create, and how to solve them
- Special education and accessibility — where music tech is most under-used and most transformative
- Procurement and budget — Title IV-A, ESSER, Digitalpakt 2.0, PTA, district budget lines — what works
- Common mistakes and how to avoid them — the failure modes you can see coming
- The Playtronica approach — what we built, why, and how it differs from what's already out there
- Free starter resources — Lesson 1 PDF, standards mapping, pilot program
This guide assumes you have a music education background. It does not assume you have a technology background. If you have neither, skim Section 2 first and come back.
1. Why music technology now
The arguments for music technology in K-12 fall into four buckets. You need all four when you're presenting to a budget approver, and you only need the strongest one when you're talking to another music teacher.
The pedagogy bucket. Music technology lets students hear themselves immediately. A piano student waits months before they can play "Twinkle Twinkle." A student with TouchMe touches a banana and plays a note, the first time, within sixty seconds. That latency — between intention and audible sound — is what we mean by "low entry threshold." Low entry threshold means: more students engage. More students engage means: more music gets made. Most of the classical-music-versus-popular-music debate of the last fifty years has been about this single question. Music technology resolves it by making the question moot.
The standards-alignment bucket. The 2014 National Core Arts Standards (NCAS) explicitly require students to "use technology to capture, change, and present musical ideas." That's NCAS MU:Cr1 and MU:Cr2 across all grade bands. The UK Model Music Curriculum (2021) names music technology in KS2 and beyond. NGSS asks students to "develop and use models" — which a MIDI workflow is, exactly. ISTE 1.4 and 1.5 are tech-integration standards that music programs can claim. We cover the specifics in Section 4.
The equity bucket. Traditional music education is biased toward students whose families could buy an instrument and pay for lessons. Music technology in the classroom levels that. A student who arrives in your room with no prior music experience can produce a finished piece by the end of the period. We've seen this in Lincoln Center's family-day programs (see our Lincoln Center case study) and in Stanford's d.school workshops (see our Stanford case study). The first-touch sound is the equity moment.
The relevance bucket. The music your students listen to is made with technology. Producing TikTok loops, freestyling over beats they made in BandLab, sampling their own voices — this is what students do at home. Music programs that ignore this are training students for a music economy that ended in 2005. Music programs that embrace it are training students for the actual present.
When you're talking to a principal, lead with relevance and equity. When you're talking to a curriculum director, lead with standards. When you're talking to a fellow music teacher, lead with pedagogy. The budget argument we cover in Section 9 — that's about money, and it's a separate conversation.
2. What "music technology in the classroom" actually means
When someone says "music technology in the classroom," they mean one of four very different things. Knowing which one is being talked about saves a lot of time.
Category A: Software-only (DAWs and notation)
GarageBand, BandLab for Education, Soundtrap for Education, MuseScore. Students sit at Chromebooks or iPads, make music in the browser or app. What it's good for: composition, arrangement, song production, sequencing. What it's bad at: the embodied, kinaesthetic side of music — students stop being players and become editors. Loop-shuffling is not the same as making music with your body.
Category B: Tangible MIDI hardware (controllers and instruments)
USB MIDI keyboards, MIDI pad controllers (Novation Launchpad, Akai MPK Mini), tangible MIDI instruments (TouchMe, Playtron, Bareconductive Touch Board, Makey Makey when used for music). Students physically touch something to produce sound. What it's good for: giving every student a real-time instrument that doesn't take six months to learn. What it's bad at: standalone — hardware must connect to software. If your school's IT environment doesn't allow USB MIDI, hardware is a non-starter (rare — see Section 5).
Category C: Hybrid (hardware that does both)
Synthesizers with built-in speakers (Korg littleBits Synth Kit, Teenage Engineering Pocket Operators). Students touch the hardware AND it makes sound without a computer. What it's good for: zero-IT-burden — plug in batteries, hand to student. What it's bad at: student work isn't capturable in DAW software. Hard to integrate into a portfolio.
Category D: Coding for music (Sonic Pi, Earsketch, Scratch + music extensions)
Students write code that generates music. What it's good for: the very specific subset of students who think mathematically about music. What it's bad at: scaling — coding fluency takes time. Coding-for-music is a wonderful elective. It's not a foundation course.
For a typical K-12 classroom program, the answer is some combination of A and B. Software for the composition/portfolio side; hardware for the embodied/expression side. Hybrid (C) is great for early grades but doesn't scale to portfolio assessment. Coding (D) is an enrichment track, not the trunk of the program.
This guide focuses on A + B because that's what 90% of K-12 music programs need. We say more about how Playtronica specifically fits the B slot in Section 11.
3. The grade-band realities
What works in your room depends heavily on grade band. Here's what we've learned from working with thousands of classrooms.
K-2 (Kindergarten through 2nd grade)
Cognitive reality: five-year-olds can't read music notation, can barely operate a mouse, but can absolutely touch a fruit and hear a sound. Their first encounter with "music technology" should be purely tactile.
What works: TouchMe-style capacitive sensing (touch anything, hear sound). Playtron with alligator clips to bananas, water glasses, and aluminum foil. The lesson is: everything is an instrument. Set up four stations with different objects, rotate students through, time-budget 30 minutes total. Done.
What doesn't work: Notation apps. DAW interfaces. Anything with a menu deeper than two layers. The cognitive load of "find the right button" eats the music-making time.
Standards anchors: NCAS MU:Cn10.1.K-2 (relating music to personal experience) — touching an object you brought from home and hearing it sing is literally that. Our Lesson 1 (Touch as Conductor) is the K-2 entry point.
Grades 3-5
Cognitive reality: students can now read elementary notation, follow a 4-step process, and start thinking about "arrangement." They can use a Chromebook for ten minutes before getting lost. They can collaborate in pairs.
What works: Hardware-software hybrid lessons. Plug a Playtron into a Chromebook running synth.playtronica.com or BandLab. The Playtron is the input (students touch fruit), the Chromebook is the output (sound, recording, sharing). Lesson length: 45 minutes. Group size: pairs.
What doesn't work: Solo activities for the full period. Students this age are intensely social — make them work together and the music-making density doubles.
Standards anchors: NCAS MU:Cr2 (organising and developing musical ideas), NGSS 4-PS3 (energy transfer — fruit-as-circuit is literal energy transfer). Our Lesson 2 (Music from the Orchard) is the canonical 3-5 lesson.
Grades 6-8 (Middle school)
Cognitive reality: students are now self-aware about their music tastes. Some have started producing on phones at home. They want to make music that sounds like the music they listen to.
What works: Pattern-based and beat-based composition. Orbita is built for this — students place coloured magnets on a rotating disc, and the disc plays back the pattern. Or: students use TouchMe to control software synthesizers, layering parts. Lesson length: 60 minutes. Group size: 2-4.
What doesn't work: Notation-first approaches. Middle schoolers will respect notation if it serves their composition; they'll resist it if it precedes their composition. Lead with the music, follow with the notation.
Standards anchors: NCAS MU:Cr1.1.7 (generating musical ideas), MU:Cr2.1.7 (organising), UK MMC KS3 Compose, ISTE 1.4 (innovative designer). Our Lesson 4 (Pattern, Pulse, Sequence) is the middle school entry.
Grades 9-12 (High school)
Cognitive reality: students should be making complete works. Their music technology fluency should approach a professional baseline. They should be able to discuss their craft.
What works: Project-based learning across multiple class periods. Students take on roles (composer, producer, engineer) within a group project. Hardware becomes one input among many; portfolio assessment becomes central.
Specific high-school pattern: the accessibility design challenge. Students design a piece playable by a partner who cannot use a traditional keyboard. This is real composition practice (constraint drives creativity), serious music theory (you have to understand what notes work without keys), and meaningful empathy. Our Lesson 5 (Composing for the Body) is built around this exact challenge.
Standards anchors: Full NCAS Create / Perform / Respond / Connect strands, NCAS MU:Cn11 (synthesising), UK MMC KS4, ISTE 1.5 + 1.6.
Conservatory and advanced settings
Cognitive reality: students arrive with formal music training but often very little hands-on tech experience. They want to integrate technology into their existing practice, not abandon it.
What works: Hardware that respects their expertise. Class-compliant USB MIDI, browser-flashable firmware, integration with Max/MSP, Pd, SuperCollider, Ableton Live. Students treat the device as a research instrument, not as a toy.
This is what Hochschule für Musik Trossingen does with our hardware — see the case study. Stanford's d.school took a different angle (design-thinking framing — see their case study). Both work. The common thread: the device must be technically deep enough to reward a serious user.
4. Standards alignment — the four documents that matter
US, UK, and international schools each have their own standards. Here's what each document wants from a music-technology lesson, and how to make sure your lessons claim it.
NCAS (US National Core Arts Standards, 2014)
The four strands: Create, Perform, Respond, Connect. Each strand has process components (e.g., MU:Cr1 = generating musical ideas) and grade-level performance standards (e.g., MU:Cr1.1.K = a kindergartener generating ideas).
Music technology naturally hits:
- MU:Cr1.1 (generate ideas) — any device that lets students improvise hits this
- MU:Cr2.1 (organise + develop ideas) — sequencing software, looper hardware
- MU:Cn10.1 (relate music to personal experience) — capacitive-touch lessons that use student-brought objects
- MU:Cn11.1 (relate music to other contexts) — STEAM cross-curricular lessons
Practical move: every lesson plan you write should explicitly cite the NCAS code in the standards section. Curriculum directors love this. Document review goes faster. Our standards page has the lesson-by-lesson mapping for Lessons 1-5.
UK Model Music Curriculum (2021)
Issued by the Department for Education. Less prescriptive than NCAS — it's a non-statutory framework — but adopted by most state schools in England. Names music technology specifically in KS2 and beyond.
Music technology naturally hits:
- KS1 Listen + Experiment — capacitive sensing as experiment
- KS2 Compose — DAW + hardware composition
- KS3 Compose — pattern-based + sequencer composition
- KS4 Connect — students relating their music to traditions and technologies
Practical move: UK teachers should pair MMC citations with their Ofsted-required documentation. The MMC is the friendly framework; Ofsted wants the evidence.
NGSS (Next Generation Science Standards, US)
Music isn't a science. But music technology lessons can hit science standards too, which is the STEAM coordinator's dream:
- K-PS2 (motion + stability) — vibration is motion; sound is motion in air
- 4-PS3 (energy + transfer) — electric current through fruit is literal energy transfer
- 4-LS1 + MS-LS1 (life sciences) — plant electrical signals in a Biotron-style lesson
- MS-PS4 (waves) — frequencies, harmonics, oscillation
Practical move: if your school has a STEAM curriculum review board, dual-citing NCAS + NGSS on the same lesson plan often unlocks budget that wasn't available under "just music."
ISTE (International Society for Technology in Education) standards
For students (not teachers). Seven domains: 1.1 Empowered Learner through 1.7 Global Collaborator. Music technology lessons typically hit:
- 1.4 Innovative Designer — students design solutions (a composition, an instrument from objects, an arrangement)
- 1.5 Computational Thinker — algorithmic thinking, pattern recognition, decomposition (rhythm = pattern, melody = decomposition)
- 1.6 Creative Communicator — students publish their work, get peer feedback
Practical move: ISTE citations are gold for IT-led districts that fund tech budgets. Music programs that claim ISTE standards get funded out of the EdTech budget, not the Music budget. That's a transformative shift in some districts.
5. The equipment decision
What you buy depends on what you're solving for. Here's the decision tree we recommend, with budget ranges.
Solo teacher testing the waters — $200-500 budget
Buy: one TouchMe + one Playtron + alligator clip kit. Total: roughly €390 (Single Teacher Starter pricing). Try it in one section for one unit. Measure: did students engage? Did anyone make music they couldn't have made before?
Don't: buy a 30-pack of anything before you've taught one full unit with one device. The most common procurement mistake is buying for scale before validating the workflow.
Single classroom (12-25 students) — $1,200-1,800 budget
Buy: 5 TouchMe + 5 Playtron + 1 Biotron + accessories (we sell this as Class Pack 10, €1,380). Five devices serve a 20-student class in pairs. The Biotron is the demo station — set up the houseplant once, leave it running, everyone visits.
Don't: buy "one device per student." Music technology is a collaborative activity. Pairs and small groups work better than solo time at this age.
Music lab or multi-section program — $3,500-5,000 budget
Buy: 15 TouchMe + 10 Playtron + 3 Biotron + 1 Orbita (Class Pack 30, €3,690). This is the dedicated music-lab setup. Five stations of 3 students. Each station rotates through devices over the semester.
Don't: spend on Orbita-only labs. Orbita is wonderful but it's specifically for pattern-and-rhythm composition. Most middle school programs need touch-based devices for 70% of lessons; Orbita is 30%.
District-wide rollout or museum-grade installation — $15,000+
Buy: custom mix. Talk to us. Bigger orders include on-site training, white-glove setup, and custom curriculum updates. The Lincoln Center configuration was incremental — three orders over two years; that's the wise pattern.
What about iPads and Chromebooks?
You probably already have these. Use them as software hosts for the hardware. A Playtron plugged into a Chromebook running synth.playtronica.com gives you sequencing, recording, sharing, all in-browser. No drivers, no installs, no IT escalations. This is the design intention.
If your district is iPad-only and explicitly blocks USB host mode on the iPads — rare but real — your hardware options narrow. In that case, focus on Category A (software-only, GarageBand) for those classrooms and lobby IT to allow USB MIDI for the music room specifically.
What about Makey Makey?
Makey Makey is the most-cited K-12 invention kit. It's great. It's also general-purpose: the same kit can be used for arts, science, coding, anything. Its music content is shallow — most Makey Makey music lessons are "make a banana piano" demos, not full standards-aligned units.
If your program is invention-literacy-led (Makey Makey's framing) — buy Makey Makey. If your program is music-led — buy music-specific hardware. Playtronica is purpose-built for music. We cover the differences in detail in our Playtronica vs Makey Makey comparison guide (forthcoming).
6. Lesson design for music tech — the 4-phase template
Every music-tech lesson, regardless of grade band, follows the same four-phase shape. Get this template right and every individual lesson plan writes itself.
Phase 1: Wonder (5-10 minutes)
Show students something surprising. The teacher touches a fruit; a sound happens. Students ask: how? Why? Can I do it?
Why this phase matters: it does the motivational work that the rest of the lesson is going to ride on. Skip the wonder phase and students don't engage; they comply. Compliance is the death of music education.
Phase 2: Try (10-20 minutes)
Students get their hands on the device. Open-ended exploration. Teacher circulates, doesn't intervene unless asked.
Why this phase matters: students need to see for themselves how the device works before they can use it as a tool. This is the equivalent of letting students hold a guitar and strum before you teach them chords.
Phase 3: Make (15-25 minutes)
Students have a concrete creative task. "Compose a 16-bar piece." "Make a rhythm pattern with at least three accents." "Design a piece your partner can play with their elbow." The task is constraint-based (this is composition pedagogy 101: constraints drive creativity).
Why this phase matters: this is the music-making. Everything else is scaffolding. If you cut a phase, never cut this one.
Phase 4: Share (5-10 minutes)
Students present, peers respond. Could be in pairs, could be whole-class, could be recorded and shared in the classroom blog. Brief, structured, mandatory.
Why this phase matters: music is a social act. Without sharing, students don't perceive what they made as music — they perceive it as homework. The share phase is the moment the work becomes music.
Total lesson length: 35-60 minutes depending on grade band. Our five free lessons all use this template. If you're new to music tech, copy the template; don't reinvent it.
7. Classroom management for music-tech lessons
Music tech creates specific classroom-management problems that don't appear in traditional music classes. Knowing them in advance is half the solution.
Problem 1: The volume war
Twenty Chromebooks, twenty pairs of cheap earbuds, twenty different songs at full volume. Solution: mandate one earbud out (the room ear). Or: assign listening partners — only one Chromebook's audio is on at a time, both students listen.
Problem 2: The student who finishes in three minutes
Music tech moves fast. A capable student can compose a 16-bar piece in three minutes. Solution: extension challenges. "Now layer a second part." "Now compose for a different mood." "Now teach someone else who hasn't started." Never let early-finishers go on their phones — you've then created a permission structure for everyone else to drift.
Problem 3: The student who can't get started
The blank-page problem hits hard in composition. Solution: provide a starter pattern they can modify. Give them three pre-recorded loops to choose from. "Start by changing one note in this pattern." Lower the barrier to first action, not to final quality.
Problem 4: The hardware that breaks mid-lesson
USB cables fail, devices reset, batteries die. Solution: keep one extra of each device in a "swap bin" at the front of the room. The lesson cannot stop because hardware failed. The swap is the procedure.
Problem 5: The student who deletes their work
Browser tabs close, sessions reset, work disappears. Solution: save every five minutes — make it a class ritual at the bell tone. Use software that auto-saves. Show students the recovery feature in week one before they need it in week three.
Problem 6: The IT incident
A device fails to enumerate as MIDI; the Chromebook crashes; the network drops. Solution: the music-tech lesson plan should be teachable without the technology in a pinch. Have an analog backup — bring out the boomwhackers, or sing the lesson. The discipline of "having a backup plan" is what separates working music-tech teachers from frustrated ones.
8. Special education and accessibility
Music technology is most under-used and most transformative in special-education settings. Here's why, and what to do about it.
A traditional piano keyboard is designed for one body type: an adult with two hands, ten fingers, and the cognitive ability to associate keys with sounds. Many students don't match that template. They might have one functional hand. They might be non-verbal. They might be cognitively younger than their physical age. The traditional keyboard turns those students into observers.
Music technology with capacitive sensing — like TouchMe — does not assume that body. Any conductor works: a hand, a foot, an elbow, an extended arm. Any object works: a foam ball, a soft fabric, a hand-warmer pad. Any latency works: the student can take ten seconds between gestures; the device waits.
What this means practically: a student who has never made a sound on a piano can make a meaningful musical phrase on TouchMe within a five-minute introduction. We've seen this in sensory-room contexts, in music-therapy settings, and in cross-categorical SPED classrooms.
Lesson template for SPED contexts
- Adapt the conductor. If the student can't grip a typical metal patch, use a soft conductive pad. Aluminum foil wrapped around a foam ball works. A copper-impregnated fabric works.
- Slow the share phase. Time pressure raises stress. Let the share phase last as long as it needs.
- Document for IEP review. A child who plays a sustained note for the first time has reached a meaningful goal. Documenting that — short video, parental release — supports IEP review and demonstrates progress in a way that standardized assessments don't.
Our Lesson 5 (Composing for the Body) is built around accessibility design. The same lesson works in mainstream and in SPED settings; the body-aware framing benefits everyone.
For broader exploration, see Save The Music Foundation's resources at savethemusic.org, NAfME's special-education repertoire at nafme.org, and the Berklee Institute for Accessible Arts Education. We're proud that Playtronica devices are used by music therapists at hospitals, sensory-rooms in K-5 schools, and inclusive-arts programs at museums.
9. Procurement and budget — where the money comes from
This is the section principals and finance officers will read most carefully.
US funding sources
- Title IV-A (Student Support and Academic Enrichment Grants) — federal funds, distributed through states, can be used for music technology under the "Well-rounded education" pillar. Most under-claimed source. We have a forthcoming Title IV-A music technology guide with example language.
- ESSER (Elementary and Secondary School Emergency Relief) — COVID-era funds, deadlines for use vary by state. Many districts have unspent allocations that can be redirected.
- Title I — for schools with high low-income enrolment. Music tech qualifies as supplemental instructional materials.
- Local PTA / PTO — varies widely. Smaller, but fast.
- Music Industry Foundations — Mr. Holland's Opus, VH1 Save The Music, Hungry For Music. Highly competitive but worth knowing about.
EU funding sources
- Erasmus+ — for cross-border music education collaborations. Slow but generous.
- Creative Europe — culture-focused EU funding; some music technology projects qualify.
- Digitalpakt 2.0 (Germany) — €5 billion for school digital infrastructure, including instructional hardware. Music tech qualifies.
- National Lottery (UK) — Youth Music Fund disburses around £20m annually for music programs reaching under-served young people.
UK-specific
- Department for Education Music Hub funding — every English region has a Music Hub. Hubs hold budget for instruments and technology.
- Pupil Premium — UK equivalent of US Title I; can fund music tech for eligible students.
Practical procurement notes
- POs accepted — most music-tech vendors (including Playtronica) accept formal POs from US districts, UK LAs, and EU institutions. We can be set up as a vendor in most procurement systems within one business day.
- VAT invoicing for EU institutions — required, available on request.
- W-9 for US — we provide a W-9 (Playtronica is W-8BEN since we're outside the US, but our US distributor partner can provide the W-9 if your accounts payable requires).
- DPA / AVV for EU — Data Processing Agreement (English) / Auftragsverarbeitungsvertrag (German) — provided on request, signed within 1 business day.
For a procurement-ready conversation, the fastest path is our institutional quote form. We reply within 1 business day with a quote PDF and any supporting documents your finance office needs.
10. Common mistakes — and how to avoid them
These are the mistakes we see most often. Each one is preventable.
Mistake 1: Buying for scale before validating
A district buys 200 devices, distributes them to 20 schools, and 18 of them sit in a closet because the music teachers never got training and the IT department blocked USB MIDI. Avoid by: pilot first. Always. One school, one teacher, one semester. Then expand.
Mistake 2: Underestimating teacher PD time
Music tech requires teachers to be confident with the tools. A music teacher who's spent 30 years teaching choir needs onboarding time. Skipping that time means the equipment sits unused. Avoid by: budget 4-8 hours of PD per teacher before they use the tools in front of students. We provide a free Playtronica 101 course; many vendors offer similar.
Mistake 3: Decoupling hardware from curriculum
Buying devices without buying or designing lessons. Teachers receive a box; they don't know what to do with it. Avoid by: committing to a curriculum first. Use our 15 free lessons. Use someone else's. But have a lesson plan for every device before unboxing.
Mistake 4: Ignoring assessment
Standards-aligned curriculum without assessment is curriculum that gets cut in the next budget round. Avoid by: designing assessment from day one. Even simple — a rubric for "did the student demonstrate Cr1.1?" — gives you evidence to defend the program.
Mistake 5: Treating it as "extra"
Music tech as a once-a-month "fun day" doesn't build skills. Avoid by: integrating into the main scope and sequence. Music tech is part of music, not adjacent to it.
Mistake 6: Ignoring the after-school context
A student who loves what they did in your class on Friday will Google "how do I do this at home" on Saturday. If the tools they used at school are inaccessible at home, the magic ends at the bell. Avoid by: choosing tools that work at home too. (synth.playtronica.com is free and browser-based; no purchase required for the software.)
Mistake 7: Letting the equipment age out
Hardware breaks. Software updates break things. Avoid by: budgeting 10-15% per year for replacement, repairs, and updates. We provide an institutional warranty on Playtronica devices; ask about it in your quote conversation.
11. The Playtronica approach
We made four music-technology devices because the existing options didn't solve the four problems we cared about.
TouchMe is a small USB MIDI capacitive-sensing device. Touch any conductive object; a MIDI note plays. We made it because the cheapest way for a student to play their first note was to touch a banana. That's the equity moment.
Playtron is an alligator-clip-equipped MIDI input. Students wire it to fruit, foil, water glasses, themselves, each other. We made it because composition-by-clipping-stuff is a fundamentally different cognitive task from composition-by-typing. The hands are involved.
Biotron is a plant-electrode MIDI device. Plug it into a houseplant, hear what the plant is "thinking." We made it because the cross-curricular biology + music + electronics combination has no commercial equivalent. The plant station at Lincoln Center is the most-photographed exhibit in their family days.
Orbita is a rotating-disc sequencer. Place coloured magnets on it; it plays back the pattern. We made it because pattern-based composition needed a tangible object — students think differently when they see a pattern in space, not on a screen.
All four are USB MIDI class-compliant — works without drivers on Chromebooks, Macs, Windows, Linux, Android. All four work with synth.playtronica.com (free, browser-based) and with any DAW that accepts MIDI input. We open-source the firmware. We license the curriculum CC-BY-4.0.
We're a small team based in Tallinn, Estonia. Founded by Sasha Pas in 2014. Our devices are used by Lincoln Center, Stanford d.school, Berklee College of Music, Hochschule für Musik Trossingen, Centre Pompidou, Garage Museum, Filharmonia Opolska, Singapore Ministry of Education, and many others. Our pricing for institutional buyers is on the pricing page; pilot applications are open at the pilot page.
We're not trying to be everything to everyone. We're trying to be the best music-specific tool for the K-12 → conservatory institutional buyer. That's the niche. We own it.
12. Free starter resources
If you've read this far and you're thinking about bringing music technology into your classroom, here are the no-cost next steps:
- Lesson 1 PDF download — print-ready K-2 lesson on touch and conductivity. Teach it tomorrow with no Playtronica devices — bring fruit, foil, and a multimeter to demonstrate the concept of conduction. Then upgrade to TouchMe if it lands.
- Standards alignment map — lesson-by-lesson NCAS / UK MMC / NGSS / ISTE citations. Useful for curriculum review boards.
- 5 free lessons in full — Lessons 1-5 from our 15-lesson curriculum. Free, CC-BY-4.0 licensed. Use them as-is, modify them, take them to your colleagues.
- Free pilot program — applications open for Fall 2026 cohort. 5 schools selected; each receives a free Class Pack 10 (€1,380 value). In return: a written case study + photo/video rights. Applications close 31 August 2026.
- Talk to Andrey — founder of Playtronica reads every email. [email protected]. Reply within 1 business day. No sales pitch unless you ask for one.
Related guides + reading
- Lesson 1 — What is sound? Touch as conductor — the canonical K-2 entry point.
- Lesson 5 — Composing for the body — the accessibility-design lesson.
- Lincoln Center case study — Performing Arts institution in NYC — three repeat orders, multi-program use.
- Stanford d.school case study — Design-thinking + maker pedagogy — €1,802 mixed-device order.
- Hochschule für Musik Trossingen case study — European conservatory + MIDI research — single-faculty-led adoption.
- Standards alignment — lesson-by-lesson mapping.
- Pricing tiers — Single Teacher Starter through District / Lab.
- Institutional quote — POs accepted, 1-business-day reply.
What this guide is, and what it isn't
This guide is written by Playtronica. We make hardware. We profit when classrooms adopt music technology. That's a disclosure, and you should read this guide with that in mind.
This guide is not a comprehensive review of every music-technology product on the market. It's a synthesis of what we've learned working with thousands of classrooms, what the standards documents actually say, and what the failure modes look like in real schools. We've tried to be honest about what music tech can and can't do — and where Playtronica fits in that landscape.
If you find a factual error in this guide, email [email protected] and we'll fix it. If you teach a music-tech lesson that works really well and isn't in our curriculum, send it — we credit teachers and license under CC-BY-4.0. The goal here is to make music education better. The guide is one tool toward that goal. Your classroom is another. Use both.
Last updated: 2026-05-28. Next review: quarterly.