What tech stack does Divergent Technologies use?

Public full-stack roles reference TypeScript, Node.js, APIs, scalable web applications, Docker, Kubernetes, cloud infrastructure, CI/CD, and distributed systems. Those are the normal software layers that support engineering, manufacturing, and operations workflows.

The more distinctive backend is DAPS itself. It is a production platform that turns engineering inputs into printable structures, manufacturing instructions, and automated assembly processes, which means the software stack is tightly tied to the physical factory.

Public robotics and process roles reference C++, C#, Python, machine-control software, PLCs, industrial communication protocols, MES, Teamcenter/NX, and data analysis for additive process development. That set points to a mixed cyber-physical stack: web apps for business workflows, low-level software for machines and robots, and engineering tools for design and process control.

Divergent's own site also identifies Monolith One as an in-house printer rather than a commercial product, so the technology surface includes proprietary hardware, materials process control, and automated assembly.

The stack maps to integration-heavy buying motions: PLM/MES integrations, industrial data pipelines, observability, OT security, identity, compliance, simulation, quality management, and factory automation. Because Divergent builds much of its core platform, vendors should position as accelerators or control layers around DAPS rather than as replacements for DAPS.

The practical discovery question is whether the buyer owns software, factory operations, quality, or defense program execution. Each group has a different pain point even though all roads eventually connect to production throughput.