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.
Software Development
Custom applications built around how users work in practice. Operations tooling, internal platforms, customer-facing products. Typed, tested, observable.
Practice areas
Systems Integration & EDI
Connect business applications through APIs, EDI, and file exchange. Deep experience in transportation workflows and common carrier and fuel retailer systems.
Operations Tooling
Internal tools that match how your team works day-to-day, not generic off-the-shelf software adapted to fit.
Internal Platforms
Developer platforms, data portals, and admin systems built for scale and maintainability.
Customer-Facing Products
Production web applications and APIs designed for reliability, performance, and real user load.
Full-Stack Engineering
End-to-end ownership from schema design through deployed, monitored production.
Transportation systems integration
EDI and API integration for transportation operations, with deep experience connecting common carrier and fuel retailer systems. Orders, dispatch, delivery records, billing, and fleet data working together.
Explore transportation integrationsWork in this practice
Integrated 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.
TCEQ delivery certificates commonly expire at month-end, turning 5,500+ Texas stores into a last-day compliance fire drill. We connected the Texas Open Data Portal to Gravitate so every site's delivery-certificate date updates nightly. One refresh surfaced 100 expired tanks before the next day's deliveries, avoiding up to $1M in potential fine exposure in a single day.
A mid-market fuel carrier needed delivery geofences for 7,000 convenience stores. Its dispatch team had been creating roughly 1,000 a month by hand. We built a map-based tool that let the team draw each site boundary and save it directly to the TMS, clearing the remaining backlog in weeks instead of months.
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.
Connected a mid-market fuel carrier's Gravitate dispatch platform to the TMSs its 5,000+ c-store customers run, using Manifold, our TMS integration platform. Customers see live load status, cost, and ETAs in their own systems, place orders that land in Gravitate, and get a DTN-sourced digital BOL for every load.
Consolidated six systems (DTN, Gravitate, Samsara, Bestpass, TMW, Google) into one data platform for the same mid-market fuel carrier. Dashboards track tank outages across 5,000+ sites, hold toll spend to policy and reclaim $200K+ a year, score every delivery window by GPS geofence, and keep driver hours honest.
Common questions
What kind of software does Riyex build?
Operations tooling, internal platforms, and customer-facing products. Typed, tested, and observable, built around how your team works in practice rather than how a generic tool assumes you work.
Who writes the code?
Senior engineers, end to end. No juniors on client work and no offshore layers; the person you talk to is the person doing the work.
Do we own the code you write?
Yes. The work happens in your repository from day one, and every engagement ends with documentation and a handoff session. We never hold code hostage.
What technologies do you work in?
Our core is TypeScript, Go, Postgres, React, and Kubernetes, with deep AWS experience including serverless architectures on Lambda and API Gateway. We fit the stack to your environment rather than forcing ours.
Need software development?
Let's talk.
Tell us what you're working on. We reply within one business day, usually from the engineer who'd run the engagement.