About The Embedded Edit

The Embedded Edit is a media publication covering the technologies, practices, and trends shaping embedded systems and critical infrastructure. We publish technically grounded, editorial content from practitioners, researchers, and industry voices who are building, securing, and maintaining the systems that underpin modern infrastructure.

Topics & Themes

We are interested in original submissions across the embedded systems lifecycle, including:

Embedded Systems & Firmware Engineering: Development practices across the full embedded lifecycle, including firmware design, tooling, testing, deployment at scale, in-field updates, diagnostics, maintenance, and long-term support of constrained or legacy systems.Development practices, tooling, testing, deployment, and maintenance
System Architecture & Platform Design: Architectural and platform decisions spanning hardware and software, including performance, power, reliability, security tradeoffs, silicon constraints, platform longevity, manufacturing considerations, and system integration.Design decisions that affect performance, reliability, safety, and longevity
Reliability, Safety & System Resilience: Engineering practices that keep embedded and infrastructure systems operating under real-world conditions, including fault tolerance, verification and validation, certification, incident response, failure analysis, and post-incident lessons learned. What it takes to keep critical systems operating in real-world conditions
Software Supply Chains & Dependencies: Managing software dependencies in embedded and long-lived systems, including open source use, third-party components, SBOMs, update constraints, end-of-life risk, and supply chain resilience.Open source, third-party components, SBOMs, and long-lived systems
Security & Vulnerability Insights: Practical analysis of embedded security risks, vulnerabilities, and failures, including threat modeling, secure design tradeoffs, responsible disclosure, remediation challenges, and lessons learned from real-world incidents.Practical analysis of embedded risks, failures, and lessons learned
Critical Infrastructure & Operational Technology (OT): Embedded systems in energy, industrial, transportation, and related sectors, including legacy platforms, modernization efforts, interoperability challenges, regulatory environments, and operational constraints unique to critical infrastructure.
Policy, Standards & Industry Direction: Regulation, certification standards, industry bodies, and global trends shaping embedded systems development, including regional regulatory differences, compliance requirements, and geopolitical factors affecting supply chains and system design.Regulation, standards bodies, and global trends shaping development
The Future of Embedded Systems: Emerging technologies, evolving engineering practices, workforce and skills challenges, organizational models, and long-term trends influencing how embedded and infrastructure systems are designed, built, and sustained.Emerging technologies, workforce shifts, and what’s coming next

What We’re Looking For

We publish:

Technical deep dives based on hands-on experience
Thoughtful analysis or informed opinion pieces
Interviews or Q&A with experienced practitioners
Long-form features synthesizing expert perspectives

Strong submissions are:

Technically accurate and clearly written
Insight-driven and grounded in experience or evidence
Editorial in tone (not promotional)
Useful to practitioners, technical leaders, and decision-makers working across embedded systems and critical infrastructure

Submission Guidelines

Length: Typically 1,000–2,000 words (flexible for strong ideas)
Originality: Submissions must be original and not previously published
Tone: Educational and editorial; no sales language or product promotion
Attribution: Cite sources where appropriate; first-hand experience encouraged
Visuals (optional): Diagrams, charts, and videos are welcome if they support the content
Author Bio: 2–3 sentences with optional link(s)

We do not accept:

Marketing or vendor-led content
Product announcements or press releases
Articles without a clear point of view or practical insight

All accepted pieces are edited for clarity, length, and editorial consistency while preserving the author’s voice and technical intent.

How to Submit

We prefer either:

A short pitch (topic, why it matters now, and your perspective), or
A complete draft ready for editorial review

Submit by email to editor@embeddededit.com.

‍

We aim to respond within 2–3 weeks. If you don’t hear back within that timeframe, the submission was likely not selected.

‍

Questions & Contact

For questions about submissions, editorial fit, or contributor guidelines not addressed above, please contact the editorial team at editor@embeddededit.com. We are unable to provide feedback on every inquiry, but we review all messages and appreciate thoughtful outreach.

Rights & Republishing

Authors retain copyright to their work. By submitting and publishing an article, authors grant the publication a non-exclusive, perpetual right to edit, publish, distribute, and promote the content in all current and future formats, including excerpts for marketing or syndication purposes.

Unless otherwise agreed in writing, published articles may not be republished elsewhere for 30 days following publication. After that period, authors may republish their work provided the original publication is clearly credited and linked.

The publication reserves the right to make editorial edits for clarity, length, and consistency, while preserving the author’s voice and technical intent.

‍

Editorial Independence

The Embedded Edit is operated by RunSafe Security, but all editorial decisions are made independently. Published content reflects the views and expertise of the individual authors and editors, not the positions or products of RunSafe. We do not publish sponsored or promotional content, and contributor acceptance is based solely on editorial merit, relevance, and quality.

Accuracy, Liability, and Claims

Authors are responsible for the accuracy of all technical statements, factual assertions, and claims made in their submissions. Claims regarding security vulnerabilities, system failures, incidents, or performance characteristics must be supported by firsthand experience, verifiable evidence, or credible sources.

‍

Submissions must not include confidential, proprietary, export-restricted, or otherwise non-public information, and must comply with applicable laws and professional obligations. The publication reserves the right to request clarification, sources, or revisions to ensure accuracy and editorial integrity.

Contributor Guidelines