GRobotics
A white studio bench with a laptop, a camera drone, and five hexapod robots arranged around it.

Robotics research and education — Kathmandu, Nepal

We build and teach to build.

A robotics lab in Kathmandu doing humanoid research and project work for organisations across Nepal. The same bench runs robotics, AI, and drone technology as a school subject — inside the timetable, at our own lab, and as internships for the people who want to go further.

What we are

A robotics lab that also teaches.

Three of these run at partner schools and at our own bench today. The other three are what the lab does with the rest of its week — research, work commissioned by others, and the people we train on it — and they are set out further down.

Robotics inside the school day

The annual programme: robotics, AI, and drone technology taught in the timetable by our instructors, grades VI to XII, at partner schools.

Weekly training

One session a week on the same curriculum spine, for schools starting smaller — a working entry point that upgrades into the full programme.

Classes at our own lab

Short courses in Buddhanagar for students whose school runs no programme yet, and for holiday cohorts. Full bench and hardware access.

Humanoid and robotics research

The lab builds as well as teaches. Humanoid and applied robotics work runs alongside the programme, and it is where the harder problems get worked out.

Work with government and organisations

Project work carried out with public bodies and organisations in Nepal, on problems that are theirs rather than ours.

Internships

A bench, a supervisor, and real work — for students and graduates who want to build rather than watch. Applications come through the contact form.

Lessons across seven versioned courses
141
Grade levels on one platform spine
VI–XII
Instructor to students, at the bench
1:12
Nepal project bank builds
10

At the bench

Things that were actually built

Not renders and not a syllabus. These four are teaching builds from our own lab — the machines a student works through before the project bank, each one a step past the last.

A two-motor rover with a five-sensor array tracking a curved black line on a white surface.

Line follower

The first machine that reacts to the world instead of a script. Five sensors, two motors, and a loop that has to run faster than the rover moves.

Sensors and a control loop
A four-wheel rover with ultrasonic sensors in front of a hand-drawn decision flowchart and a wooden block.

Obstacle avoider

Where a student draws the flowchart before writing it. The rover measures, decides, and turns — and the drawing on the wall is the program.

Decisions in code
A four-sensor rover inside a plywood maze, with its remembered route drawn above it.

Maze solver

The step from reacting to remembering. It walks the maze once, keeps the route, and the second run is the proof that it kept it.

Memory and pathfinding
A sensor glove beside a small aluminium arm it drives, with a calibration card on the bench.

Gesture-controlled arm

A glove reads a hand, an arm copies it. Calibration is most of the work, which is the lesson — the demo is easy and the zeroing is not.

Motion capture to actuator

Three ways in

One method. Three ways to run it.

The teaching side of the lab runs three ways: inside a school's timetable, one session a week, or at our own bench. The method is the same in all three — the same curriculum spine, the same Safety Passport, the same builds. What changes is where it runs and how much of it you take on.

Four student-built robots lined up on a classroom table: a traffic-light rig, a two-wheel buggy, a large wheeled rover, and a tracked chassis.
01

Annual School Program

  • Grades VI–IX · XI–XII
  • Inside the school timetable

The flagship. Robotics, AI, and drone technology delivered inside your school's timetable by our instructors — a staged path from Foundations to Advanced Systems, with Dashain–Tihar, terminal exams, and school events already accounted for in the plan.

Overhead view of a bench: laser-cut plywood chassis parts, a kit box of motors and wheels, and a student working at a laptop.
02

Weekly Training

  • Grades VI–XII
  • Weekly sessions

For schools starting smaller. One session a week on the same platform spine, the same Safety Passport, and the same practical gate checks — a working entry point that upgrades cleanly into the full program.

A two-deck robot car under test on a lab bench, wired to a bench power supply with a multimeter beside it.
03

In-House Robotics Training

  • Students & small crews
  • At our Kathmandu lab

Training at our own lab in Buddhanagar, for students whose school does not run a program yet and for holiday cohorts. Small crews, full bench and hardware access, and the same Nepal Project Bank builds.

The path

Where a student starts, and what they can do by the end

One spine, four stages. Each one closes against something built rather than something written, and no stage opens until the one before it has been demonstrated.

  • 01

    Foundations

    Grades VI–VII

    Mechanism and drivetrain, and block coding on micro:bit. The student builds something that moves under its own control and can explain why it moves.

  • 02

    Smart Systems

    Grades VIII–IX

    Sensing and control on Arduino and ESP32 — wired sensors, actuators, and a board the student has wired themselves rather than plugged together.

  • 03

    Mastery, AI & Autonomy

    Grades XI–XII

    Python, datasets collected by hand, and inference running on the device. It closes on a drone build and a piece from the project bank.

  • 04

    Lab courses

    One to three months

    The same spine outside a school timetable: robotics, AI, and drone foundations at our own bench, and an integrated course that runs all three together.

What a school gets

The whole of what arrives

Not a syllabus document and a box of kits. This is the list a head of school can hold us to, and every line of it is something the program already does.

01

A slot in the timetable

Taught inside the school day, term after term, by our instructors — a real subject on the schedule, not an after-school club competing with tuition.

02

Hardware staged by grade

micro:bit through grades VI–VIII, bare Arduino and ESP32 once students wire their own boards from IX, and a drone airframe in the final term.

03

An instructor at the bench

One per twelve students, never unsupervised, with a second adult from the school present for any session involving power tools or flight.

04

Assessment against real work

A bench check, a circuit viva, a notebook review, and a showcase — each judged against something the student built rather than a paper.

05

A term report the school keeps

The term's assessments and the incident log together, sent to the school whether or not anything happened in the lab that term.

06

Accounts for the people running it

Separate doors for the school admin, the instructors, and the students — each seeing their own cohort, and nothing from another school.

Who sees what

One platform. A different door for each of you.

This site is not only the brochure — it is where the program runs. Students, instructors, and school administrators each sign in to their own panel, and each sees exactly their own slice: never another school's, never another student's.

  • Students

    Your own record of the year: every lesson, every gate check, and a credentials wallet that shows what you have earned and what is left to earn it. Quizzes are practice, not judgement — unlimited retries, a fresh set of questions each time, and an explanation after every answer that teaches the concept instead of announcing the letter. Your progress is yours; the platform never ranks you against classmates.

  • Schools

    The school's own truth, live: attendance, progress, cohorts, and staff — for your students and nobody else's. Term reports freeze the moment they are generated; corrections are appended, never rewritten, which is exactly why the archive is worth keeping.

  • Instructors

    GRobotics staff, not borrowed teachers — certified through four stages, observe to co-teach to solo-under-audit to certified, before they run a bench alone. They capture the whole session in the lab as it happens, even with no signal: a lab without internet is a normal day here, not an error.

  • Parents

    A printed report every term: your child's assessments and the lab's incident log, sent whether or not anything happened. Nothing to install and no account to manage — and we hold the minimum about your child: no photograph, no medical detail, one contact number.

Bikram Sambat first on every date · every panel in English and Nepali

Proof

Something that runs, and a record that holds up

Every assessment closes against work the student built, and the program ends in a credential anyone can check — which is the part that matters once the student is applying somewhere.

The builds are the transcript

Work goes into the public gallery only when the school puts it forward, and the photographs show objects and hands — never identifiable faces. What is on that page was built by a school team from a brief in the project bank.

Behind every credential the rule is the same: it traces to captured records. Nothing here is awarded by a button that has no evidence behind it.

A public ID
Printed on the certificate and in its QR code. It is the only way to reach the record — high-entropy, so the URL space cannot be walked.
No account to check it
A parent, a school, or an admissions office opens the link and gets an answer. Nothing to sign up for, and no directory to browse.
A name only if the student agreed
Without consent the page says so plainly, rather than falling back to initials or a school-and-grade that identifies anyway.
An expiry computed on read
Never stored, never cached. A credential that lapsed this morning does not read as valid this afternoon.

Safety

The part schools ask about first

Lithium batteries, hot irons, and spinning propellers in a room full of teenagers. These are the standing rules, and they are the same at every partner school.

  • One instructor per twelve students

    Bench work is never unsupervised. A second adult from the school is present for any session involving power tools or flight.

  • Soldering from grade IX only

    Eye protection, a fume extractor at the bench, and a demonstrated pass on the technique before a student is allowed a hot iron.

  • Lithium cells charged in fire-safe bags

    Charging happens in the lab, in a bag, on a logged timer — never overnight, never in a classroom or a bag left in a locker.

  • Flight indoors, inside a net

    Routine flying is done in a netted cage. Outdoor flying is instructor-only and follows the prevailing CAAN rules for the airframe and site.

  • Incidents logged and reviewed each term

    Every cut, burn, crash, and near-miss is written down. The log goes to the school with the term report, whether or not anything happened.

Current work

What the lab does with the rest of its week

The school programme is what we sell. It is not the whole of what we do, and a page that showed only the programme was leaving out the part that makes the programme any good.

  • Humanoid and robotics research

    Legged and humanoid machines, and the control problems underneath them. It is the work the teaching came out of, and the reason the curriculum stays close to real hardware rather than to kits.

  • Work with government and organisations

    Project work carried out for public bodies and organisations in Nepal. The brief comes from them; the build, the testing, and the handover come from the lab.

  • Internships

    Places at the bench for students and graduates who want to build. Supervised, on work that is going somewhere, and applied for through the same contact form as everything else.

Your students are ready for this.The lab is the only thing missing.

  • A delivery plan mapped to your school's calendar
  • A visit to the Kathmandu lab, no commitment
Bring it to your school