Built in the Open
Legibility is the floor,
not the feature.
Before a platform can earn the word open, it has to ship. Six years of engineering sit beneath this one, and three robots that left the bench and met the world.
On this page
- The record, in order
- What open means here
- Six principles we hold to
- How work lands
- What we will not do
The record, in order
Machines first,
platform second.
We did not design a platform and then look for robots to justify it. The platform is the residue of building machines that had to work in front of people who had paid for them.
- Shipping since
- 2018The first machine left the bench and went to work.
- Robots delivered
- ThreeComplete machines, built end to end.
- Engineering behind it
- SixYears of engineering, and where the tooling came from.
- Source
- PublicRead it, fork it, run it yourself.
-
2018: the first robot leaves the bench
A complete machine, delivered and operated outside our own workshop. Everything we believe about simulation fidelity, deployment discipline and the cost of closed tooling comes from that year rather than from a whiteboard.
Where the opinions came from -
Two more machines, and the same bottleneck twice
The hard part was never the robot. It was the stack around it: a simulator that disagreed with the floor, data nobody could reproduce, a deployment path assembled from scripts, and reuse that was technically possible and economically pointless.
The problem, confirmed -
The tooling becomes the product
What we built to get our own robots out of the door turned into the Development Studio, the template library and the runtime underneath them. The Creator Hub followed from the observation that we kept rebuilding work other people had already finished.
Six years of engineering -
Today: the platform, in public
The repositories are public, the Studio and the Hub are in use, and the economy pays contributors out of real usage. Parts of the roadmap are unfinished, and those parts are named as unfinished on this site and in the repositories.
Open, now
What open means here
Six commitments,
stated so you can check them.
Open has become a marketing word. These are the specific things we mean by it, written in a form that can be falsified.
- Public repositories
- The platform source is public. Not a sample, not an SDK wrapped around a closed core. If the behavior of the system surprises you, the explanation is in a file you can open.
- Readable source
- Code is written to be read by somebody debugging a machine at an awkward hour. That is also why the runtime is deliberately small: a stack nobody can reason about is not open in any useful sense, whatever its license says.
- Forkable, and meant to be
- You can take the source and bend it toward your own machine. Forks are a normal outcome of open development, not a failure of ours, and fixes that come back are paid for through contributor rewards.
- Portable work and data
- Projects, datasets and published assets can be exported in formats that are useful outside the platform. Portability is designed in, because a tool you cannot leave is a tool you do not own.
- No engineered dependence
- Nothing about the platform exists to make leaving expensive. We would rather compete on being worth using than on being hard to escape, and that choice is visible in the file formats.
- Honest roadmaps
- Unfinished work is described as unfinished. The low and no-code builder is in progress, the challenge program is widening, and the template library grows with every production deployment. A roadmap is only useful if the parts marked done can be trusted.
Six principles
What we hold to
when the choice is hard.
Ownership over access
A license to use somebody else's robot is not the same as owning one. We design for the person who wants the machine, the behavior and the data to be theirs, including the right to walk away with all three.
Reuse over reinvention
The field is slowed less by missing ideas than by work that exists in private and gets rebuilt. Making reuse pay is the single highest leverage thing a robotics platform can do, so the Hub is not a side feature.
Legibility over convenience
When a shortcut would hide how the system works, we take the longer path. Magic is pleasant until the morning a robot behaves in a way the documentation does not explain.
Shipped over announced
Three robots and six years taught us to distrust claims that have never met a floor, a payload or a customer. We would rather publish less and have it be true.
Compounding over head starts
Closed stacks are faster for a quarter. Open is faster for a decade, because every fix and every published asset stays in reach of the next person who needs it.
Plain language over positioning
If a sentence about this platform would not survive a conversation with an engineer who has shipped hardware, it does not belong on the site or in the documentation.
How work lands
In public,
and in order.
Somewhere, in the open, someone is improving the very thing you will build on tonight.
- Changes arrive as versioned releases. Every build the platform produces is identified, so a robot's software can be named instead of guessed at.
- Fixes travel outward. A patch that solves your problem solves it for the next person, which is the entire argument for working this way.
- Contributions are paid. Work that improves the platform is eligible for contributor rewards, funded by usage and not by goodwill.
- Evaluation is shared. Results are reported against shared evaluation packs with stated conditions, so a claim can be checked instead of believed.
- Limits are published. Where the simulator diverges from reality, or a behavior only holds on certain bodies, that belongs in the description, not in a support conversation later.
The workshop never fully closes
This is the quiet advantage of building in the open. Progress continues while you sleep, in repositories you can read, by people whose incentives point the same direction as yours.
Said plainly
What we will not do.
Commitments are only meaningful where they cost something. These four would cost us revenue, and that is why they are worth writing down.
No closed formats for your own work
Your projects, data and assets will not be held in a format only we can read. Export exists and will keep existing.
No taking ownership of published work
Publishing to the Creator Hub grants use under terms you set. It does not assign your rights to us, now or in a later revision of the terms.
No overselling the simulator
Simulation removes cheap mistakes. It does not replace hardware, and we will not describe it as though it does in order to shorten a sales cycle.
No silent roadmap
Features in progress are labeled in progress. If something slips, the honest version appears here instead of quietly disappearing from the list.
“A robot you can read
is a robot you can own.”
Questions we get
Open, asked directly.
If the source is public, what does IMPLESS sell?
Platform services that cost money to run, marketplace settlement, and the enterprise features a fleet operator needs: deployment management, access control, audit and support. The code being readable does not make hosting, metering or operating free, and it does not make them less valuable.
Can I use the platform without any commercial relationship?
Yes. You can read the repositories, build the stack and run it on your own hardware. Many people will start exactly that way, and some will never need anything else from us.
Why only three robots in six years?
Because they were complete machines that had to work for somebody other than us, and because most of those years went into the tooling that made the third one less painful than the first. We would rather report three honestly than inflate the number with prototypes.
How do I know you will still be open in five years?
You do not have to take our word for it, which is the point. The source is public, your work exports, and a fork is a real option, not a threat. Those are structural guarantees, and they outlast any promise a company makes about its own future behavior.
Build with us
Come and
read the work.
Tell us what you are building and which part of the platform you want to look at first. We will send you to the right repositories and the right people.