about the company
about sylorlabs
sylorlabs doesn't work in one lane. an audio workstation, an ai command shell, a deterministic reasoning engine, a systems language, and the ternary hardware research underneath it, all built by the same small team, in the open.
the goal is simple. follow the interesting problems, build good tools, and keep the work public.
the lab
a research lab that follows the cracks wherever they show up, not a company built around one product.
range
an audio workstation, an ai shell, a systems language, and the hardware research underneath it. the work spans whatever needs building.
how it works
keep the scope small on any one thing and keep the work moving on all of them.
the idea behind the name
fill the cracks with gold
kintsugi matters here because it points to repair. the point is simple. fix broken workflows and make tools people can trust again.
the lineup
what each product actually does
| product | domain | what it does | status |
|---|---|---|---|
| Zenith DAW | audio | A DAW being rebuilt from the compiler down in Zag. | early |
| Dray | audio | Music at the speed of the web. | unstable |
| Koryphaios | intelligence | Your native desktop AI command center. | beta |
| Zag | infrastructure | A language that proves your promises instead of just trusting your comments. | early |
| Flash | infrastructureProject Prism | A language built for hardware that doesn't exist yet, running fine on the hardware you already have. | early |
| PrismStudio | infrastructureProject Prism | A workbench for designing ternary optical hardware and proving the design is right before anyone builds it. | early |
| RayOS | platformProject Prism | An operating system written from scratch in Flash, for hardware that thinks in three states instead of two. | early |
| Ghost | intelligence | Researching which intelligence claims survive real gates. | work in progress |
the team
who is building it
small team
a small team means less noise and more focus.
public repositories
the repos show the code and the current state of the work.
github
feedback and code can stay with the repos where the work lives.
the method
how the work stays real
step 01
show the work
the product pages and repos should make it clear what is real.
step 02
keep it small
two main builds is enough right now.
step 03
build in public
updates and code stay out in the open.
the commitments
our promises
keep it clear
make tools people want to use
earn trust by shipping