We write the software that flies, drives, and controls hardware built for federal missions. NASA has funded our research, and we have delivered flight and ground software on NASA programs both directly and as a subcontractor under a major defense prime.
Between the sensor and the actuator, and between the system and the person responsible for it. That is what we build.
Bare metal, RTOS, and embedded Linux for hardware that operates in the field rather than in a lab. Flight-adjacent and mission-critical code, written to be reviewed, tested, and maintained by someone other than the person who wrote it.
Computer vision and accelerated inference engineered to run on constrained edge compute. Turning sensor input into something a controller can act on with confidence.
Path planning, behavior systems, and decision-layer software that runs on the platform, for environments where the network is degraded, contested, or absent.
Safety-critical human-machine interfaces, teleoperation, and ground control software for remotely operated and semi-autonomous platforms. The layer where a human stays in or on the loop.
Physics-based simulation and synthetic data generation with ground truth built into the generation process, for training and validating perception systems where real-world collection is impractical.
Prime contracts with the U.S. Department of Veterans Affairs and NASA, and subcontract delivery for NASA and the U.S. Army.
Built and delivered the rover deployment software that lowers three autonomous lunar rovers from the lander, and the ground control interface for the ground-penetrating radar aboard each rover. The software is delivered. The mission has not yet flown.
Read the CADRE case study →Designed and developed the test rack infrastructure used to validate the lander’s flight hardware and software.
Read the Mars Sample Return case study →Safety-critical operator control interface for a bomb-disposal unmanned ground vehicle program, delivered against a six-month U.S. Army deadline.
Read the Teledyne FLIR case study →Interactive web-based technical manual system built on a custom content schema, generalized for use across the MTRS platform and four U.S. military branches.
Communication-less coordination of robotic swarms, with Arizona State University. Robot simulation platform for source search and mapping, with the University of Nevada Las Vegas.
Simulator that generates and automatically labels synthetic Mars imagery with pixel-level ground truth, to train and test perception neural networks. With Fayetteville State University.
Extensive perception and autonomy engineering for the world’s largest manufacturer and operator of industrial mobile robotics.
Perception → Simulation → GPU acceleration →Hardware programs slip on software, and embedded, perception, and autonomy engineers are the hardest roles a prime has to fill and hold. Geisel is a standing team in those disciplines and goes onto a program without a hiring cycle in front of it.
Embedded and real-time code, perception, on-device autonomy, and the operator interface, under one roof. The integration risk between those layers stays inside our scope, where it is ours to manage.
Physics-based simulation and synthetic training data are in-house capabilities. Perception and autonomy development runs in parallel with the hardware build rather than queueing behind it, which is time a program gets back.
Behind all three: our code has gone through the review, test, and documentation required to fly on a NASA mission, and through a prime’s security and reporting requirements. The engineers behind our past performance are the ones who do the work.
No. We work as a subcontractor under prime contract vehicles rather than carrying our own.
Geisel is a small business. We do not hold 8(a), HUBZone, SDVOSB, or WOSB designations.
Yes. We hold prime contracts with the U.S. Department of Veterans Affairs and NASA, we have delivered NASA program work as a subcontractor under a major defense prime, and we have held two competitively awarded NASA STTR research programs.
Yes. Our entire engineering staff is US-based, working from Worcester, Massachusetts. We do not offshore development, and there is no foreign IP exposure.
Yes. We are ITAR-ready and have delivered on defense programs with export control requirements.
We work at a range of scopes, from focused engineering efforts through multi-phase program work. Not every engagement is fixed scope. The right structure depends on the program.
Software for physical systems: embedded and real-time code, perception, on-device autonomy, and operator control interfaces for robots, unmanned platforms, and instrumented hardware.