Cedar AI

Name: Cedar AI
Brand: Cedar AI

Building transformational operational software for the railroad industry.

Est 2017|Valuation $200M|Raised $42.1M

LinkedIn 1K|Web traffic 9K|FTEs 56|HQ Seattle, Washington, US

MarketsSupply Chain Visibility Freight Management

Published Oct 15, 2026

01Common complaints

1. **Independent performance verification is required** - Vendor-published improvement figures (for example, the OptiSwitch performance range reported by the vendor) are not accompanied by public methodology. 2. **Public, fully transparent enterprise pricing is required** - API pricing is published, but full ARMS/AYMS implementation and module pricing appear to be sales-led and not publicly listed. 3. **Procurement depends on large volumes of third-party user reviews** - The vendor has limited presence on mainstream review platforms; if the procurement process relies heavily on G2/Capterra-style review volume, evaluation may be more difficult. 4. **The buyer prefers a long-tenured incumbent with an extensive managed-services layer** - Some buyers may prefer providers with decades-long track records and bundled services, which can reduce perceived implementation risk for certain organizations.

Deal disqualifiers (poor fit)

Organizations that require extensive independent third-party benchmarking before procurement
Environments with extreme offline or connectivity constraints that cannot tolerate synchronization limitations
Buyers that require a vendor with decades of continuous incumbent services and a heavy managed-services orientation

Publicly acknowledged limitations

The mobile application’s offline approach is described as minimal and intentionally avoids automatic synchronization, which implicitly acknowledges that offline synchronization can create operational risk.

Roadmap visibility

Some solution pages indicate items as coming soon, but current roadmap dates and commitments are not clearly published.

Scale limitations

The vendor reports customers across a wide scale range, but there is no public SRE-style reliability data (uptime SLA or incident history) to validate enterprise-scale maturity.

Security and compliance gaps (public information)

SOC 2 is claimed, but the attestation type (Type I vs Type II) is not specified publicly.
ISO 27001 and related certifications are not documented in the reviewed materials.
Data residency controls are not clearly documented publicly.

02Why they buy

Differentiation supported by available evidence

- **Event-based workflow automation:** vendor describes configurable event-driven automation intended to reduce manual processes (ARMS/AYMS and referenced "IFTT networks"). - **Contemporary identity and access posture:** documented support for SSO and RBAC, and a SOC 2 claim. - **Multi-solution suite:** the vendor offers a set of modules covering railroad inventory and revenue, yard planning, mobile operations, and storage planning.

Where competitors may have stronger differentiators

Bourque Logistics: depth of industrial shipper workflows and associated services; longer operating history.
Railinc: industry-standard data services and essential exchange mechanisms.
RailTech: published pricing and conventional packaged procurement models.

03Field reports

Review platform coverage (G2, Capterra, TrustRadius)

A key limitation in this research: the platform does not appear to have a robust footprint on mainstream SaaS review platforms with easily discoverable product review pages. In rail software—especially operational systems—peer reviews are often sparse and deals are reference-based. Implication for buyers: procurement teams may need to rely on: - direct customer references from organizations with similar size and operational characteristics - on-site demonstrations and pilot programs - contractual service level agreements (SLAs) and implementation statements of work

Vendor-published testimonials and vendor claims

The vendor site emphasizes automation and reported performance improvements. One vendor-published performance claim references OptiSwitch delivering a measurable reduction in manual procedures.

Caution: this performance claim is vendor-published and is not accompanied by an independently verifiable methodology (sample size, baseline definition, yard complexity, etc.).

Third-party case-style narrative (outside the vendor)

A partner blog describes operational impacts such as:

minimal manual input for tracking car movements
near-automated inbound/outbound traffic management
integration with AEI readers and cameras to log arrival and departure events

Caution: this is partner or customer narrative and should not be treated as independent analyst validation; it may reflect a successful deployment without documenting failure modes or full project context.

Community / social proof (Reddit, Hacker News)

Public discussion about the platform appears limited compared to mainstream SaaS categories. Possible interpretations include:

the niche market does not typically discuss operational tools publicly
the vendor has modest public mindshare outside rail circles
operational tooling is treated as sensitive by customers

1) Partner integration announcement (press release)

An announced integration with an industrial yard management provider positions the vendor’s ARMS as a rail inventory and revenue system interoperating with yard management solutions.

What this suggests: Cedar is positioning to interoperate within existing rail and shipper ecosystems rather than replacing them end-to-end.
Critical note: press releases are promotional and rarely describe implementation pitfalls, cost, or unsuccessful projects.

2) Rail park customer blog (customer narrative)

A rail park operator blog describes the vendor’s automation enabling near-automatic tracking of railcar movement events and automated messages and notifications.

Reported outcomes: reduced manual input, improved accuracy, and automated event logging via AEI and camera integrations.
Critical gaps: no quantified before/after key performance indicators and no counterfactual comparison.

04Best fit

Company sizes

Based on product positioning, likely ICP bands include: - Small and mid-size rail operators (short lines and regionals) that do not maintain extensive internal IT for specialized rail systems - Industrial operators such as logistics parks, plants, and refineries with private rail operations A pragmatic buyer-based ICP (suggested): - Organizations with roughly 50 to 2,000 employees (ranges vary widely in rail) - Operations where inventory accuracy and billing/revenue workflow automation provide a clear return on investment

Industries and verticals

Freight railroads (particularly short lines)
Industrial shippers with in-plant rail operations
Transload operations
Intermodal and terminal operators

Roles and personas

VP or Director of Operations
Yardmasters, dispatchers, and trainmasters
Billing and revenue accounting teams
IT and systems integrators responsible for ERP/EDI/identity integrations

Qualification criteria (good fit)

Clear operational pain related to manual inventory and billing processes
Ability to integrate AEI and EDI data sources
Willingness to adapt workflows to an event-based automation model

05The pitch

What the product does (objective core value proposition)

Cedar AI builds AI-enabled, rail-focused transportation management systems (TMS) and operating platforms used to run day-to-day railroad and rail-adjacent operations. Its product suite centers on: - **ARMS (Automated Rail Management System):** inventory and revenue operations for railroads (inventory single source of truth, EDI, billing, switch lists, interchange workflows). - **AYMS (Automated Yard Management System):** similar user experience and automation approach for non-railroads with complex rail operations (logistics parks, mills, refineries, chemical plants). - **OptiSwitch:** yard planning and switching optimization (automated generation of cutlists). - **Cedar Mobile:** mobile and offline workflows for crews. - **Additional modules/solutions:** Automated Storage Network (ASN), Yard Event Tracking, Transload and Intermodal-focused systems. Cedar describes its offering as automation of rail inventory events, workflow rules, and integrations intended to reduce manual clerical work and improve operational accuracy.

Target market and market positioning

**Primary buyers/users:** - Short line and regional railroads, industrial rail operators, transload facilities, intermodal and container yards, industrial parks, and shippers with private rail operations. **Positioning themes (vendor messaging):** - Described by the vendor as a modern rail operating stack with AI-assisted planning and automation. - Contemporary user interface relative to older rail inventory systems that rely on manual rule tables.

Get a comprehensive analysis of Cedar AI including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Oct 15, 2026

01Common complaints

Independent performance verification is required
- Vendor-published improvement figures (for example, the OptiSwitch performance range reported by the vendor) are not accompanied by public methodology.
Public, fully transparent enterprise pricing is required
- API pricing is published, but full ARMS/AYMS implementation and module pricing appear to be sales-led and not publicly listed.
Procurement depends on large volumes of third-party user reviews
- The vendor has limited presence on mainstream review platforms; if the procurement process relies heavily on G2/Capterra-style review volume, evaluation may be more difficult.
The buyer prefers a long-tenured incumbent with an extensive managed-services layer
- Some buyers may prefer providers with decades-long track records and bundled services, which can reduce perceived implementation risk for certain organizations.

Deal disqualifiers (poor fit)

Organizations that require extensive independent third-party benchmarking before procurement
Environments with extreme offline or connectivity constraints that cannot tolerate synchronization limitations
Buyers that require a vendor with decades of continuous incumbent services and a heavy managed-services orientation

Publicly acknowledged limitations

The mobile application’s offline approach is described as minimal and intentionally avoids automatic synchronization, which implicitly acknowledges that offline synchronization can create operational risk.

Roadmap visibility

Some solution pages indicate items as coming soon, but current roadmap dates and commitments are not clearly published.

Scale limitations

The vendor reports customers across a wide scale range, but there is no public SRE-style reliability data (uptime SLA or incident history) to validate enterprise-scale maturity.

Security and compliance gaps (public information)

SOC 2 is claimed, but the attestation type (Type I vs Type II) is not specified publicly.
ISO 27001 and related certifications are not documented in the reviewed materials.
Data residency controls are not clearly documented publicly.

02Why they buy

Differentiation supported by available evidence

Event-based workflow automation: vendor describes configurable event-driven automation intended to reduce manual processes (ARMS/AYMS and referenced "IFTT networks").
Contemporary identity and access posture: documented support for SSO and RBAC, and a SOC 2 claim.
Multi-solution suite: the vendor offers a set of modules covering railroad inventory and revenue, yard planning, mobile operations, and storage planning.

Where competitors may have stronger differentiators

Bourque Logistics: depth of industrial shipper workflows and associated services; longer operating history.
Railinc: industry-standard data services and essential exchange mechanisms.
RailTech: published pricing and conventional packaged procurement models.

03Field reports

Review platform coverage (G2, Capterra, TrustRadius)

Implication for buyers: procurement teams may need to rely on:

direct customer references from organizations with similar size and operational characteristics
on-site demonstrations and pilot programs
contractual service level agreements (SLAs) and implementation statements of work

Vendor-published testimonials and vendor claims

The vendor site emphasizes automation and reported performance improvements. One vendor-published performance claim references OptiSwitch delivering a measurable reduction in manual procedures.

Caution: this performance claim is vendor-published and is not accompanied by an independently verifiable methodology (sample size, baseline definition, yard complexity, etc.).

Third-party case-style narrative (outside the vendor)

A partner blog describes operational impacts such as:

minimal manual input for tracking car movements
near-automated inbound/outbound traffic management
integration with AEI readers and cameras to log arrival and departure events

Community / social proof (Reddit, Hacker News)

Public discussion about the platform appears limited compared to mainstream SaaS categories. Possible interpretations include:

the niche market does not typically discuss operational tools publicly
the vendor has modest public mindshare outside rail circles
operational tooling is treated as sensitive by customers

1) Partner integration announcement (press release)

An announced integration with an industrial yard management provider positions the vendor’s ARMS as a rail inventory and revenue system interoperating with yard management solutions.

What this suggests: Cedar is positioning to interoperate within existing rail and shipper ecosystems rather than replacing them end-to-end.
Critical note: press releases are promotional and rarely describe implementation pitfalls, cost, or unsuccessful projects.

2) Rail park customer blog (customer narrative)

A rail park operator blog describes the vendor’s automation enabling near-automatic tracking of railcar movement events and automated messages and notifications.

Reported outcomes: reduced manual input, improved accuracy, and automated event logging via AEI and camera integrations.
Critical gaps: no quantified before/after key performance indicators and no counterfactual comparison.

04Best fit

Company sizes

Based on product positioning, likely ICP bands include:

Small and mid-size rail operators (short lines and regionals) that do not maintain extensive internal IT for specialized rail systems
Industrial operators such as logistics parks, plants, and refineries with private rail operations

A pragmatic buyer-based ICP (suggested):

Organizations with roughly 50 to 2,000 employees (ranges vary widely in rail)
Operations where inventory accuracy and billing/revenue workflow automation provide a clear return on investment

Industries and verticals

Freight railroads (particularly short lines)
Industrial shippers with in-plant rail operations
Transload operations
Intermodal and terminal operators

Roles and personas

VP or Director of Operations
Yardmasters, dispatchers, and trainmasters
Billing and revenue accounting teams
IT and systems integrators responsible for ERP/EDI/identity integrations

Qualification criteria (good fit)

Clear operational pain related to manual inventory and billing processes
Ability to integrate AEI and EDI data sources
Willingness to adapt workflows to an event-based automation model

05The pitch

What the product does (objective core value proposition)

Cedar AI builds AI-enabled, rail-focused transportation management systems (TMS) and operating platforms used to run day-to-day railroad and rail-adjacent operations. Its product suite centers on:

ARMS (Automated Rail Management System): inventory and revenue operations for railroads (inventory single source of truth, EDI, billing, switch lists, interchange workflows).
AYMS (Automated Yard Management System): similar user experience and automation approach for non-railroads with complex rail operations (logistics parks, mills, refineries, chemical plants).
OptiSwitch: yard planning and switching optimization (automated generation of cutlists).
Cedar Mobile: mobile and offline workflows for crews.
Additional modules/solutions: Automated Storage Network (ASN), Yard Event Tracking, Transload and Intermodal-focused systems.

Cedar describes its offering as automation of rail inventory events, workflow rules, and integrations intended to reduce manual clerical work and improve operational accuracy.

Target market and market positioning

Primary buyers/users:

Short line and regional railroads, industrial rail operators, transload facilities, intermodal and container yards, industrial parks, and shippers with private rail operations.

Positioning themes (vendor messaging):

Described by the vendor as a modern rail operating stack with AI-assisted planning and automation.
Contemporary user interface relative to older rail inventory systems that rely on manual rule tables.

Get a comprehensive analysis of Cedar AI including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →