Electronics Guide

Arduino Cloud Editor

The Arduino Cloud Editor is Arduino's browser-based development environment, designed to make embedded development accessible while scaling from beginner projects to connected IoT applications. The tool launched as the Arduino Web Editor within the broader Arduino Create suite; Arduino has since unified its online tooling under the Arduino Cloud brand, with the editor reachable through the Arduino Cloud web application. The platform combines a web-based code editor with cloud compilation, device management, and integration with Arduino's extensive hardware ecosystem.

Web Editor Features

The Cloud Editor provides a browser-based coding environment with syntax highlighting, auto-completion, and inline error checking tuned for Arduino development. It maintains the familiar Arduino programming model, supporting the setup() and loop() structure along with the extensive Arduino API standard in maker and educational communities. A 2024 redesign brought the interface and library manager closer to the desktop Arduino IDE 2.x and broadened board support: where earlier versions targeted official Arduino boards plus selected ESP32 and ESP8266 modules, the current editor recognizes the same range of boards as the desktop IDE.

Cloud compilation removes the need for a local toolchain. When code is built, it compiles on Arduino's servers using the same toolchains as the desktop IDE, producing equivalent binary output. This yields consistent results regardless of the developer's local configuration and enables development from devices that cannot run traditional tools, such as Chromebooks and tablets.

The platform exposes Arduino's library manager through the cloud, enabling discovery, installation, and management of the thousands of community-contributed libraries that extend Arduino capabilities. Libraries are referenced alongside project code, so that projects retain their dependencies and can be rebuilt reliably even years after initial development.

Arduino IoT Cloud Integration

The editor integrates tightly with Arduino IoT Cloud, providing a complete platform for developing connected devices. The IoT Cloud component offers device provisioning, secure connectivity, data dashboards, and webhook integrations that turn Arduino boards into components of larger IoT systems.

Device provisioning through the platform handles the complex process of establishing secure connections between hardware and cloud services. Arduino boards with Wi-Fi or cellular connectivity can be configured through a guided process that establishes encrypted communication channels, manages authentication credentials, and registers devices with the cloud platform.

The dashboard builder enables creation of web-based control interfaces without traditional web development skills. Widgets for buttons, sliders, gauges, and data displays can be arranged to create monitoring and control interfaces that update in real-time as device data changes. These dashboards provide immediate visualization capabilities for IoT projects without requiring separate front-end development.

Agent and Local Hardware Connection

Although the editor runs in the browser, programming physical hardware requires a local software agent that bridges the web environment and USB-connected boards. The Arduino Create Agent runs as a background service on Windows, macOS, or Linux, detecting connected boards and enabling upload of compiled code from the browser. (A browser sandbox cannot access serial or USB ports directly without such a helper, which is why every cloud IDE that flashes real hardware relies on a comparable local bridge.)

The agent approach balances cloud convenience with the practical reality that physical boards connect over local interfaces. Once installed, the agent operates transparently, allowing the editor to detect boards, select the appropriate port, and upload sketches as seamlessly as a desktop IDE. Board detection and identification happen automatically, simplifying the connection process for beginners.

Subscription Tiers and Limitations

Arduino Cloud operates on a freemium model with several capability tiers. The free tier provides basic functionality suitable for learning and simple projects, with caps on compilation time, storage, and the number of connected IoT devices and dashboards. Paid tiers raise these limits and add capabilities such as increased storage, more devices, longer data retention, and over-the-air updates.

Understanding tier limits helps developers choose an appropriate plan. Hobbyists and individual learners often find the free tier sufficient, while professional projects or classroom deployments may require a paid subscription to accommodate more devices, more contributors, or heavier compilation workloads. Because the specific quotas and prices change periodically, confirm current terms before committing a project to a particular tier.

Arm Mbed and Keil Studio Cloud

For more than a decade, Arm Mbed offered a professional-grade ecosystem for Arm Cortex-M microcontroller development, and its browser-based Mbed Online Compiler was one of the earliest widely used cloud IDEs for embedded work. The platform illustrates both the strengths of vendor-backed cloud tooling and the central risk of depending on it: Arm has since wound the project down. Mbed remains instructive as a case study, and several of its design ideas live on in successor and community tools.

From the Mbed Online Compiler to Keil Studio Cloud

The Mbed Online Compiler provided browser-based development across a broad range of Mbed-enabled boards from manufacturers such as STMicroelectronics, NXP, and Nordic Semiconductor. Arm retired that compiler on March 1, 2023, directing users to Keil Studio Cloud (studio.keil.arm.com) as its successor. Keil Studio Cloud is a browser-based IDE, also offered as a Visual Studio Code extension, that built on the same account system and continued to support Mbed OS projects alongside other Arm toolchains.

Mbed OS itself is Arm's open-source operating system for constrained IoT devices, providing hardware abstraction, connectivity stacks (Bluetooth Low Energy, Wi-Fi, cellular, and LoRaWAN), security services, and an RTOS scheduler. Projects could reach these features through high-level C++ APIs that abstracted low-level register access. That hardware abstraction enabled notable code portability: an application written against Mbed APIs could often run on different Mbed-enabled boards with minimal change, allowing teams to prototype on one board and deploy on another based on cost, availability, or feature requirements. This portability distinguished Mbed from strictly vendor-specific environments.

Repository, Collaboration, and Desktop Export

The Mbed environment included version control, letting projects be managed through repositories that tracked changes, supported branching, and enabled collaboration, and projects could be published to a shared component database for reuse. The community contributed thousands of libraries covering sensors, displays, and communication modules, accelerating development through tested implementations of common functionality. For workflows that required desktop tools, projects could be exported to formats for Keil MDK (uVision), IAR Embedded Workbench, and GNU Arm Embedded (GCC), allowing a team to begin in the accessible online environment and move to a desktop IDE when advanced debugging or optimization demanded it.

End of Life and Migration Paths

Arm has announced that the entire Mbed platform, including Mbed OS, reaches end of life in July 2026. At that point the Mbed website is to be archived, and it will no longer be possible to build Mbed projects in the hosted online tools. Arm has already halted active maintenance and continuous integration on the codebase and does not provide further fixes, including security updates. This is a cautionary illustration of the long-term-viability risk inherent in cloud development tools, discussed later in this guide.

Mbed OS is open source under a permissive license and remains publicly available, and a community fork, Mbed CE (Community Edition), continues development for teams that wish to keep building on the codebase. New Arm Cortex-M projects, however, are more commonly started today on vendor-supplied environments (such as STMicroelectronics' STM32Cube tools or Nordic's nRF Connect SDK based on Zephyr) or on framework-agnostic build systems like PlatformIO. The portability lessons of Mbed remain relevant when evaluating those alternatives.

Cloud Compilers and Build Services

Beyond integrated development environments, cloud-based compilation services provide the computational resources to build embedded projects without local toolchain installation. These services range from simple compile-and-download utilities to sophisticated continuous integration platforms designed for professional embedded development.

PlatformIO Cloud Build

PlatformIO, best known as a cross-platform desktop development ecosystem built atop Visual Studio Code, also runs in cloud build contexts that leverage its unified build system. It supports more than a thousand development boards across dozens of platforms and many frameworks, including Arduino, ESP-IDF, STM32Cube, Zephyr, and (historically) Mbed. Because PlatformIO drives the same command-line core everywhere, its projects compile in continuous integration runners or cloud containers without any additional local toolchain installation.

The PlatformIO ecosystem emphasizes project portability and reproducibility. Project configuration files specify exact toolchain versions, library dependencies, and build settings, ensuring consistent builds regardless of where compilation occurs. This deterministic approach suits professional workflows where build reproducibility is essential.

Continuous Integration for Embedded

General-purpose continuous integration (CI) platforms including GitHub Actions, GitLab CI, and Jenkins can be configured for embedded compilation. These platforms execute build processes in cloud containers, enabling automated compilation, testing, and deployment workflows triggered by code commits.

Implementing CI for embedded projects requires configuring containers with appropriate toolchains. Docker images containing ARM GCC, ESP-IDF, or other embedded toolchains enable CI runners to compile firmware without custom server configuration. The embedded development community has created numerous Docker images specifically for this purpose.

CI workflows for embedded projects can include static analysis, unit testing (using frameworks designed for embedded testing), and automated deployment to staging devices. While physical hardware testing remains challenging to automate, CI still provides significant value by catching compilation errors, enforcing coding standards, and maintaining build reproducibility.

Vendor-Specific Cloud Tools

Many chip vendors provide cloud-based development tools optimized for their products. Examples include STMicroelectronics' STM32CubeIDE cloud capabilities, Espressif's ESP RainMaker platform for ESP32 development, and Nordic Semiconductor's nRF Connect for Cloud. These vendor tools often provide tighter integration with specific hardware features while limiting portability to other platforms.

Vendor platforms frequently include additional cloud services beyond compilation, such as device management, over-the-air update infrastructure, and analytics dashboards. For projects committed to specific hardware platforms, these integrated offerings can significantly accelerate development compared to assembling equivalent capabilities from separate tools.

Collaborative Coding Platforms

Collaboration features distinguish many cloud development environments from desktop tools, enabling multiple developers to work on projects simultaneously, share code easily, and maintain consistent development environments across teams.

Real-Time Collaboration Features

Some cloud IDEs support real-time collaborative editing, where multiple developers can view and modify the same code simultaneously. Similar to collaborative document editing in tools like Google Docs, this capability enables pair programming, code reviews, and mentoring sessions without screen sharing or complex remote desktop setups.

Real-time collaboration proves particularly valuable for distributed teams and educational settings. Instructors can observe student work in real-time and provide guidance without physical presence. Team members across time zones can collaborate on debugging sessions, with all participants seeing code changes and their effects immediately.

Project Sharing and Access Control

Cloud platforms enable project sharing through various mechanisms, from public repositories accessible to anyone to private projects with granular access controls. Understanding sharing models helps teams balance collaboration needs with intellectual property protection.

Educational institutions often leverage sharing capabilities for curriculum delivery, providing students access to starter projects, example code, and assignment templates through platform sharing features. Students can then fork these projects, develop solutions, and share results back with instructors for evaluation.

Code Review and Annotation

Integrated code review capabilities in cloud platforms support structured feedback on code changes. Review features may include inline commenting, approval workflows, and integration with version control branching strategies. These capabilities bring software development best practices to embedded projects that have traditionally relied on less structured review processes.

Team Management Features

Enterprise-focused cloud development platforms include team management capabilities such as organization accounts, role-based access control, audit logging, and centralized billing. These features address administrative requirements of professional development organizations while maintaining the accessibility benefits of cloud-based tools.

Cloud-Based Debugging

Debugging embedded systems traditionally requires physical connections between development machines and target hardware. Cloud-based approaches to debugging address this limitation through various strategies, though with different trade-offs compared to traditional debugging workflows.

Remote Debug Connections

Some cloud platforms support remote debugging by establishing connections between cloud-hosted debug interfaces and locally-connected hardware. This approach typically requires local software (similar to the Arduino Create Agent) that provides a bridge between cloud services and physical debug probes.

Remote debugging enables scenarios where development expertise is geographically separated from hardware. An engineer can debug hardware located in a remote test facility or manufacturing line without physical presence. While network latency introduces some limitations compared to local debugging, the capability enables otherwise impossible workflows.

Logging and Telemetry-Based Debugging

Many cloud platforms emphasize logging and telemetry approaches to debugging rather than traditional breakpoint-based debugging. Devices send diagnostic information to cloud services where it can be analyzed, searched, and correlated across multiple devices.

This telemetry-based approach suits deployed IoT systems where traditional debugging is impractical. Rather than connecting debuggers to individual devices, developers analyze aggregated data from device fleets, identify patterns in failures, and push fixes through over-the-air updates. The approach requires instrumentation in firmware but enables debugging at scales impossible with traditional tools.

Simulation-Based Debugging

Some cloud platforms include simulation capabilities that enable debugging code without physical hardware. Simulated environments model processor behavior, peripheral responses, and external inputs, allowing code execution and debugging entirely in the cloud.

Simulation-based debugging provides value early in development before hardware is available, for testing edge cases difficult to create with physical hardware, and for automated testing in CI pipelines. However, simulation accuracy varies, and physical hardware testing remains essential for validating real-world behavior.

Limitations and Considerations

Cloud-based debugging generally cannot match the capabilities of traditional debug tools for low-level debugging tasks. Real-time trace, precise timing analysis, and certain hardware debugging features require local connections that cloud architectures cannot easily replicate. Developers should understand these limitations when choosing development approaches.

Remote Board Access

Remote board access platforms extend cloud development beyond compilation by providing physical access to development hardware over the Internet. These services maintain laboratories of development boards that users can access remotely, enabling hardware interaction without local equipment.

Remote Laboratory Platforms

Educational institutions and some commercial providers operate remote laboratories with arrays of development boards accessible through web interfaces. Users can upload code, interact with boards through virtual interfaces, and observe results through webcams or instrumentation data.

Remote laboratories address hardware accessibility challenges in education, allowing students to complete embedded systems coursework without purchasing expensive development kits. They also enable sharing of specialized or expensive hardware resources across larger user populations than could access physical equipment.

Remote Development Kits

Some chip vendors and development board manufacturers provide remote access to their hardware for evaluation and development purposes. These services typically target professional developers evaluating platforms for potential product adoption, providing access to hardware that might not yet be widely available or that represents significant investment to acquire.

Remote development kits usually provide time-limited access, often through reservation systems that allocate hardware to specific users for defined periods. Users can develop and test code on the remote hardware, validating functionality before committing to hardware purchases.

Hardware-in-the-Loop Testing Services

Advanced remote hardware services support hardware-in-the-loop (HIL) testing, where cloud-hosted hardware executes firmware while interacting with simulated environments. These services enable testing scenarios that would be difficult or dangerous with physical systems, such as automotive control systems or industrial automation.

HIL services typically include sophisticated instrumentation for monitoring and stimulating device interfaces, programmable power supplies for voltage and current testing, and environmental simulation capabilities. While primarily targeting professional validation workflows, these services demonstrate the expanding scope of cloud-based hardware interaction.

Security and Access Considerations

Remote hardware access raises security considerations distinct from pure software cloud services. Development code executes on shared hardware that may retain state between users. Sensitive projects may require dedicated hardware allocations or private laboratory deployments rather than shared public resources.

Web-Based Simulators

Web-based simulation environments enable circuit design, embedded programming, and system modeling entirely within browsers, without physical hardware or downloaded software. These tools range from simple educational demonstrations to sophisticated simulation platforms capable of meaningful development work.

Circuit Simulation in the Browser

Browser-based circuit simulators like Falstad (discussed in circuit simulation articles) and Tinkercad Circuits provide immediate access to circuit simulation without installation. These tools enable exploration of circuit concepts, initial design validation, and educational activities from any device with a web browser.

Tinkercad Circuits, part of Autodesk's Tinkercad platform, specifically targets Arduino simulation. Users can design circuits with virtual components, write Arduino code, and simulate execution including LED outputs, serial communication, and sensor responses. This combination supports learning embedded programming without physical hardware.

Embedded System Simulators

More sophisticated web simulators model complete embedded systems including processors, peripherals, and external components. Wokwi, for example, provides browser-based simulation of Arduino, ESP32, STM32, and Raspberry Pi Pico targets with extensive peripheral libraries covering displays, sensors, motors, and communication modules, and it can simulate Wi-Fi connectivity for ESP32 projects. It accepts firmware written in the Arduino framework, MicroPython, CircuitPython, Rust, and Zephyr, and it is available both in the browser and as a Visual Studio Code extension.

These simulators execute actual compiled firmware rather than rough approximations, so they predict behavior realistically. Pairing a simulator with an online or local compiler enables a complete write-compile-simulate loop without physical hardware. Some simulators add collaborative features that allow shared access to a running simulation for pair programming or classroom instruction.

FPGA and HDL Simulation Online

Web-based tools for FPGA development and HDL simulation bring hardware description language workflows to the browser. EDA Playground provides online access to various HDL simulators, enabling Verilog and VHDL development without expensive commercial tool licenses.

While web-based HDL simulation cannot replace full FPGA development tools for complex designs, it provides accessible entry points for learning digital design, validating small modules, and sharing examples with others. The ability to share simulation configurations through links enables education and collaboration that would be difficult with desktop tools.

Limitations of Web-Based Simulation

Browser-based simulators face inherent limitations in simulation complexity and speed. Complex circuits or long simulations may execute slowly or encounter memory limitations. Timing accuracy, particularly for systems requiring real-time behavior, may not match physical hardware.

These limitations make web simulators most appropriate for learning, concept validation, and simple projects. Production development typically requires transition to more capable tools, though web simulators can remain valuable for quick experiments and sharing examples throughout a project lifecycle.

Choosing a Cloud Development Platform

Selecting appropriate cloud development tools requires evaluating multiple factors against specific project requirements. No single platform excels at everything, and many developers use multiple tools for different purposes.

Hardware Compatibility

The most fundamental selection criterion is support for the target hardware. The Arduino Cloud Editor naturally suits Arduino-ecosystem boards, framework-agnostic systems such as PlatformIO span many Arm Cortex-M and other architectures, and vendor-specific tools serve their own products best. Confirm that a platform supports the intended hardware before investing time in learning it.

Feature Requirements

Different projects require different capabilities. Educational projects may prioritize ease of use and simulation over advanced debugging. Professional IoT products may require device management, security features, and scalability that simpler platforms cannot provide. Matching platform capabilities to project requirements avoids both overly complex tools for simple projects and inadequate tools for demanding applications.

Team and Collaboration Needs

Solo developers have different platform requirements than large teams. Collaboration features, access control, and team management capabilities matter for organizations but add unnecessary complexity for individual projects. Evaluate collaboration features against actual team workflows rather than aspirational capabilities.

Long-Term Viability

Cloud platforms depend on continued operation by their providers. Projects with long development cycles or extended product lifetimes should weigh platform stability and provider commitment. Backing by an established vendor reduces, but does not eliminate, this risk: Arm's decision to retire the long-running Mbed platform in July 2026 shows that even a major vendor will sunset a cloud tool when its strategy shifts. Favoring open-source or community-maintained components, where a project can outlive its original sponsor, is one way to limit exposure.

Export capabilities provide insurance against platform changes. Platforms that enable exporting to standard formats or desktop tools provide exit paths if cloud services become unavailable or unsuitable. Projects depending heavily on platform-specific features should assess the implications of potential platform migration.

Cost Considerations

Cloud platform costs vary from free tiers suitable for learning and small projects to substantial subscription fees for professional features. Understanding pricing models, including how costs scale with usage or team size, helps avoid budget surprises. Free tiers often provide sufficient capability for evaluation before committing to paid subscriptions.

Security and Intellectual Property Considerations

Moving development to cloud platforms introduces security and intellectual property considerations that differ from traditional local development. Understanding these factors helps organizations make informed decisions about cloud platform adoption.

Code Storage and Access

Code stored on cloud platforms resides on third-party servers subject to the platform provider's security practices and legal jurisdiction. While reputable platforms implement strong security measures, organizations with strict intellectual property requirements should evaluate platform security certifications, data handling policies, and contractual protections.

Access control configuration determines who can view and modify project code. Misconfigured permissions can inadvertently expose proprietary code. Organizations should establish clear policies for platform configuration and regularly audit access settings.

Compiled Binary Handling

Cloud compilation means that source code is processed on remote servers, and compiled binaries are transmitted over networks. For projects with strict security requirements, this processing model may raise concerns about code exposure or binary integrity. Some organizations require local compilation for production firmware even while using cloud platforms for development.

Connectivity Dependencies

Cloud-based development requires Internet connectivity. Projects in locations with unreliable connectivity or high-security environments without external network access cannot rely solely on cloud platforms. Hybrid approaches using cloud platforms when available with local tool fallbacks address some connectivity concerns.

Terms of Service Implications

Platform terms of service define the legal relationship between users and platform providers. Terms may include provisions regarding code ownership, usage restrictions, and data handling that affect project decisions. Legal review of terms is advisable for commercial projects or organizations with specific compliance requirements.

Future Directions

Cloud-based development for electronics and embedded systems continues evolving rapidly, with emerging capabilities expanding what is possible without local development infrastructure.

AI-Assisted Development

Integration of AI coding assistants into cloud IDEs is expanding to embedded development. These tools can suggest code completions, explain existing code, identify potential bugs, and even generate code from natural language descriptions. While AI assistance requires careful validation in safety-critical embedded applications, it promises to accelerate development for appropriate use cases.

Enhanced Simulation Capabilities

Cloud simulation platforms continue improving in accuracy, speed, and coverage. Increasing computational resources enable more sophisticated simulations, while expanded component libraries cover more hardware combinations. The gap between simulated and physical development continues narrowing for many application types.

Integrated DevOps for Embedded

DevOps practices established in software development are increasingly adapted for embedded systems, with cloud platforms providing integrated workflows spanning development, testing, deployment, and monitoring. These integrated approaches bring the efficiency benefits of modern software practices to embedded development.

Edge-Cloud Hybrid Development

As edge computing grows in importance, development tools increasingly support hybrid architectures where code runs partially on edge devices and partially in the cloud. Cloud development platforms are evolving to support these distributed architectures, enabling development of systems that span edge and cloud components.

Conclusion

Cloud-based IDEs and development platforms have matured into capable tools serving needs from education through professional product development. Accessible entry points such as the Arduino Cloud Editor and browser-based simulators scale toward sophisticated applications, while specialized services address remote hardware access, advanced simulation, and team collaboration. The retirement of Arm Mbed is a reminder that individual platforms come and go even as the overall category grows.

The advantages of cloud development—accessibility from any device, elimination of local environment configuration, real-time collaboration, and on-demand computational resources for compilation and simulation—make these platforms compelling for many use cases. However, limits on low-level debugging, security and intellectual-property considerations, and the requirement for reliable connectivity mean that cloud platforms complement rather than fully replace traditional tools in many professional workflows.

Successful adoption of cloud development platforms requires matching platform capabilities to project requirements, understanding the security and intellectual property implications, and maintaining flexibility to use appropriate tools as projects evolve. As cloud platforms continue improving and expanding their capabilities, they will play an increasingly central role in electronics and embedded systems development workflows.

Related Topics

• IoT Cloud Platforms - Backend services for provisioning, connecting, and managing fleets of devices
• CI/CD for Hardware - Automating cloud builds, testing, and deployment of firmware
• Remote Hardware Access - Reaching physical boards and instruments over the network
• Documentation and Knowledge Platforms - Cloud tools for capturing and sharing project knowledge
• Simulation and Virtual Prototyping - Modeling circuits and systems before committing to hardware
• Software Development Tools - Editors, toolchains, and debuggers for embedded software