Case Study
CloneOps.ai
Low-code workflow infrastructure for trucking operations
CloneOps needed a platform that could connect internal workflows, external trucking systems, communication channels, and product billing. Adapter built the service architecture and integrations foundation that made those agent-driven operations traceable and usable in production.
Engagement
Dedicated
Full engagement, product and engineering
Stack
Vite, Express, NestJS, Node.js, MongoDB
Plus Redis, BullMQ, NATS, Telnyx, Gmail, Microsoft, and Stripe
The Challenge
Trucking teams run on fragmented communication
CloneOps focused on automating load communication in the trucking industry, but the product depended on multiple services, external trucking management systems, and communication channels all working together. The platform needed reliable service-to-service messaging, deep observability, and workflows that non-engineers could use to deliver customer-specific solutions.
The existing architecture had grown organically across Express and NestJS services. As the product expanded, coordinating state and behavior between services became a bottleneck. CloneOps needed a team that could rearchitect the backend while continuing to ship product features on a tight timeline.
Key Requirements
What they needed
- 01
Distributed service coordination across Express and NestJS
- 02
Low-code platform for non-engineers to build customer products
- 03
Integration layer for external trucking management systems
- 04
Full traceability across flows, executions, and logs
What We Built
Core platform systems for operational automation
Flows v1 and Flows v2
Built the original single-flow workflow product, then helped turn it into Flows v2: a more powerful low-code development platform that enabled account executives to build products for customers.
Distributed Service Architecture
Set up microservice communication over NATS across both Express and NestJS services so platform capabilities could be composed across multiple backend systems.
Trucking System Integrations
Built the platform layer that connected CloneOps to other trucking management systems, making operational data available inside the product.
Communications and Billing
Implemented Gmail, Microsoft, and Telnyx integrations for agent communication, alongside Stripe subscriptions and usage tracking for commercial billing.
Analytics, Logs, and Traceability
Built full-feature analytics and logs pages and made flows and executions deeply traceable so engineers could inspect behavior across the platform.
How We Worked
Engagement structure
Embedded product and engineering
Our team worked as a dedicated extension of CloneOps, handling both product decisions and technical implementation. We were not a separate vendor. We were part of the team shipping the product.
Weekly delivery cycles
Every week had visible output. We shipped features, integrations, and infrastructure improvements in tight loops so the team could see progress and adjust priorities based on real results.
Parallel workstreams
While building Flows v2 and the integrations platform, we simultaneously maintained and improved existing services. Product development and platform stability moved forward together.
Full knowledge transfer
Every system we built came with documentation, runbooks, and context for the internal team. The goal was always to leave CloneOps in a position to own and extend the platform independently.
Have a project like this?
We help teams scope, build, and ship complex platforms. Let's talk about what you're building.
Ready to get started?
Tell us about your project and we will scope an engagement that fits.