Robotics Startup
As CTO, I lead architecture and engineering for a platform that connects software builds, signed releases, and controlled updates to robots.
What we’re building
Updating software on a fleet of robots involves more than publishing a build. Each device needs the right artifact, a way to verify it, and a recovery path if the update fails.
We’re developing infrastructure for that workflow: building software from GitHub, verifying and signing release artifacts, and managing their delivery to devices. Creating a release and authorizing its deployment are separate steps.
My role as CTO
I lead a four-person development team, set the technical roadmap, and define how the build infrastructure, backend, and device runtime fit together. Architecture, implementation, and code review are all part of my work.
My hands-on work includes signing workers that preserve state through retries and failures, tenant-isolated fleet models, and storage for release artifacts. I’m currently working on build caching and retention, alongside signing-worker integration and recovery.
Engineering responsibilities
- Defining the architecture across hosted builds, release verification, and device updates.
- Leading a four-person development team.
- Setting the technical roadmap and engineering priorities.
- Building signing workers with durable state, idempotency, and failure recovery.
- Developing tenant-isolated backend models for device fleets and deployment groups.
- Working on artifact storage, build caching, and traceable release records.
MVP scope
The build and release work covers hosted CI, independent artifact verification, cryptographic signing, and private artifact delivery. Release records are designed to retain a software bill of materials (SBOM), build provenance, and verification evidence.
On the device side, the team is developing over-the-air updates, health checks, and rollback. Fleet workflows are being built around staged rollouts, with operator controls to pause, resume, or cancel a deployment.
The platform is in MVP development. Individual components are being implemented and tested; the complete workflow is still being integrated and validated.