Skip to content
About

Reduction in OpEx.

Riopex is a product of Antitropy, LLC, built for groups that hold several legal entities.

Request a pilot
A skyline at blue hour
Type
About
Operated by
Antitropy, LLC
Stage
Built, taking first pilots
Updated
29 September 2026

The name

The name is the whole thesis. Riopex is Reduction in OpEx: telecom expense management for groups that hold several legal entities, usually across several countries, usually with a different carrier in each one.

It exists because three systems that should talk stay apart. Procurement knows what was ordered, the monitoring system knows what is delivered, and each operating company knows only its own half. The evidence to join them already sits inside the group, in three places, held by three people, in three currencies.

What you can expect from us

Everything on this site is a design decision we can defend, a count you can reproduce, or the category's own well-established figure. Logos, testimonials, case studies, awards, and our own accuracy and uptime figures arrive here the day they are earned.

SOC 2 is planned with the first pilot, and we will name it the day an audit backs it. Where a percentage appears on this site it belongs to the category rather than to Riopex, and the catalogue counts are reproducible from the same open sources the catalogue was built from.

What we are looking for

A group with this problem that would like it counted properly. Ideally several legal entities, more than one country, more than one carrier, and a monitoring system already in place.

A first conversation is a look at three invoices, a description of your group structure, and an honest answer about the fit. We will say whether Riopex would be useful to you this year or next.

Where the product is

The platform is built and runs today on a fictional demo group. What it does from the files a group already holds is listed below. Accuracy on one carrier's real invoices is measured in a pilot, on that carrier's own documents.

Every integration named on this site carries its own status label. Where a page says planned, it means planned, and the label moves the day the work lands.

  • Group structure: holding company, operating company, site and service, isolated per operating company in the database, with each company's functional currency and the rate id on every converted figure. Built.
  • Inventory: one list across companies, provenance on every field, imports with an undo and opt-in import cleanup. Built.
  • Bills: CSV and XLSX mapping, and PDF extraction into a human review queue, built; PDF accuracy is measured per carrier in a pilot. Structured e-invoicing XML and carrier portals are planned.
  • Contracts and pricing: price lines, amendments and notice deadlines with alerts, with a finding wherever a bill departs from the contract. Built.
  • Findings and disputes: billed but missing from the inventory, held but never billed, outside a contract or its term; disputes with evidence, bundles split to their member services, and budgets against actuals. Built.
  • Carrier confirmation: what you hold for a carrier, sent to it by email, with its answers kept as evidence field by field. Built.
  • Orders: requests, separated approvals, a budget check, a purchase-order tally and the carrier handoff by email or portal. Built. Carrier ordering APIs are planned.
  • Monitoring: PRTG, tested against recorded fixtures, is in progress, and six more systems are planned. Cost per megabit delivered waits on this connection.
  • Security and identity: SSO over OIDC and SAML, SCIM provisioning, MFA, country-scoped grants and an append-only audit trail. Built. Riopex runs as a hosted service.
  • The assistant: answers questions over your own data with your own permissions, on your organisation's own AI key. Built.
A bright office lounge with plants

How we work

We say the unattractive number first. Onboarding a group is months of human effort, and it is where products in this category die. We would rather have that conversation in the first meeting than in the fourth month. So the onboarding machinery is treated as product: imports with an undo, mappings that make the second month cheaper than the first, provenance on every field, and one queue for everything unresolved.

We keep the product defensible even where that makes it harder to sell. We read the monitoring system you already run, the MACD workflow ends at the carrier boundary, comparison stays inside your group, and our revenue comes from you alone. Why Riopex lists the commitments those decisions became, with the reasoning behind them.

We keep the word waste for two things, and the glossary is where both are defined. A quiet DR link is a circuit doing its job, and a tool that colours it red has told you it misreads your network.

Our definitions, including the word waste

People crossing a sunlit city street

Send three invoices. A person replies with what they show.

Request a pilot