Managed game analytics for studios that want clarity without a data team

Game analytics infrastructure, managed for you.

Rawbbit hosts, deploys, and manages your game data pipeline, ClickHouse or BigQuery query layer, data models, and dashboards - so your studio can understand player behavior without hiring data engineers. A practical alternative to Firebase Analytics, Amplitude, devtodev, etc.

Built on open-source infrastructure to reduce vendor lock-in. Your raw events stay exportable, and your analytics stack stays transparent.

No subscriptions. No per-user fees. No per-event pricing.

Self-host it free
Rawbbit architecture: game producers send events to the Collector, NATS, and Raw Writer running in Docker containers on a VM. Events land as Parquet in GCS, then flow to a BigQuery external table with SQLMesh and into Metabase. ClickHouse is an optional path for fast OLAP queries. An MCP server and AI agents, including opencode and OpenClaw, connect to the analytics layer.

When your game grows, analytics costs grow with it

Many studios start with Firebase Analytics, Amplitude, or devtodev because setup is fast. The problem appears later: more players means more in-app events produced, more storage, more querying, and more cost pressure.

Usage-based pricing becomes expensive

Once your game starts generating serious event volume, analytics pricing stops feeling lightweight. High daily event counts can quickly turn a convenient tool into a recurring cost problem.

Your data lives inside someone else’s system

Raw event access, exports, and downstream flexibility are often limited by the platform you chose early. That creates lock-in exactly when you need more control.

Building everything yourself takes too much time

A custom analytics pipeline gives you freedom, but most studios do not want to spend weeks assembling ingestion, storage, modeling, and BI from scratch - or hire a data engineer to maintain it.

Why I built Rawbbit

Built from a real game analytics cost problem

I work in data engineering and have spent time around game development teams where analytics volume grows fast and platform limits become real. I've seen what happens when Firebase Analytics hits the 1 million events per day limit: either you pay for the enterprise version or you start losing data.

Read more about the founder →

A practical managed analytics setup for game studios

Rawbbit gives you a fully managed analytics pipeline, deployed into infrastructure you own and operated for you, while keeping your raw event data portable from the beginning.

Deployed and managed for you

I deploy and manage the system in infrastructure you own. No recurring vendor fees. Technical teams that prefer to run it themselves can self-host for free.

  • Hosted, deployed, and managed for you
  • Runs on infrastructure you own and control
  • Self-serve option still available for technical teams
1 VM to start
Docker containers
Scale later when needed

Portable raw event layer

Events are written to the Blob storage in Parquet format (Google Cloud Storage by default). That means your raw event layer stays portable and can be moved, replayed, or connected to other systems later without locking your tracking model to one vendor.

  • Parquet raw storage for portability
  • BigQuery or ClickHouse as the query layer
  • More downstream database support coming
Events Parquet BigQuery / ClickHouse Models BI

Default pipeline and deployment model

Rawbbit is a managed event tracking, ingestion, and raw-storage pipeline designed to keep the raw layer durable and portable - deployed and operated for you, in infrastructure you own.

The current runtime path is straightforward: producers send event batches to an HTTP collector, NATS JetStream buffers the write path, and a raw writer lands partitioned Parquet files in object storage.

The supported query path continues from that raw layer through a BigQuery external table or ClickHouse, while keeping raw Parquet as the system-of-record boundary.

Producer → Collector API → NATS JetStream → Raw Writer → Parquet in object storage

See the full architecture →

Event model designed for flexible analytics

Rawbbit uses a simple event envelope with stable top-level fields and flexible custom payload areas.

{
  "event_id": "uuid",
  "app_id": "mygame.prod",
  "environment": "prod",
  "event_name": "level_completed",
  "event_timestamp": "2026-04-06T06:00:00.000Z",
  "received_at": "2026-04-06T06:00:00.412345+00:00",
  "user": {
    "user_id": "123",
    "user_pseudo_id": "anon_abc",
    "session_id": "sess_xyz"
  },
  "device": {
    "platform": "android",
    "app_version": "1.4.2",
    "os_version": null,
    "device_model": null,
    "locale": null,
    "timezone": null
  },
  "event_params_json": "{\"level\": 12, \"duration_sec\": 84}",
  "user_properties_json": "{\"payer\": true, \"country\": \"FI\"}",
  "traffic_source_json": "{}",
  "geo_json": "{}",
  "consent_json": "{}",
  "ingest_request_id": "5d89a0c9-8e70-4108-b5e8-49bf9b2896d8",
  "ingest_user_agent": "iOS ...",
  "ingest_ip_hash": "d8e0...",
  "nats_stream": "EVENTS",
  "nats_sequence": 12345
}

Core fields

event_id, app_id, event_name, and event_timestamp define the event envelope and make ingestion, replay, and downstream processing predictable.

Identity fields

user_id, user_pseudo_id, and session_id support both authenticated and anonymous analytics patterns.

Flexible fields

event_params and user_properties are designed for custom sub-fields. These can later be transformed in SQLMesh into explicit reporting columns and output tables.

Two ways to use Rawbbit

Free self-serve for technical teams, or a one-time €500 done-for-you setup. No recurring fees.

Free self-serve

€0 one-time

For technical teams who want to deploy and operate the stack themselves.

Self-host it free

Who Rawbbit is for, and who it is not for

This is not meant to be everything for everyone. It works best for teams with some analytics maturity who want ownership without building the whole stack from zero.

Who Rawbbit is for

  • Game studios that want analytics without hiring or managing data engineers
  • Teams with a product or data owner who wants to explore player behavior
  • Studios comfortable reading dashboards and asking questions in SQL or BI tools like Metabase
  • Teams that want to own their data without building or operating the pipeline themselves

Who it is not for

  • Teams expecting a polished plug-and-play SaaS dashboard with zero setup
  • Studios with no one who will ever look at or query the data
  • Teams unwilling to own any infrastructure, even managed

Frequently asked questions

Not a traditional SaaS. Rawbbit is a managed analytics pipeline deployed into infrastructure you own - I host, deploy, and manage it for you, but your data and deployment stay yours. It's open-source, so there's no vendor lock-in.

The system runs in infrastructure you own (your own VM and cloud services), but I deploy and manage it for you. You keep full ownership and control; you just don't have to operate it yourself. Technical teams that prefer to self-host can do so for free.

No. The service offer is a one-time 500 EUR setup payment. The self-serve version is free.

The default setup starts simple, usually on one VM, and can be scaled later as your traffic increases. Cloud VM is easy to scale, usually computing performance can be increased just by updating settings in the interface.

I've worked with both Google Cloud Platform and UpCloud and recommend either.

If you go with UpCloud, this signup link (https://signup.upcloud.com/?promo=UR4689) includes free starting credit and supports the project at no cost to you. VM costs start around 3 EUR/month.

Raw events are written to the blob storage in Parquet format (Google Cloud Storage by default).

Yes. Portability of the raw layer is one of the main design goals.

Yes. Backend producers are supported now. JavaScript support is included, and game SDK support is planned.

It is designed for teams that want to move away from those tools and own their analytics stack, though migration details depend on your current event setup.

Yes. I'm working on it.