Engineers who live in ICDs
Founded in 2023 in Luxembourg. Three people tired of rewriting the same packet encoder twice each year.
Why we built this
ICDs capture the design choices needed for ground-software integration. They define packet structures, field encodings, boundary conditions, and command sequences. Yet no dependable path has existed from document to compilable, testable code. Engineers always handled that translation manually, one person and one integration cycle at a time.
The gap is no exception: it is the main bottleneck for small or mid-size teams moving from PDR to integration testing without a large software organization. Flight-software schedules slip when documents do not automatically produce code. Test harnesses come late because earlier time is unavailable. Traceability is rebuilt afterward because no tool tracked it from the outset.
We built Spacebackend around a document-to-artifact generation pipeline. It gives spacecraft engineering teams capabilities large primes have long built in-house, without needing a large prime's headcount to operate them.
Team
He builds ground-segment command dispatchers and ICD tools for spacecraft integration programs. After facing the same manual packet-encoder translation problem on successive missions, he created Spacebackend's first version and made it a product.
He works on spacecraft onboard software integration testing, using embedded C and Python fixtures for flight systems across LEO program phases. He designed the ICD ingestion pipeline and artifact generation engine to handle real documents' format inconsistencies.
She led V&V and systems integration across three small-satellite programs. She owns the early-access program and works with engineering leads to fit generated artifacts to real team workflows.
Company facts
Get in touch
Questions about early access, technical integration, or licensing? We read every message from spacecraft engineering teams.