GTFS·X vs. Spare GTFS-Flex Builder

Spare offers a free GTFS-Flex Builder as a wedge into their broader microtransit operations platform. It's a real tool that does real work — if you're already running Spare for dispatch and operations, their Flex Builder is the obvious choice. GTFS·X is the fast, free GTFS editor — anonymous, browser-based, no signup. The question is whether you want a Flex-only tool inside a dispatching platform or a fast GTFS editor that handles both fixed-route and Flex.

This page is the comparison. Three concrete differences matter; everything else is detail.

The three differences that matter

1. GTFS·X requires no signup. Spare's Flex Builder requires sign-up before you can see the editor.

This is the headline difference. With GTFS·X you land on the page, edit, validate, and export a valid GTFS feed without creating an account. Accounts only become necessary if you want feed management — saving across sessions, hosted publishing, multi-user collaboration. Spare requires you to submit a form, wait for access, then start.

For a transit director evaluating tools on a Tuesday afternoon, "click and start" beats "submit a form and wait" every time. The first version of a Flex zone takes about 90 seconds in GTFS·X starting from a cold browser. In Spare, you can't time it because you can't start until you've cleared the signup gate.

2. GTFS·X has flat, transparent pricing. Spare's Flex Builder is bundled into enterprise pricing.

GTFS·X pricing is on the pricing page. Editor: free, anonymous, no signup. Pro tier (cost estimation, demographic coverage): $49/month. Hosted publishing (stable feed URL with monitoring): $500/year. Team tier (Title VI, propensity, multi-user): $199/month.

Spare's Flex Builder is technically free, but it's part of the Spare platform, which is enterprise-quoted. There's no public price for the broader platform that the Flex Builder is a wedge for. For a small agency that has to clear procurement, "transparent flat price under $5k/year" beats "schedule a call with sales" both for the speed of the procurement decision and for the political ease of the decision.

3. GTFS·X does fixed-route + Flex + hosted publishing in one tool. Spare's Flex Builder is Flex-only.

Most rural and small-urban agencies that need to author Flex also need to author fixed-route. The realistic workflow is: take an existing fixed-route feed, add Flex zones, export the combined feed, publish at a stable URL.

GTFS·X does this end-to-end in one tool. Import a fixed-route feed, draw Flex zones, configure booking rules, export the combined feed, optionally publish at feeds.gtfsx.com/<your-agency>/gtfs.zip.

Spare's Flex Builder does only the Flex authoring. You have to bring fixed-route from somewhere else (Excel, another tool, your existing feed), merge it manually, and host it somewhere else. That's three tools and a merge step instead of one tool and an export.

Where Spare is the better choice

To match the honest-comparison framing: there are real cases where Spare is the right answer.

• You already run Spare for microtransit dispatch. If Spare is your operations platform — drivers using the Spare driver app, dispatchers using Spare's console — then Spare's Flex Builder is the natural fit. Authoring Flex zones in the same system you use to operate them is a meaningful workflow win. You shouldn't switch GTFS authoring tools to a different vendor just because.
• You're Flex-only at scale. Some operators have dozens of Flex zones across multiple sub-regional services and no fixed-route component. Spare's enterprise positioning is built for that scale. GTFS·X is built for the small-and-medium operator, not for the multi-region microtransit deployment.
• You want operations + GTFS in one vendor relationship. Some agencies prefer one vendor relationship over two. If you want dispatching, driver app, rider app, and GTFS authoring all under one contract, Spare is the consolidated option. GTFS·X doesn't do dispatch or driver apps and won't try to.

Where GTFS·X is the better choice

Four categories:

• You want to try the tool before signing anything. GTFS·X removes every step between "I'm curious" and "I have a valid feed exported." If your decision process includes "let me see if this works for our service" before procurement, GTFS·X works for that. Spare doesn't — you have to register first.
• Your service is fixed-route + Flex, not Flex-only. This is the majority of small US rural and small-urban operators. One tool for both is a meaningful workflow win.
• You need transparent pricing that fits a small-agency procurement. $49/month or $500/year are inside the small-purchase signature authority of most general managers. Spare's enterprise quote is not.
• You want hosted publishing without signing on for a broader platform. GTFS·X hosted publishing is $500/yr standalone — feed URL, monitoring, draft preview links, embeddable rider mini-site. Spare's hosted publishing comes with the rest of the Spare platform.

What about validator quality?

Both tools produce GTFS-Flex output that passes the canonical MobilityData validator. Spare contributed materially to early Flex tooling and validator alignment; their output is high-quality. GTFS·X validates continuously as you author and blocks export on errors. From the consumer side (trip planners), the output is indistinguishable.

What about trip planner support for Flex?

Worth knowing if you're new to Flex: Google Maps and Apple Maps do not currently consume GTFS-Flex (confirmed April 2025). Transit App and OpenTripPlanner do. Anyone selling you Flex tooling on the premise that "publish Flex and ride Google Maps this week" is overselling. The honest framing is "publish Flex now, get ready for the broader trip-planner ecosystem when Google and Apple enable it." Both Spare and GTFS·X position this correctly; some other vendors don't.

FAQ

Is GTFS·X going to compete with Spare on microtransit operations? No. GTFS·X is a GTFS authoring tool. We don't do dispatch, driver apps, or rider booking apps. If you need operations, Spare or one of the other operations vendors is the right answer; we won't try to be that.

Can I move my existing Spare Flex feed into GTFS·X? Yes. Export a GTFS-Flex zip from Spare and import it into GTFS·X. All Flex entities round-trip — polygon zones, stop groups, booking rules, and pickup/drop-off windows.

Does Spare's Flex Builder support fixed-route? Limited. It exists primarily for authoring Flex zones; fixed-route handling is rudimentary. Most Spare Flex Builder users bring fixed-route from a different tool.

What's the lock-in story? GTFS·X has no proprietary file format. Everything you build is standard GTFS that any other tool can import. If you leave, you leave with a valid GTFS zip that works in any consumer. Spare's Flex Builder is similar in this regard; Spare's broader platform has more lock-in around operations.

Build your Flex feed at gtfsx.com — anonymous, browser-based, no signup required.