Name a vendor. Ronin drafts the connector. You publish it — no code.
A self-contained connector engine that normalizes every OEM, GPS, TPMS, and fuel-card feed into one canonical schema — licensable to run inside your own product, not just ours.
Name a vendor. Get a working connector. Write no code.
Ronin finds the vendor's developer docs, drafts the connector — auth, endpoints, field map, and the nuances worth knowing — and a person reviews and publishes it. That's the whole flow, and it genuinely runs today.
One canonical schema. Every vendor's shape disappears.
Every feed maps to canonical signals built on ISO 15143-3 (AEMP 2.0) and COVESA VSS, with surplus vendor-specific fields retained per client rather than dropped on the floor.
Mapped once, inherited by everyone
A connector's field map is built by 2Quip a single time. Every account that connects to it — ours or yours — inherits the mapping from day one.
Standards-first, nothing discarded
Canonical signals cite the standard section they come from. Vendor fields that don't fit a standard are kept, not dropped, so nothing a customer relied on disappears.
Checkable, not just claimed
Every mapped signal carries its citation — the standard and section, or the vendor doc it was read from — so a customer or vendor can audit it line by line.
Geotab and Samsara are connectors in our system.
We normalize the vendor our fleet competitor is. That's the whole argument for renting this rather than building it.
- Cat VisionLink
- John Deere Ops Center
- JLG Link / SkyWatch
- Takeuchi Connect
- Geotab
- Samsara
- PressurePro TPMS
- WEX Fuel Cards
The engine is architected to build and manage hundreds of connectors on demand. What's live today is a smaller, growing library — see Packaging for the two ways to get coverage.
Two ways to buy.
The contrast is the point — engine-only is real and workable, but the bundle is what gets a second software company live fast.
Engine only
Build your ownLicense the connector engine and use Ronin's build flow to draft your own connector library. Cheaper to start, slower to first value, and the library is entirely yours to shape.
Engine + library
Bundled coverageOur connector library ships with the deal. Productive on day one instead of building connectors yourself. The library is a second asset on top of the engine, not a feature of it.
The bundled library is approaching 100 connectors, targeted for Q1. As of this writing it's 12 connectors live — the number is growing, and this page will be updated as it does.
Its own MCP server, plus a scoped REST API.
Ronin uses the exact same tool facade a customer's own agent or integration would — nothing is exposed externally that isn't already trusted internally.
Every key authenticates as Authorization: Bearer quip_sk_… and resolves to exactly one account. There's no such thing as a key that spans tenants.
Each tool declares the scope it needs; a key only sees and calls the tools its scopes allow. Reads and writes are marked separately so a client can auto-approve one and confirm the other.
Every call runs under row-level security for its account. A scoping mistake in application code still can't leak another tenant's data.
Authorization: Bearer quip_sk_…
Ronin watches every vendor's API so a schema change doesn't silently break your feed.
Every connector carries the field-level doc citations Ronin captured when it was built. When a vendor changes their API, scheduled re-reads catch the drift, Ronin drafts the fix against those same citations, and a person reviews it before it ships — the same review step as the original build, not a fire drill.
Connector coverage at this scale is normally a team. Ours runs on one person plus a handful of agents.
We're not asking you to take the agent-workforce pitch on faith. The same small operation that built and maintains this connector library is the one licensing it to you — and RME Rents, our own rental division, runs on the platform this engine feeds.
Talk to us about licensing.
Tell us which vendors you need covered and how fast. We'll walk through the engine, the library, and what a rollout looks like inside your own product.