Ranger LES

The only born-integrated suite

Every price is public

Month-to-month — leave whenever

Built in Texas by a working cop

§ 01 — The part nobody else can copy

Born integrated. Not bolted together.

A competitor can work offline. A competitor can promise never to lose your report. Not one of them can make their apps genuinely talk to each other — their “suites” are acquisitions stapled together years after the fact. Ranger's fourteen products were written by one team on one database per agency: a K9 deployment becomes an RMS incident link, a range qualification gates a trainee's solo certification, a subpoena collides with a shift and Watch flags it before the sergeant ever sees the draft. Data is entered once — and every app you own already knows it.

See how the suite thinks →

§ 02 — Why we exist

Built by the guy who has to use it

I'm a Texas peace officer. Firearms instructor, armorer, and my department's accidental IT guy. For years I watched good cops fight bad software — systems that crash mid-report, eat a two-hour narrative at 3 a.m., and cost more than a patrol unit while doing less than a spreadsheet.

The companies selling that software have never sat in a parked cruiser finishing a DWI report at the end of a double. I have. So I started building the records system I actually wanted to use — and then I kept going: scheduling, the evidence room, training files, the armory bench, all of it.

Ranger LES is what happens when the person writing the code is also the person writing the reports. Every product here exists because somebody on shift needed it — not because a sales team needed a new line item.

Software built by people who've never written a report at 3 a.m. feels exactly like you'd expect.
— the founder, somewhere in Texas, probably at the range

§ 03 — The suite

Fourteen products. One login. One database per agency.

Buy what you need, when you need it — every product works alone and gets sharper with each one you add. Tap a card for the details, or hit Add to estimate and watch the math happen below.

§ 04 — The receipts

We read their public pricing pages so you don't have to.
(There aren't any.)

The legacy vendors have had decades and billions. Here's what that bought their customers — every incident below is documented public reporting, sources at the bottom. We built Ranger specifically to be the answer to this list.

CentralSquare at Houston PD Houston independent panel · 2024

Houston PD's records system let incident reports — including thousands of sexual-assault cases — sit suspended for years under a code meaning “no personnel available.” The independent review panel called the RMS ineffective. The city is now paying $31.2M for a replacement.

264,000+reports shelved, found in the 2024 review

The supervisor accountability dashboard ages every unreviewed report, stalled case, and NIBRS error in plain sight, with SLA timers per agency policy. Nothing waits quietly. A backlog like that would be on the chief's screen in week one — not in an independent panel report eight years later.

Motorola Spillman Flex NBC News · 2023 / San Angelo, TX council

NBC News documented Spillman crashing mid-911 call and losing police reports — sometimes while officers were still writing them. Closer to home: San Angelo's $1.5M Spillman deployment went so badly the city council voted 5–0 to borrow $2.4M just to return to its old system — then sued, and Spillman paid the city a $1.25M settlement.

$2.4Mborrowed by San Angelo just to un-deploy it (council vote, 2017)

Ranger autosaves every keystroke, recovers drafts across devices, and runs a public status page you can check anytime. “Never lose a report” is an architecture decision, not a slogan. And month-to-month terms mean a bad rollout never becomes a hostage situation — there's nothing to claw your way out of.

Tyler Technologies Public reporting · 2020–2026

A records empire assembled by acquisition — New World, Odyssey, and friends — whose own modules famously struggle to talk to each other. In 2020, ransomware hit Tyler itself: the same strain that hit TxDOT. Their products integrate about as well as feuding in-laws at Thanksgiving.

$670Mspent acquiring New World alone — integration sold separately

Ranger is one codebase on one database per agency. Our products talk because they were born in the same building — not bolted together in an M&A deal. There is no integration project, because there is nothing to integrate.

Mark43 User-documented · verified June 2026

Cloud-native, modern, very well-funded — and if your connection drops mid-report, your work can drop with it. No offline capability. The cloud is great right up until you're finishing a DWI at 3 a.m. behind a dead cell tower in Loving County.

0offline modes shipped as of June 2026 (Texas is 268,596 square miles)

Ranger persists drafts locally and server-side today, so a dropped connection doesn't eat your narrative — and an offline-capable field mode is on the roadmap for rural agencies. We build for the coverage map Texas actually has, not the one vendors wish it had.

The entire legacy industry Their websites · checked June 2026

Quote-only pricing. Multi-year lock-ins. Deployments measured in fiscal years — Houston's replacement was still rolling out three years after the contract was signed. The price isn't on the website because the price depends on how good your procurement lawyer is.

0published rate cards among the major LE records vendors (checked June 2026)

Our entire rate card is on this page with a calculator — same price whether you negotiate hard or don't negotiate at all. Month-to-month. Deploy in a day. One-click data export the day you decide to leave (we plan on you staying).

Sources & fair-play note: NBC News investigation into Spillman Flex failures (April 2023); the City of Houston Independent Review Committee's final report on suspended HPD incident reports (2024); San Angelo, TX council action reverting its Spillman deployment and the city's subsequent $1.25M settlement from Spillman (2017); public reporting on the 2020 Tyler Technologies ransomware incident; Tyler's 2015 acquisition of New World Systems ($670M, public filing); vendor websites checked June 2026 — no published pricing found. Every incident above is documented public reporting; we cite it because we built Ranger to be its opposite. Capability claims (offline support, published pricing) are statements as of the date shown and re-verified periodically. Product names belong to their owners.

§ 05 — The part everyone else hides

What will this cost my department?

This is our real rate card — not a teaser, not a “starting at.” Build your stack, watch the bundle math work, then print it straight into the council packet. Estimates are shareable by URL.

Your department

Sworn, licensed officers — it's the only number that matters here.

Officers

Core records

The foundation. $150/officer — never discounted, no asterisks. School PDs run SBLE instead of RMS, not on top of it.

Tier A — compliance & liability

The bundle ladder: own one and it's $35/officer. Own two, both drop to $25. Own three or more, all of them drop to $20.

1 product · $35

2 · $25 each

3+ · $20 each

Tier B — daily operations

Flat $15. Cheap on purpose — these are the apps your people open every single shift.

Analytics & specialist units

Stats stays cheap. K9 is integration-only — it exists to talk to your RMS, so it needs a suite to talk to.

§ 06 — Security & data

Your data, in its own vault

Most cloud RMS vendors put every customer in one big shared database and promise the rows won't mix. We think evidence deserves better than a promise.

A database per agency

Your records never share a table — or a database — with another agency. Isolation isn't a tenant ID column; it's physics.

Per-agency storage & keys

Evidence files live in your agency's own encrypted bucket with its own keys — encrypted in transit and at rest.

Audit-everything

Every state change writes an audit event in the same transaction as the change itself. Court-defensible by construction, not by cleanup.

CJIS-aware by design

Designed to CJIS Security Policy v6 controls — MFA, encryption, access logging, personnel screening. (Nobody is “CJIS certified” — anyone who says so is selling something.)

Texas-first compliance

NIBRS with the Texas rule layer, TCOLE training hooks, TEC §37.114 drills for school PDs. Built where you work, for how Texas reports.

Founder-direct support

Your support contact carries a TCOLE license, not a script. Texas time zone, Texas vocabulary, no ticket purgatory.

§ 07 — Straight answers

Frequently asked questions

What does deployment actually look like?

For a new agency: your tenant is provisioned, branded, and taking reports the same day — onboarding your roster takes about as long as a shift briefing. Migrating off a legacy system adds a structured data-migration pass, typically inside 30 days. Either way, nobody is billing you for a “multi-year implementation phase.”

Are these prices real, or “starting at” prices?

Real. The calculator above is the actual rate card, published on purpose — no quote-only games below 1,000 officers. Roadmap products show planned pricing that locks at general availability. Your formal quote just confirms officer counts and puts the same numbers on letterhead.

Is there a contract? Can we leave?

Month-to-month by default. Annual prepay is optional and takes 10% off — handy for single-PO procurement. If you leave, you get a one-click export of your data in documented formats. Vendors who make leaving painful are telling you something about their product.

We're a school district PD. Do we need RMS and SBLE?

No — SBLE is the records system for school-based law enforcement: campus-first incidents, TEC §37.114 drill compliance, threat assessment, FERPA-aware workflows. You buy SBLE instead of RMS, never both.

Is Ranger CJIS certified?

There is no such thing as a “CJIS certified” vendor — any company claiming the badge is marketing at you. What exists is the CJIS Security Policy (v6), and Ranger is designed to its controls: MFA, encryption in transit and at rest, auditing, personnel screening, and the agency-side agreements that go with them. Ask us for the control mapping; we'll actually send it.

Who actually builds this?

A working Texas peace officer (firearms instructor and armorer) and a deliberately small team. That's not a staffing limitation, it's the product strategy: every feature gets shaken down by someone who'll use it on shift. The longer story is up top.