Each system carries the next
We build small systems that stay running, so the next change extends the loop instead of starting over.
Ourobeam Studio
Software that stays up, for people and agents.
Ourobeam is an independent studio. We build on Elixir and the BEAM, and we use Midnight when an app has to prove a fact without showing the data underneath.
We build software that can run for years, answer a person, and answer an agent.
Software has to stay after the launch
A system written for a launch starts to drift once the team moves on. Agents now call the same systems people do. Private data cannot sit in the open just so a check can be made.
We build the part that has to keep its word. Elixir on the BEAM for the running system. Midnight when a fact must be shown and the record behind it must stay put.
What we hold
A failure returns to its place
On the BEAM, a process that stops is restarted by the one watching it. The rest of the system keeps its place.
A proof can leave the record private
On Midnight, an app can show that a rule held. The data behind that proof stays with the person who owns it.
How a piece of work starts
-
01
Write the note
Tell us what must keep running, and who calls it. A person, an agent, or both.
-
02
Name the boundary
We say what is public, what stays private, and what the runtime is responsible for holding.
-
03
Build a system you can keep
You get a small system you can run and watch. The next change starts from that system.
What the systems run on
- Elixir · the language
- BEAM · the runtime
- Midnight · when the proof and the record part
- Phoenix · the pages people read
Questions
What does the studio build?
Long lived software on Elixir and the BEAM. When a product has to prove a fact without exposing the record, we build that part on Midnight, a data protection network and a Cardano partner chain.
Who is it for?
Teams that need one system a person can use and an agent can call. The rules should live in one place, not in two products that drift apart.
Why Elixir and the BEAM?
Elixir runs on the BEAM. Processes are small, they supervise each other, and a failure can return to a known state while the rest stays up. That fits software which has to remain available while it changes.
What is Midnight in this work?
Midnight keeps a public ledger and a private state. A zero knowledge proof lets the network check a result without receiving the raw data. Selective disclosure is a rule about who may see a specific part, and when. We use Midnight when that split is the product. We do not put every app on a chain.
Why the name Ourobeam?
Ouroboros is the serpent that meets its own tail. Ouroboros is also the consensus protocol family Cardano uses. BEAM is the runtime Elixir runs on. The studio sits on that loop: a system that can carry the next one.
Do you list products on this page?
No. A public system keeps its own name and its own site. This page is the studio, not a catalog.
How does a conversation start?
Write to [email protected]. Tell us what the system has to do and what must stay private. We reply with a yes, a no, or a question.
Tell us what has to keep running.
The first note costs nothing. No card, no deck, and no retainer to hear back. If we are the wrong studio, we say so.