Company
We were the team getting paged at 3am
Substrate started as internal tooling at a hospital network that could not send patient data to an API.
Why we built it
In 2023 we were running clinical summarisation on twelve GPUs in a basement in Newark. Everything available assumed you would rent capacity from someone else. Nothing assumed you already owned the hardware and legally could not move the data off it.
So we wrote a scheduler. Then a router, because the scheduler was not enough. Two other hospital systems asked to use it, and at that point it stopped being internal tooling.
We are eleven people, funded by revenue and one seed round, and we intend to stay small enough that the person who answers your support ticket wrote the code.
Open roles
Systems engineer, scheduler
Rust. You will own pre-emption and the bin-packing heuristics. Remote within US timezones.
Solutions engineer
You will run the first two weeks of every regulated deployment. Heavy Kubernetes, some travel.
Technical writer
Our docs are the main support channel and we want them to stay that way. Part-time to start.