Ghost 6, Tinybird Integration and Real Usage Experience

I want to share my experience with the new Tinybird analytics integration in Ghost 6. The idea behind this feature is very good. You can see analytics directly inside the Ghost dashboard without leaving the platform. In theory this should improve workflow and give faster access to data. In practice the situation is very different, especially on the Tinybird Free Plan.

The Free Plan is not usable for any real production site. You cannot use it even for a small blog with a few members. I spent a lot of time configuring Tinybird for Ghost. Because Ghost and Tinybird are official partners I expected the setup to be simple. My expectation was to see a predefined schema ready for Ghost, where the user only needs to create a Tinybird account and paste a token. Instead, you must deploy data sources through the Tinybird CLI. For many people this is a major problem.

The main issue is the 1,000 requests per day limit. At first 1,000 requests may look like a lot. In real usage they disappear in a few hours. If you open the Ghost dashboard and view the analytics multiple times you will burn through the limit very fast. I tested three different Ghost 6 installations and three Tinybird configurations in Docker. Every single time the 1,000 requests were consumed almost instantly.

What is even stranger is what happened after I deleted everything. I removed the Docker images, I deleted the test VPS, everything was gone. Even after that Tinybird continued to receive requests. I kept their dashboard page open in my browser and within half a day the counter reached 374 out of 1,000 requests. This means I was billed for requests without an active Ghost project, only by having their dashboard open.

The service is also expensive. The value you get does not come close to simpler and cheaper alternatives like Rabbit. The configuration process is not easy and the cost is high. From my point of view the integration is limited compared to other solutions. The only good part is the ability to see analytics directly in the Ghost dashboard. The problem is that this comes with a high cost.

I ask the Ghost team or Tinybird team to explain how these requests are calculated. I want to know if every page reload counts as one request or if the amount of data read is the factor. This information changes everything. A clear explanation is needed because at the moment the real behavior is confusing.

If anyone has deeper technical details about how Tinybird counts requests in this Ghost integration, please explain it here.

1 Like

It might be the periodic updates: Tinybird Rate Limits - #2 by muratcorlu
This is why I am exploring a third party solution for my hosting environment for clients.

1 Like

I think worth to mention this topic: We pay for Tinybird to get analytics in self hosted Ghost 6.0? You can find some self-hosting there.

In Synaps Media, we use our in-house solution, that replaces Tinybird behind the scenes. Otherwise it was not possible to provide that service with an affordable price tag :blush:

2 Likes

Okay, after reading many posts and real experiences from other members who use Ghost Blog, it’s obvious that everyone is confused about how Tinybird charges and what exactly the 1,000 requests per day limit really means.

The truth is that although many of us were excited to update to Ghost 6 specifically for this real-time analytics feature, in the end it turns out that it does not help us at all. It only makes sense if you have a huge budget to spend every month, blindly paying Tinybird without even knowing what you are being charged for.

The idea is that, instead of this company, Ghost could have integrated a different solution that is self-hosted, easy to run in Docker, and fully functional without any headaches. But in its current form, this integration is not the best solution from our point of view.

Now with Ghost you depend on Stripe, Mailgun, and Tinybird.

Maybe someone can explain if they managed to use Tinybird in self-hosting mode with Ghost 6. I tried, but something is not working correctly and the entire setup becomes a big mess.

2 Likes

Even though I’m providing a managed hosting alternative for Ghost, I’m still sad to say that, indeed release of Ghost 6 is not fun for self-hosters [1]. I hope it’ll improve in time, because this harms the liberated position of Ghost in the market.

As far as I know, @jannis from Magic Pages still happily uses TinyBird self-managed regions solution in his platform. If you ask the specific issues you had, maybe he can help. But, keep in mind that self-managed regions solution is free “for now”. They will announce the pricing plan for it when it reaches to a stable state. Of course, they can keep it free or make it very affordable. Nothing is clear about that.


  1. not fun for me as well, considering the huge effort to maintain our own ActivityPub server for 100+ websites, without any documentation, and replacing Tinybird with our own analytics solution to keep pricing affordable for everyone ↩︎

2 Likes

You’re very welcome to open PRs that help improve the self-hosting experience

1 Like