Curiosity, Engineered.
Bineary builds the infrastructure layer for teams who ask better questions — typed end to end, observable by default, and quick enough that “why?” costs you seconds instead of sprints.
Speaks the stack you already run
Four primitives. No platform tax.
Bineary is a small set of sharp tools that compose, not a walled garden you have to move into. Adopt one piece; keep everything else exactly where it is.
Every request explains itself
Traces, logs and metrics are emitted by the runtime itself, correlated before they leave the process. No agent to install, no sampling guesswork, no separate SDK to keep in sync with your code.
Typed end to end
Schemas defined once flow through the client, the queue and the database. Breaking changes fail at build, not at 3am.
1 const charge = defineTask({
2 input: ChargeInput,
3 run: ({ input }) => pay(input),
4 });
5
6 // ^? Task<ChargeInput, Receipt>Fast enough to stay curious
A Rust runtime with WASM isolates. Cold starts you can ignore, so experiments never get vetoed by the build clock.
Runs where you already run
Your cloud, your VPC, your compliance boundary. The control plane never needs to see your data to keep it observable.
Boring on purpose
Declarative config, reversible deploys, budgets that page you before your customers do.
- Instant rollback to any prior revision
- Error budgets wired to alerting
- Config as code, diffed on every PR
Four hops from question to answer.
Most stacks make you assemble the story after the fact. Bineary keeps the story assembled the whole way through.
Your code stays your code
One import. The runtime instruments the boundaries it already owns — handlers, queries, queue consumers — and leaves your business logic untouched.
0 agents to install
Three commands, not a three-week migration.
The fastest way to lose curiosity is to spend a sprint wiring up the tooling meant to protect it. Bineary is designed to be useful before lunch.
$ npm i @bineary/runtime$ bineary init ✓ project linked atlas · eu-west-1✓ telemetry enabled 4 sinks detected✓ ready in 1.8s 0 config files written $ bineary dev → runtime http://localhost:7070→ explorer http://localhost:7070/traces→ watching 12 handlers · 0 errorsNo sidecars, no agents, no daemon set.
The full stack runs on your laptop, offline.
OpenTelemetry in, OpenTelemetry out. No lock-in.
Curiosity is the input. Engineering is what makes it repeatable.
Bineary started from a small frustration: the best engineers we knew were spending their curiosity on tooling instead of on their actual problem. We are building the layer that gives it back.
Ask smaller questions, faster
A question that takes a day to answer stops getting asked. We optimise for the second question, and the tenth — the ones that only get asked when the first one was cheap.
Make the invisible legible
Systems fail in the parts nobody can see. Our job is to move the interesting behaviour out of the dark and into something a person can read on a Tuesday afternoon.
Earn the right to be boring
Novelty belongs in the product, not the plumbing. Everything underneath should be so predictable it disappears — reversible, observable, and dull in the best way.
Bring us your hardest question.
We are onboarding a small number of teams by hand. Tell us what you are trying to see inside your system, and we will tell you honestly whether we can help yet.
Usually a reply within a day · no sales sequence