# chrt: software for time-critical shipping

Canonical: https://mudpie.ai/companies/chrt/
Breadcrumb: [Home](https://mudpie.ai/) / [Companies](https://mudpie.ai/companies/) / [chrt: software for time-critical shipping](https://mudpie.ai/companies/chrt/)
Author: Ali Abouelatta (https://mudpie.ai/authors/ali-abouelatta/)
Published: 2026-09-19
Updated: 2026-09-19
Research type: Company profile
Method: Company and accelerator sources checked 2026-09-19. Product claims are attributed to their sources; this is research, not a hands-on product trial.

## What it does

chrt is a logistics platform for time-critical shipping. It serves the three parties in the movement: couriers get dispatch, driver and fleet tools; forwarders can book flights, coordinate providers and track orders; shippers get placement and visibility. It also sells physical tracking devices, giving the company a way to see cargo or assets beyond a software-only status feed. The [YC profile](https://www.ycombinator.com/companies/chrt) describes the market as urgent healthcare and industrial shipments; the [homepage](https://chrt.com/) shows the operating view, AWB milestones, payment flow and a single order record.

The fit is a courier or forwarder whose work is too time-sensitive for email, carrier portals and disconnected spreadsheets. The strongest use cases are pharma, medical equipment and other shipments where a missed milestone has operational cost. This is not a generic fleet dashboard: the value is coordinating an exception across shipper, forwarder, courier and carrier while keeping the money trail attached to the order.

## Why I’d look closer

The public product surface is unusually complete. chrt shows dispatch and driver location, airline milestones, control-tower search, multi-party payments, Stripe/QuickBooks/Sage connections and an API surface. The [docs](https://docs.chrt.com/support) link onboarding for couriers, shippers and forwarders, concepts such as rate sheets and connections, an API reference and SDKs. That gives an evaluator something concrete to inspect before a sales call.

Pricing is also public. The [pricing page](https://chrt.com/pricing) lists Small Team at a $250 monthly minimum or $0.50 per completed stop, Medium at $500, and Large at $1,000, with the same usage rule. A tracker-only plan is listed at $30/month, with hardware and usage billed separately. Those rates describe provider and tracker plans; they do not answer what a large forwarder’s multi-party implementation will cost.

The founder background is close to the problem. The YC biographies describe Kyle Reagan as a former strategy lead at a time-critical-logistics company who worked with enterprise customers, and Aaron Carver as a full-stack and AI/ML engineer who deployed NLP services and hosted LLMs in high-security environments. That pairing helps explain the blend of operational domain knowledge and coordination software.

## What I’d ask

Which carrier, airline and TMS connections are live, and what happens when a milestone is late or wrong? I’d test one real lane with a cold-chain or high-value exception, inspect the driver and customer views, and validate liability, tracker replacement, insurance, permissions and payment reconciliation. The demo data is useful for understanding the product; it is not evidence of real customer volume.

## My editorial take

chrt is a good fit for time-critical operators that need one operational and financial record across the shipment chain. The public docs and pricing make it easier to evaluate than most logistics startups. I’d still insist on a lane-level pilot: the product earns its keep only when it helps a team intervene before a missed milestone cascades.

## Quick facts

| Field | Sourced detail |
|---|---|
| Buyer fit | Couriers, forwarders and shippers handling urgent freight |
| Public pricing | $250/$500/$1,000 provider minimums plus $0.50 per completed stop; tracker-only $30/month |
| Docs | Public onboarding, API, SDK and support surfaces |
| Product boundary | Operations, tracking, billing, payments and optional hardware trackers |

## Sources checked

Checked 2026-09-19.

| Source | Used for |
|---|---|
| [YC company profile](https://www.ycombinator.com/companies/chrt) | Market, product and founder context |
| [chrt homepage](https://chrt.com/) | Current operations, tracking and payment surfaces |
| [Pricing](https://chrt.com/pricing) | Current provider and tracker plan terms |
| [chrt docs](https://docs.chrt.com/support) | Onboarding, API, SDK and support links |

## Cohort context

chrt is listed in Spring 2025. In our 2026-09-18 directory snapshot, 97 of 143 listed companies in that cohort have YC’s primary industry label B2B (67.8%). This is a current-directory comparison, not an original intake count or a performance ranking. [Nine-cohort dataset](https://mudpie.ai/research/yc-cohorts-2026-09-19.json).

## Public website snapshot

Observed 2026-09-19T16:15:59.186Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.

| Signal | Homepage observation |
| --- | --- |
| Product description metadata | Observed |
| Canonical link | Observed |
| H1 or H2 heading | Observed |
| Typed structured data | Observed |
| Docs/developer link | Observed |
| Pricing link | Observed |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |

[Public observations](https://mudpie.ai/research/yc-homepage-links-2026-09-19.json) · [Collection method](https://mudpie.ai/research/yc-homepage-methods/README.md). Missing links here do not establish that a capability or file is absent elsewhere.


## Author disclosure

I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.