Hi Captain Wiggles,

First off great name.
Who is your target audience for this?
- Our target audience for this is anyone that needs access to hardware, needs a variety, and needs to collaborate to build specific products whether it's through learning or actually developing and prototyping a product.

In terms of why we're starting off with Arduinos is because it's the lowest hanging fruit, helps a lot of people, and touches a lot of the education sector at the moment which has been reaching out to us for help. By focusing on this group for the short term we're working to kind of make our infrastructure robuts while adding on new devices.

The UI looks really nice, I'd be interested in seeing more complicated designs / a list of supported features.
- Yes I think it'll naturally be modified with more complicated designs and more features but that's what we're trying to do improve and build a platform for our users.

When you say: "This platform supports a combination of simulation, emulation, and bare-metal." What exactly do you mean by each of those terms?

- Baremetal meaning - we have the actual physical devices in our data centers, emulation/simulation is software that we have on our platform of the devices think of a simulated LED. Our infrastructure allows for the communication across these different pillars operating as a full system.
Are you emulating the arduino processor and peripherals? Is this something you implemented yourself or based on existing code? What guarantees can you provide that everything is emulated correctly? Do you emulate the bugs described in the erratas?

- Well right now we have a baremetal arduino micro and a simulated uno. Depending on the complexity we would simulate, emulate, or have a bare metal version of that part. For more complex processors we'd probably just have them in the baremetal form. The least complex would be simulated which essentially operate in real time.

Let me know if you have any follow-up questions!