Some will build an unfair advantage. Others will find themselves on the wrong side of an expanding capability gap. OpenIndustrial exists to make that advantage accessible: adaptive, future proof, and completely yours to own. https://t.co/ZzcTS1OrK8

OpenIndustrial Unveils AI-Native Capabilities for Industrial Automation

Instead of abstracting away complexity, we help teams own it — composing cloud-native infrastructure, real-time data, and AI agents into systems that don’t just run. They evolve. @AutomateShow #Automate25 https://t.co/mE0sCrgucO

Introducing OpenIndustrial, a cloud-native industrial integration hub and AI-native execution engine. - Composable Integration Hub - Azi AI Co-Architect - Reflex Memory - Forkable Runtime Read the full announcement: https://t.co/cNVXa963kK

The power of the iceberg concept lies in its ability to balance simplicity and complexity. By offering a simple and easy-to-use starting point, Fathym creates an entry point that sets the tone for ongoing development. https://t.co/rHzlIpDMvN #DevOps #Cloud #App #software

Define and Standardize: How automation allows traditional and citizen developers to work in concert https://t.co/SPUBcNJjgp #automation #DevOps #Cloud #Azure #lowcode #application

In this way, LCUs are a bridge between “high code” development and the emerging worlds of low code and even no code in a way that doesn’t compromise good development practice. #Lowcode #Container #API #Frontend #CLI #Software

Fathym provides a pathway for engineers to craft custom LowCodeUnits that can be used across their organisation or shared with customers and partners.

An LCU can be a package of frontends and proxies, deployable as a set of routes on the same domain. Or it could be a deployable instance of a content or asset management system, self-hosted with a few CLI commands on Azure.

LCUs can be anything across the full stack, spanning frontend and backend. An LCU can be a packaged Infrastructure as Code template, an automated container deployment, an API reverse proxy, a third-party API integration, a UI component, micro frontend or React starter template.

LCUs are composable and can be consumed by existing solutions or weaved together to create new, cohesive solutions. In this way, organisations can efficiently craft custom, open source, and SaaS/third-party solutions. What are some examples?

These flexible units can hold anything ranging from automated containers to APIs and frontends. LCUs are not just configurations like other "low code" offerings. They’re real code – in components.

Fathym facilitates this through what we call LowCodeUnits (LCUs) – deployable and reusable software components and the most basic building blocks of the Fathym world.

At Fathym, we believe the key for successful adoption of #lowcode is through the lens of "high code" best practice.

The power of the “iceberg concept” in software development https://t.co/rHzlIpDeGf #iceberg #devops #cloud #composable #PaaS #IaaS #azure

Unlocking the true power of composable low-code application development for the enterprise https://t.co/haO3sfKP3v #lowcode #composable #devops #cloud #application

The goal of the iceberg concept in software development is to provide a simple and easy-to-use starting point, while still offering the option for more complex and customized features below the surface: https://t.co/rHzlIpDeGf #softwaredevelopment #devops

At Fathym, we believe the key for successful adoption of low code is through the lens of "high code" best practice. Fathym facilitates this through what we call LowCodeUnits (LCUs). Find out more in our latest blog: https://t.co/haO3sfKP3v

https://t.co/qkJSkDSSY8

#FortCollins is expecting 4-12" of snow tonight and into Wednesday morning. #Poudre Schools are closed already for a snow day tomorrow. We don't suggest driving when it's snowing that hard. But, Habistack can help you find safer, less dangerous routes: