End-to-end robotics development intelligence

The intelligent development platform for robotics.

Osseus plugs into the tools a robotics team already uses and builds a live dependency graph of the entire robot. Change a part and Osseus traces every downstream impact across mechanical, electrical, and software, prepares the fixes on a reviewable branch, reruns the relevant tests and simulations, and hands engineers validated changes to approve and merge.

Get a demo Join the waitlist
Backed by Y Combinator Built for robotics R&D teams

Change one part. Osseus traces every impact and prepares a tested branch.

Osseus follows each revision across CAD, electronics, firmware, requirements, and tests. It prepares the connected fixes on a reviewable branch, reruns validation, and leaves approval and merge to your engineers.

Learn more
See Osseus handle
Change detectedDrive motor · MX-18 → MX-24New mount · +4 A peak current
Motor
swap Motor bracketWiring + power boardMotor firmwareRequirements + tests
  • Motor bracketResize
  • Wire harnessHeavier gauge
  • Motor firmwareRetune limits
  • Requirements + testsUpdate
Reviewable branch ready motor-swap/mx24 6 updates · CAD, wiring, firmware, requirements + tests
Review branchView changes3 owners

Validation rerun12 / 12 passed

Ready to merge
  • Mount + clearance simulationPass
  • Power + firmware testsPass
Part changeBattery pack · v2+180 g · +2.4 W
Mass94%Power61%Thermal44%

Over60 g

1.8 kg reserve
Reviewable branch ready battery-pack/lighten-bracket 4 updates · CAD, parts list, payload requirement + test
Review branchView changesME owner

Re-checked80 g clear

1.8 kg reserve
  • Payload requirementPass
  • Weight limitPass
Safety requirementEmergency stop cuts motor torque in ≤ 100 msSafety requirements · robot v2
RequirementEmergency stop ≤ 100 msEvidenceE-stop timing test · passed

Gap1 test missing

Full coverage
Reviewable branch ready safety/e-stop-timing 3 updates · requirement, test plan + validation script
Review branchView changesQA owner

Re-checked74 ms

100 ms limit
  • E-stop timing testPass
  • Requirement coverageComplete
Your engineering ruleWhen an actuator changes, check bracket fit, wiring current, control limits, and the tests tied to them.
  • Part or spec changesTrigger
  • Connected files + testsTrace
  • Branch + validationOutput

Over3.2 A

Wiring limit
Reviewable branch ready actuator-swap/joint-4 5 updates · wiring, control limits + tests
Review branchView changesEE + FW

Re-checked1.8 A clear

Wiring limit
  • Joint 4 currentPass
  • Your engineering checkPass
Step 1 of 5

A drive motor changes. Osseus reads the new mount, power, and control details from the source revision.

Why Osseus

Tradeoffs priced before you commit, designs shared with your supplier in one click, every signal owned by a person, and connected documents that keep up on their own.

Learn more

Evaluate the change before it becomes a revision.Compare the current architecture with a proposed redesign on requirements, performance, and BOM cost. Osseus then drafts the simulations, tests, and design updates needed for approval.

Change study · 5 V power architecturehexapod_mk2_main · v2.0 proposal · evaluated against requirements and supplier evidence CurrentProposal
Current architecture Pololu D24V90F5, external 5–38 V in · 5 V / 9 A typical · off-board with XT30 pigtails
Proposed change DFR0753, onboard power stage 6–14 V in · 5 V / 8 A · 40 W · mainboard-mounted
Two decision metrics · manufacturer specifications
Rated output currentMeasured peak: 7.2 A Current · 9 A typ. Proposal · 8 A
Supported input rangeProject: 6.4–8.4 V Current · 5–38 V Proposal · 6–14 V
Supplier data: Pololu item 2866 and DFRobot DFR0753 · checked 11 Aug 2026
Build verification plan 3 checks proposed Change assessed against connected requirementsElectrical, battery, thermal, BOM, and verification evidence checked
  • Battery operating windowDFR0753 starts at 6 V; rerun the low-SOC servo transient against the 6.4 V requirement.Test drafted
  • Input protectionThe current module includes reverse-voltage protection; preserve that protection upstream.Circuit change drafted
  • Thermal envelopeThe 40 W stage moves inside and is specified to 70 °C; rerun board and enclosure thermal cases.Simulation + test
Review each proposed check or change. Nothing is written until the responsible owner approves.

One click, and your supplier is in the review.Share the exact schematic or drawing revision as a view-and-comment link. Feedback comes back pinned to the dimension it means, auto-translated, and every manufacturing constraint is saved for the next design.

Leg Measurement Drawing.pdfCenter to leg motor measurements · sheet 1 of 1 · Hex1 CAD Version 2 V1 releasedV2 staged
The Hex1 leg measurement drawing with the released V1 position of the S2 and S5 legs in red and the staged V2 position in green S2_x −110.0 · V2 S5_x 110.0 · V2
❐Comparing V2 and V1✕
1JLJordan LeeMechanical engineer

S2 and S5 motor centres move from ±108.5 to ±110.0 mm for the new lower-leg bracket. V1 stays released until this review closes.

2林Lin WeiMachining supplier · external guest

整块底板在我们的三轴机床上，孔位只能保证 ±0.1 毫米。±110.0 没问题，但公差再小就要上坐标镗，成本翻三倍。

Auto-translated · Chinese to English

Across the full plate our 3-axis mill holds ±0.1 mm true position on these bores. ±110.0 is fine, but anything tighter means jig boring at three times the cost.

Supplier constraint saved

±0.1 mm true position on the S2 and S5 bores

Carried into your next design review of this part

Every signal becomes work somebody owns.A supplier constraint, a design check finding and a cost opportunity land in one queue, each still carrying the revision it came from. Jira is written only after a person approves the draft.

5 open itemsEach one keeps its origin, its source revision and a single owner Filter · Open
Supplier constraint Hold ±0.1 mm positional tolerance on the leg motor bores Leg Measurement Drawing.pdf · V1 → V2 · saved from Lin Wei JLJordan Lee In review
Design check Size the 5 V rail and the leg contact for simultaneous servo startup Hexapod_Controller_Rev1.sch · Rev 1 electrical · 1 high finding DCDana Cole Open
Cost opportunity Quote MJF PA12 for the S2 segment at 24 units Hex2 BOM · v2.0 staged · $216 to $384 estimated MCMaya Chen Estimate
Engineer comment Define datum, units and positional tolerance on the leg drawing Leg Measurement Drawing.pdf · released · raised in review H1-08 JLJordan Lee Open
Verification Rerun the level, pitch, roll and servo startup checks Validation plan · draft · blocked on the clearance decision SRSam Rivera Planned
5 Jira issues drafted, none createdTitle, evidence links, owner and acceptance checks are ready for a person to approve.

Your internal documents are updated by the change, not after it.Osseus knows which getting-started page, BOM sheet, controls map and interface document read each part, pin and connector. When a revision merges it drafts the exact edit into every one of them, in the tool that owns the document, and holds it until an owner approves.

hexapod_mk2_main · v1.0 → v2.0 mergedAutodesk EAGLE 9.6.2 · 28 differences read from the source: 12 part, 16 net 6 documents read this revision
What changed in the source
  • E_STOP connectorXT30XT60
  • Overcurrent protectionF1 · 3557-2 fuse holder added
  • 5 V supplyexternal moduleonboard DFR0753
  • Level shifterU1 74LVC1T45GWU2 SN74LVC1T45DBVR
  • Signal pinsLEDSIG 33 · PWRSIG 319 · 11

Read from the pinned v1.0 and v2.0 Eagle files. No number here is typed by hand.

Internal documents that read it — each edit drafted in place
getting-started.mdGitHub · docs/Hex2 · owned by Dana Cole Plug the battery into the XT30 pigtailPlug the battery into the XT60 e-stop pigtail CheckingEdit draftedUpdated
hexapod_bom – electrical.pdfSharePoint · Hex2_resources/BOM · owned by Maya Chen 12 V → 5 V converter, externalDFR0753 onboard buck · F1 3557-2 fuse holder CheckingEdit draftedUpdated
controls_mapping.pdfSharePoint · Hex2_resources · owned by Priya Raman PWRSIG on Teensy pin 3PWRSIG on Teensy pin 11 CheckingEdit draftedUpdated
common-commands.mdGitHub · docs/Hex2 · owned by Dana Cole status LED on pin 33status LED on pin 19 CheckingEdit draftedUpdated
Hex2 harness interface documentConfluence · Electrical space · owner not set Level shifter U1 74LVC1T45GW,125U2 SN74LVC1T45DBVR · check I/O direction CheckingNeeds an ownerNeeds an owner

Also read: 2024-11-05_heatset_insert_guide.pdf — nothing in it depends on this revision, so it is left alone.

Every edit is written by Osseus into the tool that owns the document, and only after the document owner approves the draft. Document wording is illustrative; the revision delta is read from the pinned Eagle sources. 4 approved and written1 held for an owner
The Problem

The robot is one system. Its R&D record isn’t.

Mechanical designs, robot models, software, test results and supplier feedback live in different tools. Each system records its own artefacts, but no single record shows why a change was made, what else it affects or what needs to happen next.

Up to 70%

less time maintaining requirements, freeing systems engineers to focus on architecture.

Up to $100K

lost in one failed early-stage robotics design cycle.

Up to 3×

more test coverage in the same engineering hours, helping teams catch conflicts earlier.

Up to 78×

the late-stage cost multiplier avoided when a requirements error is caught before integration and test.

Four kinds of work. One permissioned record underneath. Every artefact version, result, decision, supplier constraint and owner stays connected in the memory layer. Explore the memory layer →
Marketplace

Design with parts you can actually get.

The Osseus Marketplace brings nearby component availability and lead times into the design process. If the specified motor is unavailable, teams can find compatible alternatives to buy or rent and compare their effects on geometry, power, thermal limits, software, and testing before committing.

This helps builders keep prototypes moving instead of waiting weeks for parts. Teams and individuals can also monetize spare components and unused prototyping hardware by listing them for sale or rent.

Browse the marketplace
Practical answers

Got questions?

A few things robotics teams usually ask before we connect their first systems and workflows.

More questions? Chat to us.

What robotics design data can Osseus connect?

Osseus connects CAD and drawing revisions, schematics, BOMs, supplier feedback, robot software, simulations, tests, issues, requirements, and controlled documents. Builders can import files and BOMs directly; larger teams can connect permissioned systems and external revision histories.

Does Osseus change designs or publish documents automatically?

No. Osseus traces likely impact and prepares Jira issues, document updates, and validation work as reviewable drafts. The responsible owner approves each downstream action, and released documents remain immutable.

How do supplier translation and external design intelligence work?

Supplier reviews retain the original comment alongside an automatic English translation. External intelligence is optional and policy controlled; every community signal includes its direct source and requires engineer review before it informs a design decision.

How does Osseus keep our data secure?

Osseus mirrors your existing roles, permissions and confidentiality structure, so an agent can only retrieve what its owner is already allowed to see. Promotion into shared memory is governed, logged and default-deny. Your data is never used to train foundation models. You can read more on our security page.

Can we run everything on-prem?

Yes. Deployments can run with your own API keys, in your own cloud or VPC, so your data stays inside your boundary.

Do we bring our own model keys, or do you provide the subscription?

Both are supported: bring your own model keys and cloud, or use the managed Osseus subscription.

How much does Osseus cost?

Builder, Team, and Enterprise plans scale from one-person projects to permissioned multi-team deployments. Compare plans, then get early access and we will scope the right setup with you.

Secure by architecture

Robotics design intelligence, secured by architecture. Privacy built in.

✓Mirrors your existing roles, permissions, and confidentiality structure
✓Governed, default-deny memory promotion
✓Your keys, your cloud. Never trained on your data
✓SOC 2 · ISO 27001 · HIPAA · GDPR. Available on request
Learn more about permissions & security →

The permission boundary, mirrored from your existing tools

Chat with us!

Let’s have a chat about the designs, suppliers, and connected workflows that matter most to your team, and where to start.

Get a demo

Built by engineers and researchers, for engineers and researchers.