A mid-market fuel carrier had tank-level inventory in Gravitate but no single operations view for finding low tanks across its customer base. We built a dispatch NOC dashboard that puts 20,000+ active tanks in priority order, so operators can spot inventory risk and turn it into the next delivery.
Turn operational complexity
into forward motion.
Senior software, data, and AI engineering. Deep transportation integration experience, connecting carrier and fuel retailer systems through EDI and APIs. Our engineers own the work end to end. No juniors on client work, no account managers in the way.
Keep freight moving.
Keep systems in sync.
Transportation systems integration through EDI and APIs. We connect orders, dispatch, delivery records, billing, and fleet data, with deep experience in common carrier and fuel retailer operations.
Explore transportation integrationsExplore all industries →EDI document exchange. API connections. Automation for workflows that live in desktop applications.
See our fuel carrier integration work →Running your operation on Gravitate?
We build the integrations and operations tools around Gravitate, from Crossroads connectivity to Supply & Dispatch API work. Connect the systems so your team can stop moving information by hand.
- 01Dispatch and exception views
- 02Retailer supply and tank intelligence
- 03Shared delivery records
- 04Carrier operations and customer tools
Five practices. One team.
Senior end to end.
No account managers. No offshore layers. You talk to the engineer who's doing the work. The same one who signs the SOW.
Agentic AI
Multi-agent architectures, custom workflows, and AI decision pipelines. We build systems that act, not just respond. Evals first, models second.
Read the agentic ai practiceSoftware Development
Custom applications built around how users work in practice. Operations tooling, internal platforms, customer-facing products. Typed, tested, observable.
Read the software development practiceStrategy & Advisory
Vision-to-execution guidance from people who build the thing, not just plan it. Architecture reviews, AI adoption strategy, roadmapping.
Read the strategy & advisory practiceSupport Operations
Ongoing system care. Not an afterthought, but a discipline. We keep production healthy so your team can focus on building.
Read the support operations practiceAI & Automation
Machine learning and automation solutions that turn data into decisions. From model development through production deployment and monitoring.
Read the ai & automation practiceBuilt to run in production. Not just to demo well.
Most consulting delivers a presentation. We deliver a system. Here's what that means in practice.
- Partnership over process
We work with clients, not at them. You get direct access to the engineer doing the work. No intermediaries.
- Simplicity over showmanship
The right solution, not the flashy one. We have zero interest in building things that don't matter.
- Engineering depth, every engagement
50+ years of combined expertise. No juniors on client work. The same people who scope the project ship it.
- Production-first thinking
We build to run at 3am. Evals before models. Observability before features. Debuggable by design.
Shipped systems.
Carrying the load.
Software, data, and AI systems built so the people running the operation can focus on their jobs.
View all workIntegrated daily Great Plains accounting data and banking-provider pending-invoice data into a mid-market fuel carrier's existing data lake and data mart. Metabase now combines financial records with operating data for finance reporting, payables, billing-completeness curves, line-haul analysis, and revenue projections.
After six years running Spentra's AWS environment, we rewrote the core Money Earned API from an aging Ruby monolith into a serverless distributed system on AWS Lambda and API Gateway. Daily deploys, lower costs, no servers to patch.
A managed TMS integration platform
Today, every fuel carrier builds and maintains its own connection to each retailer's systems. Manifold is designed so a carrier connects once, and we build and run the connections to each retailer. Orders, status updates, and invoices move without re-keying, and retailers can bring their carriers on board the same way.
It's early, and we're building it alongside the carriers and retailers who will use it. If integrations are eating your team's time, we'd love to hear what Manifold should handle first.
Learn more- 01Order and status updatesBetween carrier TMSs and retailer systems
- 02Invoice closeoutDaily X12 210 or CSV, no duplicates
- 03Order historyWhat was sent, where, and when
We couldn't ask for a better development operations partner in riyex. It's rare to find a partner this committed, responsive, and trustworthy. We truly value the partnership and trust them completely.
Three phases. No surprises.
Every Riyex engagement follows the same structured process. You always know where we are and what's coming next.
Discovery & scoping
We learn your system before we touch it. One week of structured discovery: architecture review, stakeholder interviews, constraint mapping.
Architecture & design
We design before we code. Every system gets an architecture doc, data model, and decision log before a line of implementation ships.
Build & ship
We ship to production, not staging. Weekly deployments, observed from day one. You own the repo. We never hold your code hostage.
Got something hard to build?
Let's talk this week.
Tell us what you're working on. We reply within one business day, usually from the engineer who'd run the engagement.
