Blog
From the field
What we're learning building AI systems for companies that make real things.
NetSuite Alternatives for Manufacturers Who Want to Own Their Software
A working comparison of NetSuite alternatives for small and mid-market manufacturers. Cost, lock-in, on-prem options, and the path most lists miss.
Read →Can I Build My Own ERP? What the Answer Looks Like in 2026
The honest answer for a mid-market manufacturer: cost, timeline, staffing, when a custom ERP wins, when it fails, and what the hybrid path delivers.
Read →Manufacturing Data Sovereignty: What It Actually Means, and Why NetSuite Isn't It
For manufacturers, data sovereignty means 4 things: residency, ownership, portability, extensibility. Big ERP fails all four. Here is what passing looks like.
Read →RAG for Manufacturing: A Knowledge Base Your Shop Floor Can Actually Use
RAG for manufacturers is not another generic chatbot. What to ingest, what to skip, how to deploy it on your infrastructure, and how to trust the answers.
Read →Quality Substrates for AS9100 Shops: Turn Audit Prep from Weeks Into Hours
An AS9100 quality manager spends 3 weeks per audit hunting evidence across SharePoint, the QMS, and email. A quality substrate cuts that to hours.
Read →The 6-Question Context Engine Audit (And What Your Score Means)
Six questions that tell you whether your AI system has a real context engine or a pile of half-built parts. Score in 15 minutes. What each band means.
Read →Storage for AI vs Object Storage (S3, R2, GCS): The Comparison Nobody Else Writes
S3, R2, and GCS hold bytes. They do not know what is in them. A storage for AI layer holds the record an agent reads from. When to use each, and both.
Read →Why Manufacturing AI Projects Stall (and the State Layer That Lets Them Ship)
CNC shops and fabricators carry deep state in BOMs, routings, and AS9100 evidence. Stateless LLMs cannot reason against it. The fix is a substrate.
Read →Your AI Demo Worked. Your AI Project Failed. Here's Why.
Frontier LLMs are stateless. Every conversation starts cold. The gap between a demo and a shipped project is the state layer your business does not have.
Read →Every AI Team Builds a Context Engine. Most Don't Realize It.
Every team building with AI rebuilds the same 6 components: connectors, retrieval, storage, review, protocol, drift detection. That is a context engine.
Read →Storage for AI vs Vector Databases: When to Use Which (and How They Work Together)
A storage for AI layer holds the canonical record. A vector database indexes over it. Different problems, different layers. Most systems need both.
Read →The 5-Question Substrate Audit (And What Your Score Means)
Five questions that tell you whether your business has an AI substrate. Score in 15 minutes. What each band means and what to fix first.
Read →Vector DBs Aren't Storage. They're Indexes.
A vector database is an index. The storage sits somewhere else, usually a Postgres table nobody talks about. The missing category is storage for AI.
Read →AI Substrate Glossary: Definitions for the Terms KoldOps Uses
Definitions for AI substrate, storage for AI, context engineering, decision-state, code-state, drift detection, and substrate audit. Refreshed quarterly.
Read →Decision-State, Airlocked to Code-State: Defining the AI Substrate
The AI substrate isn't compute. It's the discipline that fuses business decisions to your codebase with the same git, review, and audit you use for code.
Read →Why Your Manufacturing Floor Still Runs on Spreadsheets
A third of manufacturers still manage production data in spreadsheets. Here's why. And what the path out actually looks like.
Read →AI Readiness: What It Actually Means for Your Business
AI readiness isn't about technology. It's about whether your data, processes, and people are structured enough for automation to work. Here's how to tell.
Read →