Who we are

Two humans.
One studio.

Dromlight is not a startup pretending to be a research lab. It's two people making the thing, in Oregon, with a working relationship with the AI they build alongside.

The team

Salem & Milwaukie.

Two people, ninety miles apart, building the same platform.

Gus · Salem, Oregon

Founder. Builder. First user.

Writes the code, wires the hardware, produces the shows. Dromlight is the tool he wanted to exist — and when it didn't, he built it. Everything on this site has passed through his hands.

Kage · Milwaukie, Oregon

Collaborator. Pipeline partner.

Learning the pipeline, shaping the workflow, contributing to the shows. Dromlight is built to be a two-person studio that can scale beyond two people — and Kage is the proof it works with more than one.

The story — placeholder, needs Gus's voice

How we got here.

Dromlight started with a question that most people building AI right now aren't asking: what if the AI didn't replace the person doing the work?

Every generative music tool on the market is the same shape. Type a prompt. Wait. Get back an output you had no hand in shaping, from a model you don't own, hosted on servers you can't see. The tools treat the human as the customer, not the collaborator. And the results feel like it.

We wanted something different. A studio, where the AI is an instrument in the room — something you play, correct, shape, argue with. Where the person making the thing is still making the thing. That's not a slogan; it's why the platform has a piano roll and an effects rack instead of a "generate" button.

We built it because it needed to exist. We ship it because now other people can use it too.

The way we work

We treat the AI like a collaborator, not a servant. We argue with it, correct it, get frustrated with it. And in return, we get better work out of it than the people who treat it like a magic wand. That relationship is the whole point — and it's baked into every tool Dromlight ships.

The stack

We own the hardware.

Dromlight runs on machines we can touch. AI inference, voice generation, music models, storage — all local, all ours. No third-party cloud in the critical path.

That matters for two reasons. First: nothing about your work is at the mercy of someone else's business decision. Second: when we tell you a voice sounds a certain way, or a mix hits a certain quality bar, that's a promise we can keep — because the model isn't going to get quietly retrained next month.

Independence isn't a marketing story here. It's an operational choice.

The name

Dromlight.

A drom is a road. A path with movement in it. Dromlight is what you build for the road ahead — a lantern for the work, when the work is figuring out what work should even look like.