{"id":109975,"title":"Osseus: The intelligent development platform for robotics","tagline":"Build robots at the speed of software. Trace and fix all the downstream impacts of a design change.","body":"**TL;DR:** Osseus plugs into the tools a robotics team already uses and crafts a live dependency graph of the entire robot. When you change a part, our agents trace what it affects across mechanical, electrical, and software, re-run the tests and sims, and then propose fixes in a branch for engineers to merge in.\n\n**Ask:** If you work in robotics, as a professional or hobbyist, please reach out. Details at the bottom, or find us at [founders@osseus.ai](mailto:founders@osseus.ai).\n\n\u003chttps://youtu.be/tEpkmA42fSA\u003e\n\nHey everyone, we’re Anish and Ayush from Osseus. We’re building the intelligent development platform for robotics.\n\nThe age of robots is coming, and will not be unlocked by better AI models alone. Robot development is still messy and broken: every iteration crosses mechanical, electrical, software, suppliers, and testing, while the reasoning is scattered across tools and people. We’re building Osseus to make robot development agentic, compress the iteration cycle, and drive the avoidable cost of each design change to zero.\n\n**The problem: One component change can break an entire robot build. A requirements error discovered during integration and testing can cost up to 78x more to fix than one caught upfront.**\n\nImagine the specified drive motor has a months-long lead time, or is underpowered, so the team selects a replacement. It looks similar, but it has a longer housing, draws more current, uses a different connector, and reports motion differently.\n\nTo the mechanical team, it is a motor swap. To electrical, it is a current and connector change. To software, it is a calibration change. The bracket, wiring, motor controller, thermal limits, firmware, requirements, and tests may all need review, but that chain is scattered across different tools and teams. Nobody sees the whole robot until integration fails.\n\n**What we do: Trace the change, prepare the fixes, and validate them before the build.**\n\n* **Build the requirements graph.** Osseus connects into the tools a robotics team already uses (CAD, ECAD, GitHub, Jira, docs, test runs) and crafts a live dependency graph of the entire robot. The extracted requirements are related to every component, decision, test and evidence that proves it.\n* **Trace downstream impact.** When a change is made or being proposed, Osseus identifies the affected hardware, software, requirements, owners, tests, and simulations.\n* **Run CI/CD across hardware and software.** Osseus' agents find which requirements may be compromised, run the attached tests and sims, create fixes for the affected hardware/software on branches, and re-run the tests to confirm the new design doesn’t break downstream.  Engineers see the proposed changes and evidence before approving and merging them.\n\n**Design with parts you can actually get.**\n\nThe 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.\n\nThis 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.\n\n**Design review that remembers.**\n\nEngineers can see why a component was chosen, what was tried previously, and why an earlier design failed. Suppliers can comment directly on a part through a secure link. If a supplier flags that something cannot be manufactured or suggests a change that reduces cost, that insight stays connected to the design and resurfaces when relevant.\n\n**The team**\n\nWe’re Imperial College London engineering and computer science graduates. Between us, we’ve done robotics research at Imperial, ML research at a Harvard-HKU lab, and built agentic systems at Apple.\n\n![uploaded image](/media/?type=post\u0026id=109975\u0026key=user_uploads/1409413/c2262c87-4d8b-4f68-a69d-3ec56d3eb217)\n\n**How you can help**\n\nWe would love to speak with, or intros to:\n\n* VPs and Heads of Engineering, Robotics, Systems, or Hardware at companies building physical robots.\n* Robotic engineers who have felt the pain of integration.\n* Hobbyists, university teams, and independent builders who build or modify robots.\n* Anyone who has spare components they would list, or are looking to buy/rent.\n\nWe’re onboarding in waves - sign up to the [waitlist here](https://osseus.ai/)! Email us at [hello@osseus.ai](mailto:hello@osseus.ai) or[ book a call](https://osseus.cal.com/founders/osseus-intro).","slug":"Sbn-osseus-the-intelligent-development-platform-for-robotics","created_at":"2026-08-11T13:30:00.269Z","updated_at":"2026-09-19T04:00:51.902Z","total_vote_count":59,"url":"https://www.ycombinator.com/launches/Sbn-osseus-the-intelligent-development-platform-for-robotics","share_image_url":"//bookface-static.ycombinator.com/assets/ycdc/yc-og-image-c440a0ad1dacfb86eeeb343717479cc54d256614449b4ef719977a0a451f8bc8.png","company":{"id":33540,"name":"Osseus","slug":"osseus","url":"https://osseus.ai/","logo":"https://bookface-images.s3.amazonaws.com/small_logos/fd39ca163a2a8ea396a6ec66701926317f9f416c.png","batch":"Summer 2026","industry":"B2B","tags":["Artificial Intelligence","Robotics","B2B","Biotech","Healthcare"],"search_path":"https://bookface.ycombinator.com/company/33540"}}