The school lab, from anywhere.

Most schools have already paid for the expensive piece. A CAD lab has twelve workstations running Fusion 360 and SolidWorks — each one a five-thousand-dollar machine carrying a multi-thousand-dollar annual software license. A music lab has Logic Pro and Pro Tools on Macs that cost more than the rest of the room combined. A video lab has Premiere and DaVinci Resolve running on hardware purchased specifically to handle the timeline scrubbing. A statistics lab has SPSS or Stata or SAS licenses tied to specific seats. Those licenses were bought to be used. They sit idle from the moment the school day ends.

Remio puts those idle hours to work. A student pairs once with one of the lab workstations, then streams it from home on whatever device they have — an iPad, a hand-me-down laptop, a Chromebook running the Android client, the family Windows PC. The student gets the full software, the full GPU, the full license. The school does not buy a new machine. The school does not buy a new license. The school does not negotiate a per-seat concurrent-user contract with the software vendor — the software does not even know it is being used remotely.

There is no per-seat pricing to do math on. Remio is free. A school with twelve workstations and three hundred students who rotate through them pays the same as a school with one workstation and one student — nothing. There is no concurrent-user limit to plan around either. The natural ceiling is one student per workstation at a time, which is the same ceiling as in the physical lab. The scheduling is whatever the lab admin already does for the physical lab — Remio just extends those hours past 4pm.

The result is more access for students, with no procurement cycle, no new line item, and no new vendor to add to the IT inventory. The lab workstation is the unit of scale. If a school can buy one more lab machine, it can serve one more cohort of after-hours students. The pricing model never gets in the way.

Picture the lab at 4pm on a Tuesday. The classroom empties out. Twelve workstations are still running Fusion 360, SolidWorks, or Rhino — the software is open, the licenses are checked out, the GPUs are warm. Without Remio, the school turns the machines off or lets them idle. With Remio, the lab admin has paired each workstation with a roster of students for the evening shift. At 4:15pm, the first student in the queue sits down at home with their iPad and connects.

The student sees the workstation desktop exactly as it would appear in the lab. They open the project file they were working on during class. The cursor moves the way a cursor moves on the host machine, not the way a cursor moves on a streamed-down preview that lags a quarter-second behind the input. Fusion 360 rotates a model in real time. SolidWorks regenerates a feature tree without the visible reflow that other remote tools introduce. The student does the work that was assigned for that night.

A student who owns a Wacom tablet at home plugs it into the iPad or the laptop they are streaming from. Pressure, tilt, and pen buttons pass through to the host workstation as native input — the workstation behaves exactly as it would if the Wacom were plugged into it directly in the lab. This is the part conventional remote tools usually break: pressure goes flat, tilt disappears, the pen buttons stop registering. With Remio the Wacom works the way the student bought it to work.

At the end of the slot, the student saves, closes their project, and disconnects. The workstation is back in the queue, ready for the next student. The handoff is clean because Remio does not maintain a per-user profile on the host — it just forwards input and renders pixels. The next student connects, opens their own project, and goes. No reboot between sessions is required, though the lab admin can schedule one if a course expects a fresh environment.

Over an evening from 4pm to midnight, twelve workstations comfortably serve thirty-six to forty-eight students in two-hour blocks. The CAD lab effectively triples its capacity without the school buying a single additional machine. The lab admin's job is the same as scheduling the physical lab — most schools fold it into the calendar tool they already use.

A music student cannot run Logic Pro on a Chromebook. Pro Tools does not exist for iPad. Avid Media Composer is not a thing a sixteen-year-old has on their personal laptop. The school's lab Mac, with the licensed software, the audio interface, and the studio monitors, is the only realistic environment for the assignment. Without remote access, the student has to be in the lab during open hours — which often means the same after-school window when sports, jobs, and family responsibilities are also competing for time.

Remio streams the lab Mac to wherever the student is. Audio plays through the encrypted channel and out the student's headphones — the latency is low enough that arrangement work, MIDI editing, and mixing decisions are practical. A student cannot perform a live tracking session through a remote stream (no remote tool can solve the speed-of-light problem on a live take), but every other step of the music workflow — arrangement, MIDI sequencing, virtual instrument work, mixing, mastering revisions — happens normally over Remio.

Video editing has the same shape. The DaVinci Resolve or Premiere timeline on the lab workstation scrubs smoothly because the lab workstation is the one doing the decoding — the student's laptop or iPad is just rendering the pre-decoded stream. A 4K timeline that would chug on the student's personal laptop scrubs in real time because it is being scrubbed on the workstation. Color grading, effect work, multi-cam editing — the heavy lifting happens on the powerful machine that was bought to do exactly that.

Apple Pencil works the way it would on a connected iPad if the student is using one for video color grading or audio automation drawing — pressure and tilt pass through as native input. A USB MIDI controller plugged into the student's laptop routes through to the lab Mac. The student's environment at home is treated as an input layer for the lab workstation, not as a separate machine that has to mirror state.

For a school running a media program, this is the difference between "you can only practice during open lab" and "you can practice whenever you have free time." The hardware purchase that made the program possible in the first place now stretches across the whole school week, not just the school day.

Most software a school deploys arrives with a privacy review attached: what data does the vendor collect, where is it stored, who has access, how is it deleted, how would a parent's request to inspect or erase that data be honored. The review is necessary because most software collects student data. Remio is unusual in that the review is short — there is no data to inspect, no email address to erase, no student name in any Remio database, no session content stored anywhere on Remio infrastructure.

The reason is architectural. Remio does not have a user account system. There is no signup flow. The way a student connects to a workstation is by entering a 4-digit PIN that the workstation displays on its screen when the lab admin asks it to. The two devices exchange ephemeral encryption keys through Remio's introduction server, then connect directly to each other. From that point forward, the session content — the desktop video, the keystrokes, the mouse movements, the audio — travels between the student device and the workstation, and not through Remio. Remio is not in the path.

The practical implication is that Remio cannot leak student data because Remio does not have student data. There is no database of student emails. There is no log of what apps a student opened on what workstation. There is no recording of session content. A parent request to see "everything you have about my child" would honestly return an empty set. A FERPA-style data inventory of school-vendor relationships typically does not need to include Remio, because Remio is not a data processor of student information — it is closer to the role of a network cable, ferrying bits between two endpoints that have already encrypted them.

There is no such thing as a FERPA-certified product, or a COPPA-certified product, or a HIPAA-certified product. Those are regulations that apply to deployments, not labels that ship on software. What Remio offers is an architecture that makes a compliance review short and a deployment that fits cleanly inside the school's existing data-flow inventory. Every school should still have its own counsel confirm that fit — that is what counsel is for — but the conversation tends to be brief.

For schools that do collect telemetry from other vendors and want to verify what Remio sends, the answer is short: pairing handshakes (a 4-digit code, a public key, no identity) and presence pings (a workstation is online or not). That is the entire wire footprint of the introduction server. The session content itself never reaches Remio. Schools that want to inspect this with their own packet capture are welcome to.

The pairing model is one workstation, one student device at a time. A lab admin sits at each workstation in turn, opens Remio Host, and reads off the 4-digit PIN as each student enters it on their own device. The pairing is then remembered on both ends — the student device knows about that workstation, the workstation knows about that student device, and a future connection just uses the saved pairing instead of asking for the PIN again. Pairing twelve workstations against forty student devices takes an afternoon. After that, the lab admin's only ongoing job is scheduling.

Workstations need a stable wake-from-sleep policy. The most common deployment failure is the workstation going to sleep at 6pm and the student at 8pm not being able to wake it. The fix is to set the workstation's sleep policy to "never" or "after a long idle period," or to use the workstation's built-in scheduled-wake feature so it is reliably awake during the after-hours window the lab supports. Both macOS and Windows have first-class controls for this; the IT team probably already has a group policy for similar fleet behavior.

The school's existing network controls keep working. Remio runs inside the school's network ACLs, content filters, and firewall rules the way any other application running on a workstation would. There is no Remio-specific port to open, no Remio-specific exception to make. The connection from the student's home to the school workstation traverses the school's normal inbound or relay path; the content filtering and acceptable-use policy that already governs the workstation continues to govern it when accessed remotely.

Reset is simple. When a student graduates, transfers, or finishes a course, the lab admin unpairs the student's device on the workstation — a single action from the Remio Host's paired-devices list. The student's device no longer connects to that workstation. If a device is reported lost or stolen, the same unpair operation revokes its access in seconds. There is no central console to log into, no support ticket to file, no propagation delay. The workstation owns the list of who can connect to it, and the workstation is the place where that list is edited.

For schools that want a written rollout plan, support@remio.net is happy to put one together — covering recommended sleep policies for the workstation OS, suggested scheduling cadence, and a checklist for the first cohort. For most labs the rollout is small enough that a single afternoon by the lab admin replaces any of that.

Remio is free for individual students. A student downloads the client on their iPad, their Mac, their Windows laptop, their Android tablet, or their phone, pairs once with the lab workstation the school has set them up against, and connects. No credit card, no email signup, no in-app upgrade prompt sitting on the side trying to convert them to a paid tier later. Free means free, and means free for the use case this page describes.

Remio is free for schools. A school installs the Host on every lab workstation it wants to make remotely accessible, and pays nothing. There is no per-seat fee. There is no per-workstation fee. There is no concurrent-session ceiling that turns into a hidden charge when the lab grows. A school running one workstation pays the same as a school running a thousand workstations — nothing. The pricing model is a flat zero, intentionally, so that the math of "should we expand the lab" is purely a hardware-and-licensing question and not also a Remio-licensing question.

A school that needs a paper trail can have one. Some procurement processes require a quote on letterhead, a deployment letter, a signed statement that pricing is what we say it is. Email support@remio.net with the request and we will provide it. There is no sales engineer who needs to be on a call. There is no "request a demo" form that hides behind a contact form for two weeks. The free tier is the whole offering, and we put it in writing if the school's purchasing system needs us to.

For districts considering a larger rollout — hundreds of workstations across many schools, an MDM-managed deployment to student devices, a central pairing console for IT to manage at scale — the same email reaches the people who would help plan that. Most rollouts do not need it; the standard installer and a lab admin's afternoon is usually enough. When something more is needed, the response is human.

The reason the page does not have a pricing table is that there is nothing to put on the rows. There is one tier. It is free. It includes everything. That is the entire pricing page for the education use case.