Now it is time to build

Tell us what
you want to build.

Publishing your first skill to the Hub, carrying a fleet from simulation into production, or simply working out whether open robotics could work for your team. We read everything that arrives.

Before you write

  • Name the body you are building for
  • Say which stage you are at
  • Send a link if there is one to send

Technical questions are welcome in the first message. They usually get a better answer than a meeting would.

Write to us

A few fields,
and the detail that matters.

The form composes a message in your own email client, so you keep a copy of what you sent and nothing passes through a third party on the way.

Email
hello@theimpless.com
Telephone
(773) 856-0094
Post
146 N Kingsley Dr
Los Angeles, CA 90004
Company
IMPLESS LLC, building robotics in the open since 2018.

Submitting opens your email client with everything filled in, addressed to hello@theimpless.com. Writing to us directly works just as well.

01

What happens next

No funnel,
no sequence of emails.

  1. Somebody who builds reads it

    Messages are read by people who work on the platform, not routed through a qualification script. If your question is technical, the first reply will be technical.

  2. You get a specific answer

    We will point you at the repositories, templates or targets that apply to your robot, and tell you plainly where the platform is unfinished for what you are trying to do.

  3. A call only if it is useful

    If the question needs a conversation, we will suggest one. If it does not, we will answer in writing and leave your calendar alone.

02

What helps us answer well

Detail is not
an imposition.

A short message is fine. A specific one gets a better reply, because we can check the actual constraint instead of guessing at it.

  • The body. Arm, quadruped, mobile base, something of your own design, or undecided.
  • The task. What the robot has to accomplish, and in what environment.
  • The stage. Reading, simulating, on hardware, in production, or operating a fleet.
  • The constraint. Compute budget, timeline, certification requirement, or the thing that is currently blocking you.
  • The ask. Access, a technical answer, a partnership, or a second opinion on an approach.
03

Read first, if you prefer

Three pages that
answer most questions.

I

The Development Studio

What the environment contains, how the bridge from simulation to production works, and what the real-time runtime underneath is for.

Open the Studio page II

The Creator Hub

What you can publish, how a royalty reaches you, how quality is established, and what you keep when you publish.

Open the Hub page III

The Token

The four flows of the economy, why it is funded by usage instead of emissions, and what the token explicitly is not.

Open the Token page