TransitFeeds vs. navitia.io

[dotlambda]

I'm not quite sure about the differences between TransitFeeds and navitia.io.

• TransitFeeds seems to support GTFS-realtime, even though the API for that seems cumbersome.
• TransitFeeds does not seem to limit the amount of free API requests.
• I think (but this is more like a feeling) that TransitFeeds supports more providers (718 at the moment). I know that once GTFS data is public, it can also be published on navitia.io, but that's extra work.
• TransitFeeds isn't open source as far as I know.

So overall, I think that TransitFeeds may be a better choice than navitia.io for those providers that use GTFS. What do you think?

Did someone actually consider this alternative when implementing a navitia.io provider?

[grote]

I can run my own instance of Navitia, because it is free software. So you don't depend on an external API provider, API keys and possible revocation at any time and slow updates. I don't think you have this freedom with Transitfeeds, do you?

Also, their API seems to be rather limited and just provides information on the feeds, but doesn't allow complex queries like routing. So both look very different to me.