Skip to content

Makerfield / Patch OS

One workspace.
From code to connected systems.

Develop firmware, inspect device data, and test workflows in Patch OS, Makerfield’s engineering workspace.

Explore the guest sandbox · Sample data, no account needed

Patch OS/ Greenhouse LabWorkspace preview

Firmware

Code Studio

Edit and organize source files.

Explorer
src
main.cpp
platformio.ini
main.cpp
struct Reading {  float celsius;  unsigned long uptime_ms; }; void loop() {  Reading sample = {    readTemperature(), millis()  };  publishReading(sample); }
Illustrative interface · not connected to hardware

The platform

An engineering platform. Connected by design.

  • Build

    Edit firmware and export your source.

  • Connect

    Register boards and set up secure device credentials.

  • Observe

    Inspect the data your devices send.

  • Automate

    Design and test visual workflows.

Inside Patch OS

Three views of one system.

01 / Code to artifact

Start with the exact source.

Import a pinned public repository, edit firmware in Code Studio, and choose a target. Export the source for a local build or compile with a configured worker.

Open Code Studio
FIG. 01Code Studio / Example
  1. SourcePinned commit
  2. src/main.cppFirmware entry
  3. platformio.iniBuild target

02 / Device to data

Read what the board sends.

Give a board its own device identity. Send readings over HTTPS or a configured MQTT relay, then inspect the time series in Observatory.

Open Device Cloud
FIG. 02Device Cloud / Example
Sensor temperature
29.4 °CSample series · not live

03 / Events to actions

Test the rule before the relay.

Connect an input, a condition, and an output in Automation Studio. Run sample data through the graph and inspect the log without sending hardware commands.

Open Automation Studio
FIG. 03Automation Studio / Example
  1. Sample inputtemperature: 29.4
  2. Thresholdabove 28 °C
  3. Log resultcondition matched

Engineering sequence / operator guided

From the first commit to a connected system.

These are handoffs, not an automatic deployment pipeline. Compilation needs a worker; approval and flashing happen outside Patch OS.

  1. Repository

    Pin a public commit.

  2. Project

    Edit the imported source.

  3. Build

    Compile on a configured worker.

  4. Artifact

    Collect the build output.

  5. Deployment

    Review and flash locally.

  6. Device data

    Send a reading over HTTPS.

  7. Automation

    Test a rule with that input.

Solutions

For people who build with hardware.

Embedded development

Choose a target in Code Studio and export a project for the bench.

Robotics and edge systems

Review ROS configuration and generated package files in the board configurator.

IoT operations

Identify a device in Device Cloud and inspect its readings in Observatory.

Education and research

Explore a sample workspace and use simulated inputs to teach threshold logic.

Developer field notes

Know what’s ready.

Open the workspace library
Available
Browser editing, pinned public repository imports, project ZIP exports and the example library.
Preview
Use the guest workspace to explore sample device data and simulation without connecting hardware.
Requires setup
PlatformIO builds need an external worker. MQTT ingestion needs a configured broker and relay.
Planned
Signed over-the-air firmware delivery is not available. Use a local flashing workflow.

Your next project

Bring your next system together.

Start with a project. Build toward a connected workflow.

No account needed for the guest sandbox.