Company

Roborama operates instrumented robot facilities and sells statistically defensible evaluation as an API.

Thesis

Every robotics team is about to face the same question from a customer, an insurer, or a regulator: how do you know it works? Today the honest answer involves a borrowed lab, a spreadsheet, and a sample size chosen by fatigue. We think the answer should be a function call — roborama() — that returns a number with error bars, from real hardware, on pinned versions, at a price quoted in advance.

We are building the boring, load-bearing layer of the robotics stack: cells, scripted resets, calibrated instrumentation, and an API whose every result carries n and a confidence interval. Simulation companies are our counterparties, not our competitors — verify() exists to make simulators better, and calibration ground truth is a product line, not an accident.

Principles

Statistics are an input. Sample size is chosen before the run (episodes="auto(ci=0.95, moe=0.03)"), not defended after it.
Versions or it didn't happen. Robots pin firmware, environments and suites pin revisions, and @latest resolves to a recorded pin.
Two visible meters. Robot-hours × environment-hours, in every quote and every result.
Legible to agents. Every page on this site has a markdown twin, the API is one curl away, and /llms.txt orients an agent in one request.

Team

A small group out of robot-learning labs and infrastructure companies, currently heads-down building. Bios will appear here when the platform ships; until then the work speaks in the docs and the research notes.

Brand

The mark is a function call. The name is set in Newsreader Light, the parentheses in Geist Mono — that recipe is the whole logo. It is monochrome everywhere; the green belongs to returned values only, never to the mark. There is never a robot illustration in the mark. And it is always typeable: roborama() works in an email, a terminal, or a legal footer.

roborama()r()

Assets: download the brand kit — path-based SVGs of both marks, the OG image, and favicons — or right-click the logo in the header.

Careers

We hire people who think resets are interesting. Open stubs:

Facility systems engineer — scripted resets, calibration, uptime.
Evaluation statistician — interval methods, sequential designs, paired comparisons.
Developer experience engineer — SDKs, docs, and the agent surface.

Write to careers@roborama.com with something you've measured carefully.