Autonomy Logic

Open-source and cloud-native software for programmable logic controllers (PLCs) for industrial automation.

Cover Block

Open sources

Field	Detail
Name	Autonomy Logic
Tagline	Open-source and cloud-native software for programmable logic controllers (PLCs) for industrial automation [Autonomy Logic]
Headquarters	Longwood, Florida [LinkedIn]
Founded	2023 [LinkedIn]
Stage	Seed [PitchBook]
Business model	Open source / Commercial
Industry	Deeptech
Technology type	Software (Non-AI)
Geography	Global / Remote-First
Growth profile	Venture Scale
Founding team	Solo Founder
Funding label	Seed
Total disclosed	Approximately $300,000 [PitchBook]

What an Investor Needs First

PUBLIC Autonomy Logic builds open-source and cloud-native software for programmable logic controllers, a part of industrial automation that still suffers from vendor lock-in, long hardware cycles, and fragmented tooling, which is why the company merits attention despite thin public disclosure [Autonomy Logic] [LinkedIn] [GitHub]. Founded in 2023 in Longwood, Florida, the company appears to have been created to give the long-running OpenPLC project a dedicated commercial home, while preserving an open-source distribution model that can widen adoption before monetization shifts to managed cloud and enterprise support [LinkedIn] [UAH | Engineering | - | ECE Alumni Spotlight - Thiago Alves] [Autonomy Logic].

The product stack is legible from public repositories and documentation: OpenPLC Editor for writing PLC logic, OpenPLC Runtime for executing that logic, and Autonomy Edge for browser-based development and fleet management of virtual PLCs, with versioned projects and deployment workflows positioned as the operational layer on top of the open-source core [GitHub] [Autonomy Edge] [Autonomy Logic]. That architecture is the most interesting part of the bet, because the differentiation seems to rest less on a proprietary controller and more on making PLC software portable across hardware and manageable through modern software practices such as version control and cloud orchestration [Autonomy Logic] [Autonomy Edge] [OpenPLC: An open source alternative to automation | Request PDF].

The public record ties the company closely to founder and CEO Thiago Alves, PhD, whose background spans security research and direct technical work on OpenPLC, including visible contribution activity in the editor and runtime repositories [LinkedIn] [GitHub] [OpenPLC Forum]. His prior role as Head of Security Research at Mosyle and earlier OpenPLC-related academic and competition credentials are relevant signals for technical credibility, although the current public record says less about commercial scaling experience than about product authorship [LinkedIn] [DEF CON® 26 Hacking Conference Speakers].

Funding is only lightly documented in public sources.

Over the next 12 to 18 months, the key public watchpoints are whether company-reported usage converts into identifiable enterprise adoption, whether Autonomy Edge becomes the primary monetization surface, and whether the company can translate developer and academic reach into production use cases that fit the stated limits of non-safety-critical deployments [Autonomy Logic] [Open Source Industrial Automation: Certification and Safety - Industrial Monitor Direct]. The company-reported scale metrics, including 1M+ downloads, 26K+ cloud users, and presence in 150+ countries, are notable but still need independent corroboration before they can carry much weight in an underwriting case [Autonomy Logic].

Reasoned from indirect evidence -- This section combines company materials, LinkedIn, GitHub, one academic profile, one university profile, and PitchBook, with several material traction claims still company-reported and only partial independent corroboration for team and funding details.

Taxonomy Snapshot

Axis	Value
Stage	Seed
Business Model	Open Source / Commercial
Industry / Vertical	Deeptech
Technology Type	Software (Non-AI)
Geography	Global / Remote-First
Growth Profile	Venture Scale
Founding Team	Solo Founder
Funding	Seed, total disclosed approximately $300,000 [PitchBook]

Inside the Company

Open sources Autonomy Logic presents as a young industrial automation software company built around a project that long predates the corporation itself. The company is headquartered in Longwood, Florida, and its public LinkedIn presence lists 2023 as the founding year, while the company site describes the business as the team behind OpenPLC, an open industrial automation stack for programming IEC 61131-3 logic, running it on varied hardware, and managing virtual PLCs through Autonomy Edge [Autonomy Logic] [LinkedIn].

The founding narrative that is publicly attributable is narrow but coherent. A University of Alabama in Huntsville alumni profile states that Thiago Alves founded Autonomy in 2023 to give OpenPLC a dedicated team and focus, which fits the current company positioning around commercializing and extending the open-source PLC environment into cloud-based management and deployment tools [University of Alabama in Huntsville] [Autonomy Logic]. Public GitHub activity also shows the Autonomy Logic organization maintaining the OpenPLC Editor and Runtime repositories, which is a useful milestone because it ties the company identity to active stewardship of the software stack rather than to a landing page alone [GitHub].

The clearest public milestone sequence is therefore: OpenPLC existed as an open-source project before the company, Autonomy was formed in 2023 around that base, and the business now markets a broader stack that includes OpenPLC Editor, OpenPLC Runtime, and Autonomy Edge as its commercial control plane for cloud-managed virtual PLCs [University of Alabama in Huntsville] [Autonomy Logic] [GitHub]. Public evidence in the source set does not establish a legal entity filing name or a dated sequence of financing and customer milestones, so the current read has to stay close to product lineage and corporate self-description [Autonomy Logic].

Partially corroborated -- Relies primarily on company website materials, with partial corroboration from LinkedIn, GitHub, and the University of Alabama in Huntsville profile.

Under the Hood

MIXED The product story is legible even if the operating data is thin. Autonomy Logic presents itself as the company behind OpenPLC, with a stack that spans OpenPLC Editor, OpenPLC Runtime, and Autonomy Edge, covering authoring, execution, and cloud management for programmable logic controllers [LinkedIn] [GitHub] [Autonomy Logic]. The company describes the stack as open-source and hardware-agnostic, with support that runs from microcontrollers to industrial servers, while third-party technical coverage similarly characterizes OpenPLC as an open-source environment for deploying industrial automation code across hardware from different vendors [Autonomy Logic] [OpenPLC: An open source alternative to automation | Request PDF].

The public materials are more specific on workflow than on underlying architecture. Autonomy Edge is described in product documentation as a cloud platform where users write IEC 61131-3 PLC programs in a browser-based IDE, store them as git-versioned projects, and deploy them to virtual PLCs, with additional documentation referencing organization management and usage of shared Autonomy Compute Units for AI Engineer jobs [Autonomy Edge] [Autonomy Edge, Retrieved 2026]. The homepage also advertises version control, collaboration, and CoPilot support for ST, Python, and C++, while external guides indicate OpenPLC Editor is distributed under GPL-3.0 and OpenPLC Runtime v4 under MIT, although another industry source describes the runtime license differently for commercial deployment, which suggests investors should treat licensing scope as a diligence item rather than a settled public fact [Autonomy Logic] [OpenPLC guide: Arduino, ESP32 and industrial PLCs] [Open Source Industrial Automation: Certification and Safety - Industrial Monitor Direct].

The technical wedge appears to be openness first, then enterprise overlays. Autonomy says it offers enterprise support, SLAs, compliance features, fleet management, and five Autonomy Edge plans from Community through Enterprise, but those claims remain company-supplied and are not corroborated by named customer references or independent product reviews in the materials reviewed here [Autonomy Logic] [Autonomy Edge]. A second constraint is safety scope: external commentary says OpenPLC is suitable for education, lab automation, retrofit, and lower-risk industrial use cases, but is not certified to IEC 61508 for SIL-rated deployments without independent assessment, which narrows where the stack can credibly land inside regulated control environments [Open Source Industrial Automation: Certification and Safety - Industrial Monitor Direct].

Claim stands unchecked -- Core product surfaces are corroborated by GitHub, LinkedIn, and company documentation, but many feature, licensing, and deployment claims in this section remain company-supplied or partially conflicting in public sources.

Market Research

Open sources The market matters now because industrial control software is starting to separate from proprietary hardware, and Autonomy Logic is positioning itself at that fault line with an open-source PLC stack and a cloud control layer [Autonomy Logic] [Autonomy Edge].

Public market sizing for Autonomy Logic's exact category, open-source and cloud-native PLC software, is not established in the cited record, so any sizing discussion has to stay narrow and analogous rather than precise. The available evidence does support the underlying demand domain: programmable logic control remains a core layer of industrial automation, and OpenPLC is described in third-party technical coverage as an open-source alternative for deploying industrial automation code across hardware from different vendors [Request PDF] [Industrial Monitor Direct]. That places the company at the intersection of several existing spend pools, industrial automation software, edge orchestration, engineering tooling, and industrial training and research, even if the public sources here do not permit a clean TAM or SAM calculation.

Demand signals in the record point less to immediate enterprise standardization and more to a broad top-of-funnel user base. The company reports more than 1 million OpenPLC Editor and Runtime downloads, more than 26,000 Autonomy Edge cloud users, deployments in more than 150 countries, and more than 500 academic citations [Autonomy Logic]. Those are company-reported figures and should be read as adoption indicators rather than audited commercial metrics, but they fit the product's apparent wedge in education, research, prototyping, retrofit environments, and lower-risk industrial use cases where engineers value hardware flexibility and software portability [Autonomy Logic] [Industrial Monitor Direct].

The adjacent markets are easier to define than the core market itself. OpenPLC is presented as suitable for lab automation, education, retrofit projects, low-risk process control, and IIoT prototyping, while third-party commentary states that it is not certified to IEC 61508 and should not be used in SIL-rated applications without independent assessment [Industrial Monitor Direct]. That distinction matters, because it suggests the near-term addressable market is likely broader in developer adoption than in safety-critical production control, at least until certification, validation, or integrator trust closes part of that gap.

Macro and regulatory forces cut both ways. On the positive side, the appeal of vendor-independent control logic, browser-based collaboration, and versioned deployment maps to long-standing industrial concerns around lifecycle cost, workforce constraints, and hardware lock-in [Autonomy Logic] [Autonomy Edge]. On the limiting side, industrial buyers still operate under conservative qualification standards, and the absence of built-in safety certification in the public record narrows where open PLC software can be deployed without extra engineering review or external assurance [Industrial Monitor Direct].

Market angle	Public evidence	What it suggests
Industrial automation software	OpenPLC is described as an open-source alternative for industrial automation across hardware vendors [Request PDF]	The company is selling into a real control-software category, even if its exact segment is still emerging.
Education and research	The company reports 500+ academic citations, and third-party sources describe OpenPLC as suitable for education and lab automation [Autonomy Logic] [Industrial Monitor Direct]	Universities and training environments appear to be a credible adoption wedge.
IIoT and edge control	Third-party sources cite OpenPLC for IIoT prototyping, while Autonomy Edge adds cloud orchestration of virtual PLCs [Industrial Monitor Direct] [Autonomy Edge]	The commercial upside may sit in cloud management and fleet operations rather than the open-source runtime alone.
Safety-constrained automation	OpenPLC is described as not certified to IEC 61508 for SIL-rated use without independent assessment [Industrial Monitor Direct]	Safety-critical process control remains a constrained segment under the current public evidence.

The pattern here is a market that is plausible and structurally interesting, but still best framed through adjacent categories and workload substitution rather than a verified standalone TAM. For investors, the useful question is not how large "open-source PLC software" is on paper, but whether developer adoption in education, prototyping, and low-risk industrial deployments can convert into paid orchestration, support, and enterprise controls over time.

Partially corroborated -- This section relies on company materials and a limited set of third-party technical sources. No named third-party market report or independently verified TAM study was available in the cited record.

Competition and Substitutes

Competitive Map

MIXED The company is positioned less against a single named startup rival than against three established alternatives: proprietary PLC software from incumbent automation vendors, open-source PLC tooling maintained outside a venture-backed wrapper, and adjacent industrial software that manages edge devices without replacing the control layer itself [Autonomy Logic] [GitHub] [LinkedIn].

The first segment is the incumbent PLC stack, where buyers typically use vendor-tied environments and hardware-specific runtimes rather than an open, hardware-agnostic control layer [Autonomy Logic] [OpenPLC: An open source alternative to automation | Request PDF]. Public materials do not name Schneider Electric, Siemens, Rockwell Automation, or Beckhoff directly, so the comparison here has to stay at the category level rather than attach unverified feature claims to specific vendors. What is clear from the product description is that Autonomy Logic is trying to shift the basis of competition from bundled hardware plus software toward portable IEC 61131-3 logic, browser-based development, and cloud orchestration of virtual PLCs [Autonomy Edge] [Autonomy Logic].

The second segment is the open-source and education-oriented control ecosystem around OpenPLC itself, where the company has a more tangible claim because it is publicly tied to the project on GitHub and LinkedIn [GitHub] [LinkedIn]. In that lane, the challenge is not only commercial competitors, but the fact that open-source users can remain free users indefinitely, fork the codebase, or self-support if their use case is narrow enough. The third segment is adjacent edge orchestration and industrial software that can coexist with PLCs rather than replace them, which limits how much of an automation budget a PLC software vendor can realistically capture unless it becomes part of a broader controls workflow [Autonomy Edge] [Autonomy Logic].

Where the Edge Exists Today

MIXED The clearest edge visible in public evidence is distribution through an existing open-source project rather than through a conventional enterprise sales motion [Autonomy Logic] [GitHub]. The company reports 1M+ OpenPLC Editor and Runtime downloads, 26K+ Autonomy Edge cloud users, deployments in 150+ countries, and 500+ academic citations, while Thiago Alves' Google Scholar profile shows 536 citations [Autonomy Logic] [Thiago Alves - Google Acadêmico]. Those figures are partly company-reported and should be treated cautiously, but they still point to a real pattern: awareness appears to begin with developer and academic adoption, then extend toward commercial deployment.

That matters because industrial controls software is usually hard to seed from zero. A founder who is publicly visible in the codebase, the forum, and educational content has an easier path to trust among engineers than a new commercial entrant without community roots [GitHub] [OpenPLC Forum] [The University of Alabama in Huntsville]. The durability of that edge is mixed. Community credibility and installed familiarity can persist, but download-led distribution is perishable if conversion to paid support, compliance, and fleet management does not become strong enough to finance ongoing product development [Autonomy Logic].

Where the Exposure Is Highest

MIXED The main exposure is that the company's strongest public asset, OpenPLC's openness and portability, does not automatically solve the hardest part of industrial buying: certified reliability, procurement comfort, and integration into existing vendor estates [Autonomy Logic] [Open Source Industrial Automation: Certification and Safety - Industrial Monitor Direct]. One source states that OpenPLC is not certified to IEC 61508 and should not be used in SIL-rated applications without independent assessment, which narrows the set of workloads where an open control stack can displace incumbent systems outright [Open Source Industrial Automation: Certification and Safety - Industrial Monitor Direct].

That limitation gives incumbent automation vendors a specific advantage even without naming them one by one. They already own plant-floor relationships, certified product lines, channel partners, and long replacement cycles. Autonomy Logic is also exposed to the possibility that some users value OpenPLC as free infrastructure but do not need Autonomy Edge's commercial layer, especially if their deployment is small, educational, or confined to low-risk retrofit work [Autonomy Edge] [Open Source Industrial Automation: Certification and Safety - Industrial Monitor Direct]. In other words, the company does not yet appear to own a protected channel in the way a large automation OEM or systems integrator does.

Plausible 18-Month Scenario

MIXED The most plausible 18-month scenario is a split market rather than a winner-take-all outcome. Autonomy Logic could strengthen its position if open-source PLC adoption continues to move from education and prototyping into low-risk industrial production, and if Autonomy Edge becomes the default management plane for those deployments through browser-based development, version control, and fleet operations [Autonomy Edge] [Autonomy Logic]. In that case, OpenPLC itself is the likely winner if portability and cloud management become more important than tight coupling to a single hardware vendor.

The likely loser under the opposite condition is not a named startup in the record, but the commercial layer around OpenPLC. If buyers keep using the open-source runtime for labs, teaching, and selective retrofits while reserving production-critical automation for certified incumbent stacks, then the free project can remain relevant while the monetization surface stays narrow [Open Source Industrial Automation: Certification and Safety - Industrial Monitor Direct] [Autonomy Logic]. That is the competitive tension to watch: strong top-of-funnel technical adoption is visible, but the public record is still thin on named customers, channels, or proof that the company can convert community mindshare into a durable enterprise position [Autonomy Logic] [LinkedIn].

Partially corroborated -- This section relies on company materials, GitHub, LinkedIn, and one independent industry source.

Opportunity

Upside Case

PUBLIC The prize here is not a niche developer tool outcome, but a credible shot at becoming the default software layer for a meaningful slice of modern industrial control, if open-source PLC tooling continues to move from education and prototyping into commercial deployment workflows.

The clearest upside path is straightforward. Autonomy Logic sits on top of OpenPLC, a project the company describes as an open industrial automation stack for programming IEC 61131-3 logic, running it on diverse hardware, and managing virtual PLCs through Autonomy Edge [Autonomy Logic]. Public evidence supports the existence of three linked surfaces, OpenPLC Editor, OpenPLC Runtime, and Autonomy Edge, across the company website, GitHub, and product documentation [GitHub] [Autonomy Edge]. That matters because the larger outcome is not simply selling support around an open-source project. It is owning the control plane that links development, deployment, fleet management, and browser-based collaboration for PLC software. The company-reported adoption figures, 1M+ downloads, 26K+ cloud users, and deployments in 150+ countries, are not independently audited, but they do indicate early distribution around a real developer artifact rather than a concept deck [Autonomy Logic].

What makes that outcome reachable, rather than purely aspirational, is the product shape and the founder-project fit. OpenPLC already appears to be used across hardware types, from microcontrollers to industrial servers, and external sources describe it as suitable for education, retrofit, low-risk process control, and IIoT prototyping, while also noting limits around safety certification [Autonomy Logic] [Open Source Industrial Automation: Certification and Safety - Industrial Monitor Direct]. That is a narrow but useful starting wedge. Thiago Alves appears both as founder and as a hands-on contributor in the public repositories, and the University of Alabama in Huntsville profile states he founded Autonomy in 2023 to give OpenPLC a dedicated team and focus [LinkedIn] [GitHub] [UAH | Engineering | - | ECE Alumni Spotlight - Thiago Alves | The University of Alabama in Huntsville]. In practical terms, the company seems to be commercializing an existing open technical community, not trying to invent one from zero.

Scenario	What happens	Catalyst	Why it's plausible
Open-source to enterprise control plane	OpenPLC remains the developer entry point, while Autonomy Edge becomes the paid system for versioning, collaboration, deployment, and fleet operations across industrial estates	More teams need browser-based IEC 61131-3 development, Git-style workflows, and centralized deployment for virtual PLCs [Autonomy Edge] [Autonomy Logic]	The public stack already spans IDE, runtime, and cloud orchestration, which is the minimum architecture for a control-plane business rather than a point tool [GitHub] [Autonomy Edge]
Education and prototyping pipeline into commercial standard	Universities, labs, and machine builders adopt OpenPLC early, then carry it into retrofit and low-risk production environments where incumbent tooling is costly or closed [Autonomy Logic] [OpenPLC: An open source alternative to automation	Request PDF]	A larger installed base of trained users and reference deployments makes OpenPLC a familiar default in non-safety use cases [Autonomy Logic]
Embedded software layer for industrial-device vendors	OEMs and device makers ship hardware that is easier to program and manage because OpenPLC Runtime and Autonomy Edge sit underneath	Hardware vendors increasingly want software-defined controls without maintaining a full proprietary PLC stack [Autonomy Logic]	The company explicitly targets industrial-device vendors and positions OpenPLC as hardware-agnostic, which fits an embedded distribution model if commercial packaging matures [Autonomy Logic]

The compounding mechanism, if it forms, is a classic open-core industrial software flywheel. Free runtime and editor access widen top-of-funnel adoption, especially in education, experimentation, and low-risk industrial settings [OpenPLC: An open source alternative to automation | Request PDF] [Open Source Industrial Automation: Certification and Safety - Industrial Monitor Direct]. Once teams have logic written in OpenPLC workflows, the paid value can move uphill into cloud collaboration, permissions, deployment history, fleet management, enterprise support, and compliance features, all of which the company says it offers or is building into Autonomy Edge and its commercial layers [Autonomy Logic] [Autonomy Edge]. The more projects, libraries, and deployment estates that sit inside that workflow, the higher the switching cost becomes. There is also a softer distribution moat in training and familiarity: if engineers first learn PLC development on OpenPLC, the commercial product has a natural path into their later procurement decisions.

The size of the win is harder to quantify from the current public record because no credible market-size study or direct public comparable is included in the sourced material. Still, the strategic endpoint is legible. If Autonomy Logic became a standard software layer for non-safety industrial controls across education, prototyping, retrofit, and selected production environments, it would look less like a services firm and more like infrastructure software with an open-source distribution edge. That could support a venture-scale outcome, particularly because industrial controls budgets have historically been anchored in proprietary vendor ecosystems, and an accepted software-defined alternative can redirect where value accrues [Autonomy Logic] [OpenPLC: An open source alternative to automation | Request PDF]. Any valuation framing beyond that would be speculative on the present evidence, so the upside is best described qualitatively: a meaningful control-plane company for programmable industrial automation, if the company can convert project adoption into repeatable commercial accounts and do so without crossing into regulated safety claims it cannot yet support [Open Source Industrial Automation: Certification and Safety - Industrial Monitor Direct].

Partially corroborated -- Relies on company website, product docs, GitHub, LinkedIn, and one external industry source; upside scenarios are analytical inferences built on partially corroborated public evidence.

Sources