GTFS·X vs. Remix by Via
Remix is a transit planning suite — drag-to-edit network design, multi-scenario workshop tools, service equity analysis, GIS-integrated route drawing. It was acquired by Via in 2021 and is now branded "Remix by Via." It serves 340+ cities across 22 countries and is the go-to tool for transit planning departments at mid-to-large agencies and MPOs doing active service redesign.
GTFS·X is a GTFS editor with planning analyses and scenario comparison workflows built in: cost estimation, demographic coverage, Title VI equity analysis, a nationwide demand-propensity layer, and snapshots that let you save and compare multiple feed versions side-by-side. The primary purpose is producing and maintaining a clean GTFS feed; the planning capabilities serve agencies who want to evaluate their own service alternatives without leaving the editing tool.
These are adjacent products with overlap in the analysis layer. The honest comparison is whether you need drag-to-edit network design at scale (Remix) or a GTFS editor that includes the planning analyses and scenario comparison most small-and-medium agencies actually need (GTFS·X).
This page is split. If you're evaluating planning tools for the first time, start with the comparison table. If you're an existing Remix customer wondering if you still need it, skip to the section further down.
Quick comparison (first-time buyers)
| Remix by Via | GTFS·X | |
|---|---|---|
| Primary purpose | Transit planning + scenario modeling | GTFS feed authoring + planning analyses + scenario comparison |
| GTFS authoring | Yes, via export from planned scenarios | Yes, as the core feature |
| GTFS-Flex authoring | Limited | Full support — polygon zones, booking rules, stop groups |
| Drag-to-edit network design at scale | Yes — this is the core | No |
| Multi-scenario workshop tools (side-by-side, stakeholder voting) | Yes — this is the core | No |
| Scenario comparison via saved snapshots | Yes | Yes — snapshot any feed state, restore or compare later |
| Title VI / equity analysis | Yes | Yes (Team tier) |
| Demographic coverage | Yes (integrated GIS) | Yes (Pro tier) |
| Cost estimation | Yes | Yes (Pro tier) |
| Demand-propensity layer | Yes (integrated demographics) | Yes — nationwide transit-propensity map layer, free for all tiers |
| Hosted GTFS publishing at stable URL | Some support; not the primary product | Yes — $500/yr standalone |
| Cost | Enterprise, quote-based; commonly $20,000–$150,000+/yr depending on agency size and scope | Free editor; $49/mo Pro, $199/mo Team, $500/yr hosted publishing |
| Procurement complexity | Enterprise contract; RFP common | Sub-$5k SaaS that fits small-purchase signature authority |
| Best fit | Mid-to-large agencies, MPOs, planning departments doing active service redesign with multi-scenario workshops | Single agencies producing + publishing a feed and using built-in analyses to evaluate alternatives |
Where Remix is genuinely better
Real categories where Remix is the right answer:
- Drag-to-edit network design at scale. Remix's core UX is moving service around on a map — drag a route, see the cost and ridership impact, save the scenario, repeat. If you're actively redesigning a network with frequent edits and multiple working scenarios, Remix's editing flow is purpose-built for that. GTFS·X can compare scenarios via snapshots, but it doesn't have the drag-to-redesign-and-see-impact-live workflow.
- Multi-scenario workshop tools. Remix is built for planning departments running redesign workshops with stakeholders — side-by-side scenario comparison, voting, shared review. If that's your workflow, Remix is the right tool. GTFS·X's snapshot workflow handles "what did the feed look like last month" cleanly but isn't a workshop-facilitation tool.
- GIS-integrated workflows. Remix integrates demographics, parcels, employment, and other GIS layers into the planning environment. For planners who think in spatial overlays, this is a real workflow advantage. GTFS·X has demographic coverage analysis and a nationwide demand-propensity layer but doesn't aim to be a GIS platform.
- Multi-jurisdiction planning. MPOs and regional agencies coordinating service across multiple operators have a structurally different workflow than a single-agency GTFS editor. Remix is built for that scale; GTFS·X isn't.
- Existing Via operations stack. If your agency is using Via for microtransit operations or rider-facing tech, having Remix in the same vendor relationship is a real consolidation benefit. The integration story has substance.
Where GTFS·X is genuinely better
Five categories:
- You primarily need to produce and maintain a GTFS feed with planning analyses on the side, not redesign your network from scratch. Most small and small-urban agencies are in this category. The service plan is mostly stable; the work is keeping the GTFS feed clean, validated, and published — and running cost / coverage / Title VI analyses on the existing or proposed service. Remix is overkill — and over-priced — for that primary need.
- Scenario comparison via snapshots, not workshop tooling. GTFS·X lets you snapshot any feed state and restore or compare later. For evaluating "what would happen if we added Saturday service" or "how does this restructure compare to the current network," snapshots + the cost / coverage / Title VI analyses cover the substantive workflow without the workshop overhead. If you don't need stakeholder workshops, you don't need Remix's workshop tooling.
- You operate fixed-route + Flex and need both in one tool. Remix's Flex authoring is limited; GTFS·X has full Flex support including polygon zones, booking rules, and stop groups.
- Transparent pricing under $5k/year. GTFS·X pricing is on the pricing page: $49/mo Pro, $199/mo Team, $500/yr hosted publishing. Remix is enterprise-quoted. For a small-agency procurement, the price difference and the transparency difference both matter.
- No signup to evaluate. GTFS·X editor and export are anonymous. You can build a complete feed and run the analyses before deciding whether to pay for anything. Remix evaluation requires sales engagement.
Thinking about switching?
If you're an existing Remix customer reading this, the answer probably depends on what you're using Remix for. A few cases:
Case 1: You're paying for Remix but only using it for GTFS authoring
This is the case where switching may pencil. Remix-by-Via enterprise pricing for an agency that only uses the GTFS authoring features (plus the analyses GTFS·X also has) is overpaying by roughly an order of magnitude versus the comparable GTFS·X tiers. If you're not actively using the drag-to-edit network design, multi-scenario workshop tooling, or multi-jurisdiction coordination, you're paying for capabilities you don't use — and GTFS·X covers cost, coverage, Title VI, and snapshot-based scenario comparison at a fraction of the price.
Practically:
- Audit your Remix usage over the last 12 months. If 80%+ of seat-hours are on GTFS authoring tasks vs. planning tasks, you're a switching candidate.
- Export your current GTFS feed from Remix.
- Import into GTFS·X (anonymous editor, no signup).
- Verify the feed validates and matches what Remix produced.
- Decide between Pro ($49/mo, cost + coverage) and Team ($199/mo, adds Title VI + propensity) based on which analyses you need.
- Optional: hosted publishing at $500/yr if you want a stable URL with monitoring.
Total: $1,088/yr to $2,888/yr depending on tier, versus likely $20,000–$60,000/yr for Remix. The savings is real if the usage audit supports it.
Case 2: You're using Remix for active network redesign with stakeholder workshops
Don't switch. Remix's drag-to-edit and multi-scenario workshop tooling is built for what you're doing; GTFS·X's snapshot-based scenario comparison won't replace it. The GTFS authoring side is a small portion of your Remix value.
Case 3: You're an MPO coordinating across multiple operators
Probably don't switch — Remix's multi-jurisdiction model is built for that workflow. GTFS·X is single-agency-oriented and you'd be giving up coordination tooling that Remix handles well.
What the math looks like
For an agency paying $30,000/yr for Remix and using it primarily for GTFS authoring with occasional Title VI analyses, the GTFS·X equivalent (Team tier + Hosted) is $2,888/yr. Annual savings: ~$27,000, against the staff time to learn a new tool and migrate the feed. For most agencies that's a 1–2 week migration window for a roughly 10x annual cost reduction. Worth doing if the usage audit supports it.
For an agency paying $80,000+/yr because Remix is bundled with other Via services, the math depends on what else you're buying — savings on the GTFS side may not justify unbundling.
The Remix-by-Via rebrand
A note on brand confusion: Remix is being progressively integrated into Via's product naming. Some Via marketing now refers to "Via's transit planning platform" without explicitly calling out the Remix brand. The underlying tool is still Remix; the product page still exists at ridewithvia.com/solutions/remix. Customers report some uncertainty about whether Remix will remain a standalone product or get fully absorbed into Via's broader platform. As of mid-2026, it's still distinguishable.
If you're procuring "Remix" today, you're procuring Via's transit planning platform with the Remix branding on the planning suite. The contracting entity is Via.
FAQ
Is GTFS·X a planning tool? Partially. GTFS·X is a GTFS editor with planning analyses (cost, coverage, Title VI, demand propensity) and snapshot-based scenario comparison built in. What we don't do is drag-to-edit network redesign at scale or multi-stakeholder workshop tooling — those are Remix's strengths. If your workflow is "evaluate alternatives to my existing service and pick one," GTFS·X handles it. If your workflow is "actively redesign a network from scratch with stakeholders," you need Remix.
Can I export from Remix and import into GTFS·X? Yes. Remix produces standard GTFS that GTFS·X imports cleanly. Round-trip preserves all standard GTFS files.
Will my Remix integrations (downstream consumers, agency website embed, etc.) still work after switching? The GTFS feed itself is standard, so trip planners and other consumers see no change. Any custom Remix integrations (data layer in your agency website, embed widgets from Remix) would need to be replaced with equivalents.
What if my staff is trained on Remix? GTFS·X has a different UI and a different scope (editor, not planning suite). There's a learning curve. The quickstart docs cover the editor end-to-end and most agency staff can produce a feed within a working day.
What about Remix's Title VI tooling specifically? GTFS·X has Title VI equity analysis built into the Team tier ($199/mo), using ACS data with the four-fifths threshold convention from FTA Circular 4702.1B. It's not a one-to-one replacement for Remix's full equity workflow, but for most small-urban Title VI analyses it produces the same output.
Try the GTFS·X editor at gtfsx.com — anonymous, no signup. Or book a 30-minute consult call to talk through whether self-serve fits your agency.